> 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/tracking-explained/deduplication-best-practices.md).

# Deduplication Best Practices

Cross-channel deduplication makes sure a single conversion is credited and paid to only one marketing partner, even when the customer interacted with several channels before they purchased. Without it, two or more channels can claim the same sale, and you end up paying for it twice.

To prevent this, set up one rule-based source of truth for attribution. Decide in advance which channel gets credit in each scenario, and make sure your setup applies that decision every time.

## Why deduplication matters

If two or more channels are credited for the same conversion, you can run into these problems:

* **Duplicate payouts:** you pay commission more than once for the same sale.
* **Partner disputes and contract breaches:** a setup that doesn't match each partner's terms can lead to disputes, and in some cases a breach of contract.
* **Inaccurate return on investment (ROI) reporting:** budget decisions get made on numbers that overstate what each channel drove.

## Know your contract terms

Align your attribution logic with each channel's contract before you launch. A setup that ignores a partner's crediting terms can cause a breach, even when no one intended one. Review the template terms and payout rules for each partner and network, and confirm that your credit groups, exception lists, and payout rules match them.

## Don't use action reversals to fix attribution

Attribution errors are not a valid reason for an action reversal. Reverse an action only when the conversion didn't complete, for example:

* Customer returns or cancellations
* Payment failures
* Fraudulent transactions
* Exceeded budget caps

{% hint style="warning" %}
**Warning:** Using reversals to correct attribution can breach your contracts. Fix the attribution setup instead.
{% endhint %}

## Set up attribution before you launch

Map every marketing channel and track it under one unified source of truth before you start paying partners. Setting this up early takes far less time than correcting duplicate payouts after the fact.

## Credit groups

Credit groups let you prioritize or de-prioritize how the program attributes certain partners. Set each partner as Preferred, Standard, or Non-Preferred. Credit groups can quickly change how attribution works across your program, so review them carefully before you make changes. Credit groups take precedence over promo code tracking attribution.

* To see how each group changes attribution, read [Credit Groups Explained](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/credit-groups-explained.md).

## Promo code exception lists

Use promo code exception lists to pay partners different rates based on the promo codes tied to the actions they drove.

Use these pages to set up promo code exception lists:

* Create your lists by following [Create Promo Code Exception Lists](https://help.impact.com/brand/what-would-you-like-to-learn-about/account-administration/program-settings/exception-lists/create-promo-code-exception-lists.md).
* Set the payout rate for each list by following [Set Payout Rules for Category, SKU, or Promo Code Exception Lists](https://help.impact.com/brand/what-would-you-like-to-learn-about/account-administration/program-settings/exception-lists/set-payout-rules-for-exception-lists.md).
* Add each list to your template terms under Payout Groups by following [Create Payout Groups](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).

## Shared Id

The Shared Id identifies the traffic source for each action, so you can adjust conversion payouts based on where the traffic came from. Partners can add the Shared Id as an extra parameter to their marketing content.

To use the Shared Id in your payouts, see [Dynamically Pay Partners with the Shared Id](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/dynamically-pay-partners-with-the-shared-id.md).

## Optimize

Optimize is impact.com's cross-channel attribution suite. It checks for overlapping touchpoints and lets you configure which network or partner gets credit for an action. Use it when you promote your brand through affiliate networks alongside impact.com.

To set up deduplication in Optimize and learn how it works, read these pages:

* Add each affiliate network to Optimize and set how it's credited by following [Configure Affiliate Networks for Deduplication](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/configure-affiliate-networks-for-deduplication.md), so its conversions aren't paid twice.
* See how Optimize tracks each channel and what it reports on the conversions each one drives by reading [Optimize Channels](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/optimize-channels.md).
* Create the rules that tell Optimize which visits come from each channel by following [Set Up Rules to Identify Channel Traffic](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/set-up-rules-to-identify-channel-traffic.md).

## Tracking setup

Deduplication depends on accurate tracking. Work through these pages:

* Set up a tracking domain and keep cookies reliable by following [Tracking Best Practices](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/tracking/tracking-best-practices.md).
* See how partner links carry tracking data in [Tracking Links Explained for Brands](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/tracking/tracking-explained/tracking-links-explained-for-brands.md).
* Track clicks with the Universal Tracking Tag by following [Tracking with Universal Tracking Tag (UTT)](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-universal-tracking-tag-utt.md).
* Track clicks through gateway links by following [Configure Gateway Tracking Settings](https://help.impact.com/brand/what-would-you-like-to-learn-about/account-administration/program-settings/tracking-settings/configure-gateway-tracking-settings.md).

## Additional resources

* [Promo Codes Overview](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/promo-codes/promo-codes-overview.md) — How promo codes work, and how they tie a conversion to a specific partner or source.
* [impact.com Tracking Methods & Terminology Explained](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/tracking/tracking-explained/impactcom-tracking-methods-and-terminology-explained.md) — The tracking methods impact.com uses, and the terms you need to read your tracking settings and reports.


---

# 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/tracking-explained/deduplication-best-practices.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.
