> 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/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/set-payout-rules-using-payout-groups.md).
# Create Payout Groups
Take the PXA course
*Payout Groups* allow you to set rules on partner payouts for actions they drive, and they are included in your [template terms](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms.md). If a payout group's condition is met, it will apply the payout change at the same level (order or item) as the template term's *default payout*.
Only 1 payout group can apply at a time. Customized payout groups work best when they're mutually exclusive, so if payout groups have overlapping conditions, place the more specific payout group criteria at the top (e.g., "Customer Status is New & Order Total ≥ $200"), and the more common criteria near the bottom (e.g., "Order Total ≥ $200").
## Add a payout group to a template term
{% hint style="warning" %}
**Warning:** Adding additional payout rules might require some technical knowledge. If you want to configure additional payout rules, [contact support](https://app.impact.com/secure/advertiser/support/customer-support-portal-flow.ihtml?execution=e3s1).
{% endhint %}
Payout groups are usually added when you create a template term, but you can always switch out contracts later.
1. From the left navigation bar, select  **\[Engage] → Contracts →** [**Template Terms**](https://app.impact.com/secure/advertiser/engage/contracts/library/view-manage-ios-flow.ihtml).
2. In the upper-right, select **Create Template Term**.
3. Next to *Event Type*, from the  **\[Drop-down menu]**, select the event type this template term applies to.
4. Next to *Payout Groups*, toggle  **\[Toggle on]** **Set up customized payout groups**.
5. To add a payout group, select **Add new**.
6. Set up the payout group's [*payout rules*](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/how-payout-rules-work.md) using the  **\[Drop-down menu]** and fields.
* Optionally, select  **\[Add another]** to create a second rule within the same payout group.
* If you add multiple rules to 1 payout group, all rules must apply for the payout group to apply.
7. Enter the **Payout** amount, and if given the option, specify **Limits** on payable items.
* If you don't see the *Limits* toggle in the modal, [contact support](https://app.impact.com/secure/advertiser/support/customer-support-portal-flow.ihtml) to request that the feature be added to your account.
8. In the lower-right corner of the modal, select **Add** to save the payout group.
9. To create another payout group, select **Add new**. If you create multiple groups, you can select and drag them around to change their rank.
How ranking works
Your payout groups are evaluated from top to bottom, and the first group whose conditions match the conversion applies — all lower-ranked groups are skipped. Place your most specific conditions at the top and broader or catch-all conditions at the bottom.
For example, a group targeting **New Customers with an order total greater than $200** must sit above a group targeting **New Customers** only. If the broader group ranks first, it matches every new customer order before the more specific rule gets a chance to apply.
10. Continue [creating your template term](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms.md).
{% hint style="success" %}
**Note:** When setting up a payout group using the *Referral URL* parameter, you can use the *wildcard* option to match despite any former or following characters. For example, use `*facebook*` to match for any Referral URL coming from Facebook.
{% endhint %}
### Combine payout group criteria
* Commas in your payout group criteria will not combine the two criteria (e.g., `Item Category is ACME, Anvils` will be interpreted as Item Category is ACME OR Anvils). You can get around this by placing quotation marks around your rule containing a comma (`Item Category is "ACME,Anvils"`).
## Payout groups based on location
When configuring payout groups based on geographic location, you'll have to choose the correct data source. You can distinguish between where a click originated and where the customer actually resides.
| Requirement | Recommended Parameter | Data Source |
| -------------------------------------- | ------------------------------- | ------------------------------------------------- |
| Payout group based on shipping address | Customer Country/Region | Data passed via your tracking pixel at checkout. |
| Payout group based on click location | Referral Derived Country/Region | The user's IP address at the moment of the click. |
---
# 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/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/set-payout-rules-using-payout-groups.md?ask=&goal=
```
`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.
