> 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/add-payout-restrictions-to-template-terms.md).
# Add Payout Restrictions to Template Terms
Payout restrictions help you pay only for high-value, qualified conversions. By defining specific conditions that block payouts, you can automate compliance and quality control.
## Configure payout restrictions
1. From the left navigation menu, select  **\[Engage] → Contracts →** [**Template Terms**](https://app.impact.com/secure/advertiser/engage/contracts/library/view-manage-ios-flow.ihtml).
2. Modify or create your terms:
* **To modify existing terms:** Find the existing terms for which you want to add payout restrictions, then select  **\[More] → Modify Terms**.
* **If you are creating new template terms:** in the upper-right, select **Create Template Term**.
3. Next to *Payout Restrictions*,  **\[Toggle on] Specify items that will not generate a payout**.
4. Set up the payout restriction's [*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  **\[AND]** to create a second rule within the same payout restriction. In this case, all rules must apply for the payout restriction to apply.
* Optionally, select  **\[Add another restriction]** to add a separate restriction in which the rules are independent of each other.
5. Select **Next**.
1. If you have existing partners joined to these template terms, select **Next** to review your changes, then if satisfied with the changes, select **Save**.
2. If there are no partners joined to these template terms, select **Next**, then **Save**.
## Common examples
* **Traffic Type + is not present:** Use this rule when you want to pay only for clearly identified traffic sources.
* **Ad Keyword + contains + \[Term]:** Prevents payouts for clicks associated with restricted or non-compliant keywords (e.g., "Firearms" or "Discount").
* **Geo-Restrictions:** Blocks commissions from regions where your product is not available.
## Payout restrictions based on location
When configuring geographic restrictions, 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 |
| ---------------------------------- | ------------------------------- | ------------------------------------------------- |
| Restrict based on shipping address | Customer Country/Region | Data passed via your tracking pixel at checkout. |
| Restrict 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/add-payout-restrictions-to-template-terms.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.
