> 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/tracking/stand-down-policy-explained.md).

# Stand-Down Policy Explained

impact.com's [stand-down policy](https://app.impact.com/pcontent/stand-down-policy.ihtml) is a best practice that prevents certain partners—particularly those using browser extensions, toolbars, or in-cart solutions—from interfering with the shopping experience if another click has already been recorded from another partner. Once a shopper has engaged with a tracking link (e.g., from a creator, content publisher, cashback program, or coupon site), the `afsrc=1` parameter is automatically appended to the landing page URL for all partner-driven traffic. Any competing extension must withdraw and not attempt to override the original click by triggering pop-ups, activating new tracking links, or altering the customer's path to purchase.

#### How it works

1. The consumer clicks on a link from a partner site, which brings them to a brand's landing page.
2. The `afsrc=1` parameter is automatically appended to the landing page URL.
3. The competing partner, e.g., a browser extension, checks the link that redirected the consumer and recognizes it as an impact.com tracking link.
4. The extension is then required to abide by the stand-down policy, and no extension pop-up should be made visible for that consumer.

#### Check the stand-down policy in your template terms

You can ensure the stand-down policy is enabled by viewing your template terms' *General Terms* section.

1. From the left navigation bar, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **Contracts** → **Template Terms**.
2. Hover over the relevant template terms, then select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FMLtRUwWz0pujlfmYWOgg%2FMoreVN.svg?alt=media\&token=03a3c355-a347-4207-baf7-c44fadf6d080) **\[More]** → **View Terms**.
3. Scroll down to the *General Terms* section, then look for *Stand Down Policy*.

   <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F19H28e2EDbt26S4WrsLh%2FScreenshot%202026-05-06%20at%2015.36.13.png?alt=media&amp;token=6f7460f6-3b25-460b-9a93-9046b1185af4" alt="" width="563"><figcaption></figcaption></figure></div>

#### Disable the stand-down policy

{% hint style="warning" %}
**Warning:** Your program’s stand-down policy is enabled by default, and we recommend you keep it enabled to establish good partnerships. Explicitly stating that you adhere to a stand-down policy will give partners a better opportunity to maintain their status as a conversion winner.
{% endhint %}

1. From the top navigation bar, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media\&token=f84c5b17-fae4-4a30-990a-9de5e57a150b) **\[User profile] → Settings**.
2. On the right, under *Tracking*, select **General**.
3. Below the *Stand Down Policy* section, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FwXho9QKP3e4iU4ZKUSJ5%2F167ebb8cc30303.svg?alt=media\&token=a046e9f0-63aa-46f6-8a35-f73973fd326c) **\[Checkbox]** **Activate stand down policy on all template terms**.
4. Select **Save**.


---

# 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/platform-features/tracking/stand-down-policy-explained.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.
