When an advertiser works with multiple affiliate networks, the same conversion can sometimes be measured by more than one network. Affiliate network deduplication helps prevent duplicate commission payments by deciding which competing affiliate network should receive credit for a conversion.
This article explains when automatic deduplication is needed, what a cookie switch setup does, and which implementation method may be suitable.
What is affiliate network deduplication?
Affiliate network deduplication is the process of deciding which competing affiliate network should track and receive credit for a conversion.
The most common setup is based on the last click principle. This means the affiliate network responsible for the latest valid affiliate click before the conversion is selected.
A cookie switch setup normally stores the latest affiliate network source in a cookie or similar storage mechanism. On the conversion page, this stored value is used to decide which network conversion pixel should fire.
Before you start: do you need automatic deduplication?
Automatic network deduplication is not always required from day one. When an advertiser starts working with multiple affiliate networks, the overlap between networks may initially be limited. The impact of duplicate registrations depends on the publishers, traffic sources, transaction volume, and campaign setup.
In these situations, it may be sufficient to monitor overlap manually and correct duplicate transactions when needed. This can be a practical approach for new campaigns, lower-volume campaigns, or setups where the amount of overlap is still unclear.
As traffic and transaction volume increase, manual correction becomes less scalable and more error-prone. At that point, an automated deduplication setup can help prevent duplicate commission payments and keep attribution consistent across competing affiliate networks.
Before implementing automatic deduplication, first confirm whether the expected overlap and transaction volume justify the additional setup and maintenance.
Manual monitoring may be sufficient when:
- You are just starting with multiple affiliate networks
- Transaction volume is still limited
- Overlap between networks appears low
- Manual transaction correction is still manageable
- You first want to measure how often duplicate registrations occur
Automatic deduplication is recommended when:
- You work with multiple competing affiliate networks at meaningful volume
- Duplicate registrations happen regularly
- Manual corrections take too much time
- You need consistent last click logic across all involved affiliate networks
- You want to reduce the risk of paying multiple commissions for the same order
Only deduplicate between competing affiliate networks
Network deduplication is intended to prevent duplicate commission payments between competing affiliate networks. It is not meant to act as a complete attribution model across all marketing channels.
We recommend against suppressing affiliate tracking because another marketing channel or traffic source, such as SEA, paid social, display, email, or direct traffic, was also involved.
Affiliate marketing is a post-paid channel, where commission is paid after a valid conversion. Many other marketing channels are pre-paid or budget-based. Deduplicating a post-paid affiliate channel against a pre-paid channel can unfairly remove a valid affiliate commission, even though the advertiser has already paid for the other channel separately.
Advertisers can still use their own attribution reports to analyze the role of different marketing channels. This analysis should be kept separate from the decision to deduplicate transactions between competing affiliate networks.
Last click does not show the full contribution
The last click principle determines which network is rewarded, but it does not always reflect the full contribution of all publishers involved in the customer journey.
Some advertisers choose to reward assisting publishers separately, depending on their attribution strategy. Read more about assisted conversions.
Common deduplication methods
The appropriate method depends on the campaign setup, tracking implementation, and attribution requirements.
- Last Cookie Counts (LCC): stores the latest affiliate click source and uses this value on the conversion page
- Last Event Counts (LEC): makes recent Daisycon view event data available on the visitor’s client, mainly to support post view deduplication
- Broad catch-all setup: triggers Daisycon tracking when the source is Daisycon, or when no known competing affiliate network has been identified
- Custom setup: uses advertiser-side, tag management, or server-side logic to decide which network pixel should fire
When to use LCC
Use LCC when deduplication is based on affiliate clicks and each network can pass a recognizable source value to the advertiser website.
- The latest affiliate click should decide which network is rewarded
- The network source can be stored when the visitor lands on the website
- The stored source can be read on the conversion page
- Post view attribution does not need to be considered
Read more: Affiliate network deduplication with Last Cookie Counts (LCC).
When to use LEC
Use LEC when recent Daisycon event data, such as post view data, should be considered in advertiser-side deduplication.
- The campaign uses post view attribution
- The advertiser deduplicates between competing affiliate networks
- The current setup depends on click cookies, click IDs, or network flags
- The advertiser needs to detect recent Daisycon activity on the visitor’s client
LEC can be combined with existing LCC logic. A known, newer click from a competing affiliate network should not be overwritten by an older Daisycon view.
Read more: Using Last Event Counts (LEC) for post view deduplication.
Fallback logic
A fallback rule is needed when no network source or recent event data is available. The appropriate fallback depends on the advertiser’s setup and risk preference.
- Trigger all relevant affiliate pixels for maximum measurement coverage, with a higher risk of duplicate registrations
- Trigger no affiliate pixels when the source is unknown, with a higher risk of missed conversions
- Trigger Daisycon when the source is Daisycon or when no known competing affiliate network has been identified
Fallback logic must be agreed before going live. Incorrect fallback logic can cause duplicate registrations or missed conversions.
Implementation responsibility
Network deduplication only works correctly when all involved affiliate networks are configured using consistent logic. Daisycon can only control the Daisycon conversion pixel. The advertiser is responsible for making sure the full setup works across all involved networks and tools.
Tracking based on cookies or client-side storage can be affected by browser restrictions, consent settings, privacy tools, and ad blockers. Always test the implementation before going live and monitor the results after release.
Conclusion
Affiliate network deduplication can help prevent duplicate commission payments between competing affiliate networks, but it is not always required immediately. First check whether the expected overlap and transaction volume justify an automated setup. Use LCC for click-based deduplication and LEC when post view attribution also needs to be considered. Do not use affiliate network deduplication as a general cross-channel attribution model.