> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/it/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-3-partner-engagement.md).

# Fase 3: coinvolgimento del partner

## Pianifica i tuoi contatti <a href="#plan-your-outreach-0-0" id="plan-your-outreach-0-0"></a>

Pianifica una serie di messaggi persistenti, orientati al valore [email di outreach](/brand/it/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md). Mantienilo conciso e concentrati sui vantaggi di partecipare al tuo programma, come tassi di payout più elevati, una finestra dei cookie più lunga e qualsiasi bonus di performance.

Rendi l’offerta più allettante con un bonus di ingresso o un aumento temporaneo delle tariffe per favorire l’adozione iniziale. [Termini programmati](/brand/it/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/set-limited-time-payouts-with-scheduled-terms.md) oppure [Product Boost](/brand/it/what-would-you-like-to-learn-about/beta-product-boost/product-boost-campaign-management/create-a-product-boost-campaign.md) può aiutarti a farlo.

## Condividi notizie rilevanti <a href="#section-id23524846371987" id="section-id23524846371987"></a>

È importante tenere i tuoi partner informati su promozioni, lanci di prodotti/funzionalità, aggiornamenti aziendali, ecc. La [Newsletter](/brand/it/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/introduction-to-newsletters.md) di impact.com è il modo più semplice per farlo, aumentando al contempo il coinvolgimento e la produttività dei partner.

## Forma i partner <a href="#section-id235248464024764" id="section-id235248464024764"></a>

Usa la tua [*Risorse*](https://app.impact.com/secure/advertiser/engage/ads/manage-resources-flow.ihtml) pagina per condividere [materiali di formazione e risorse didattiche](/brand/it/what-would-you-like-to-learn-about/platform-features/ads/requests-from-partners/create-a-resource-to-share-with-partners.md) che aiutano i partner a promuovere efficacemente i tuoi prodotti Amazon e a generare vendite. Rimanda alla tua *Risorse* pagina nel tuo messaggio di benvenuto iniziale e in tutte le newsletter programmate.

Sentiti libero di condividere la documentazione di supporto pertinente per assicurarti che i partner capiscano come promuovere i tuoi prodotti e cosa [migliori pratiche](https://help.impact.com/partner/what-would-you-like-to-learn-about/seller-partnerships/amazon-seller-partnerships/best-practices-for-seller-partners) li aiuterà ad avere il massimo successo.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/it/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-3-partner-engagement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
