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

# Step 4: Partner Engagement

Expand the way partners promote you beyond default online tracking links by [creating unique ads](/brand/what-would-you-like-to-learn-about/platform-features/ads/create-ads.md). Be sure to prioritize which [ad types](/brand/what-would-you-like-to-learn-about/platform-features/ads/create-ads/introduction-to-asset-types.md) to create based on your promotional methods.

An important part of working with partners is [ensuring that your product catalog is available](/brand/what-would-you-like-to-learn-about/platform-features/product-catalogs/add-product-catalogs-as-a-brand.md) for use by your partners and your products are featured in the product marketplace. Making your products available on the Product Marketplace could result in more incoming program applications.

Another useful tool for partner engagement is your [Resources](https://app.impact.com/secure/advertiser/engage/ads/manage-resources-flow.ihtml) page. This page is a great way to share a whole host of [training material and educational assets for partners](/brand/what-would-you-like-to-learn-about/platform-features/ads/requests-from-partners/create-a-resource-to-share-with-partners.md) to ensure they effectively market your products or services to their audience to generate sales. You can link out to your Resources page in your initial welcome message and scheduled Newsletters.

It’s important to keep your partners in the loop regarding promotions, product/feature launches, company updates, etc. impact.com’s [Newsletters](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/introduction-to-newsletters.md) feature is the easiest way to do this, while also increasing partner engagement and productivity. Check out a mockup of what a branded newsletter could look like below:

<div data-with-frame="true"><figure><img src="https://paligoapp-cdn-eu1.s3.eu-west-1.amazonaws.com/impact/attachments/f01cdffa431a4d75ff09c130b66974d4-af28286ab8956d657e8ef50c9e376e6f.png" alt=""><figcaption></figcaption></figure></div>


---

# 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/what-would-you-like-to-learn-about/performance-program/introduction-welcome-to-impact.com/step-4-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.