> 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-2-contracting-and-commissions.md).

# Step 2: Contracting & Commissions

impact.com offers many ways to fine-tune how you pay partners based on different data points and variables (e.g., SKU, promo code, cart size, or customer status). These dynamic commissions are a great way to incentivize partners further to help you reach your program goals by rewarding specific behavior.

You can use [payout groups](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/set-payout-rules-using-payout-groups.md) to offer different payouts. You can also offer [performance bonuses](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/performance-bonus/add-a-performance-bonus-to-a-contract.md) to partners that drive the most value to your program and use [template terms](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms.md) to set up ideal contracts.

Dynamic commissioning can also be tailored based on your specific business goals. A few examples are below:

| Business Goal               | Commission Strategy                                                                                       |
| --------------------------- | --------------------------------------------------------------------------------------------------------- |
| Increasing revenue          | <ul><li>Higher commission on % of sale</li><li>Higher commission rates for high-margin products</li></ul> |
| Increasing new customers    | Higher commissions for actions from new customers                                                         |
| Increasing app downloads    | Increase commissions for partners driving app downloads                                                   |
| Improving ROAS              | Create commission structures based on promotional method and level of effort                              |
| Decreasing CAC              | Increase commissions for actions from repeat customers, higher purchase frequency, and higher AOV         |
| Increasing customer LTV     | Recurring commissions for repeat customers or subscriptions                                               |
| Improving profit margin     | Lower rates for low margin products and vice versa                                                        |
| Promoting key SKUs/products | Increase commissions for specific SKUs/products                                                           |


---

# 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-2-contracting-and-commissions.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.