> 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/es/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-3-partner-engagement.md).

# Paso 3: Participación de socios

## Planifica tu alcance <a href="#plan-your-outreach-0-0" id="plan-your-outreach-0-0"></a>

Planifica una serie de comunicaciones persistentes, orientadas al valor [correos electrónicos de contacto](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows). Manténlo conciso y céntrate en los beneficios de participar en tu programa, como las tasas de pago más altas, una ventana de cookies más larga y cualquier bonificación por rendimiento.

Endulza la propuesta con un bono de inscripción o un aumento temporal de la tasa para impulsar la adopción inicial. [Términos programados](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/set-limited-time-payouts-with-scheduled-terms) o [Impulso de producto](https://help.impact.com/brand/what-would-you-like-to-learn-about/beta-product-boost/create-a-product-boost-campaign) puede ayudarte a hacerlo.

## Comparte noticias relevantes <a href="#section-id23524846371987" id="section-id23524846371987"></a>

Es importante mantener a tus partners al tanto de promociones, lanzamientos de productos/funciones, novedades de la empresa, etc. Las newsletters de impact.com [newsletters](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/introduction-to-newsletters) es la forma más sencilla de hacerlo, al tiempo que aumenta la participación y la productividad de los partners.

## Capacita a tus socios <a href="#section-id235248464024764" id="section-id235248464024764"></a>

Usa tu [*Recursos*](https://app.impact.com/secure/advertiser/engage/ads/manage-resources-flow.ihtml) página para compartir [materiales de formación y recursos educativos](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/ads/requests-from-partners/create-a-resource-to-share-with-partners) que ayudan a los socios a comercializar eficazmente tus productos de Amazon y generar ventas. Enlaza con tu *Recursos* página en tu mensaje inicial de bienvenida y en cualquier newsletter programada.

No dudes en compartir documentación de ayuda relevante para asegurarte de que los partners entiendan cómo promocionar tus productos y qué [mejores prácticas](https://help.impact.com/partner/what-would-you-like-to-learn-about/seller-partnerships/amazon-seller-partnerships/best-practices-for-seller-partners) les dará mayores probabilidades de éxito.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.impact.com/brand/es/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=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
