Most operators leave the old affiliate platform open longer than they should because traffic is still coming through it.
That logic sounds safe. It isn't.
Two platforms tracking the same player events means duplicate commissions, split NGR, and attribution gaps that do not surface until the weekly commission review. WebKit's 24-hour cookie cap adds another layer: players who click an affiliate link and register the next day may not be attributed to anyone.
The overlap window is not the risk. Running it without a hard closure date is.
This covers how to structure the cutover, what to monitor after, and where migrations typically break down.
Most operators treat running both platforms as a safety net. It isn't. Yes, you can run two affiliate platforms simultaneously, but only within a controlled overlap window of two to four weeks where one platform is the designated system of record for commissions and attribution. Outside that window, simultaneous operation is not a transition strategy. It is a data integrity problem that compounds the longer it runs.
The legitimate use case is narrow: the new platform is live and tested, the old platform is winding down, and affiliates are mid-link-swap. A short overlap lets high-volume partners transition without a hard cutoff that breaks attribution mid-campaign. During this window, the new platform handles all commission calculations and player attribution. The old platform stays accessible for historical reporting and pending payouts, nothing else.
Two platforms actively tracking the same player events with no designated primary source is where the damage starts. One player registers through an affiliate link, both platforms claim the conversion, and two commission records are created. In iGaming, player journeys span multiple sessions and devices before a first deposit, so the window for duplicate tracking is longer and the revenue at stake is higher than in most other verticals.
Most tracking failures during migrations are not caused by bad technology. They are caused by ambiguous ownership of the tracking layer. When two platforms compete to own the same conversion event, three failure modes emerge.
The NGR fragmentation problem is more serious than it looks. NGR is not a single field. It is GGR less a deductions ledger that includes taxes, admin fees, jackpot contributions, payment processing charges, bonuses, free bets, chargebacks, and fraud. One operator's affiliate terms explicitly acknowledge that their tracking platform reflects GGR and NGR as the same figure, requiring manual derivation of true NGR by applying standard deductions totaling 56.5% of GGR. When reporting is split across two platforms with different revenue schemas, that manual reconciliation becomes a weekly finance task instead of an edge case.
Set the closure date for the old platform before the new one launches, not after. Operators who leave the old platform open indefinitely because traffic will eventually drop are the ones who end up with split data they cannot reconcile six months later.
|
Phase |
Timeframe |
What should be live |
|
Pre-launch |
Four to eight weeks before new platform goes live |
Old platform only |
|
Overlap window |
Two to four weeks after new platform launches |
Both platforms, new platform is system of record |
|
Closure |
At or before four weeks post-launch |
New platform only |
High-volume SEO affiliates with hundreds of embedded links need more lead time than display or paid media partners who can update a single redirect. Contact them individually before the mass announcement.
The decisions made before the overlap window opens determine whether the migration stays controlled or turns into a six-month reconciliation project. Each step below addresses a specific failure mode.
Before any overlap begins, the new platform must be declared the authoritative source for commissions and attribution, documented internally and communicated to affiliates in writing. If a dispute arises during the overlap, the system of record wins, not whichever platform shows the higher conversion count.
Historical player cohort data, commission records, and creative performance history should be exported and stored independently before decommissioning. Most platforms will not migrate historical data automatically, and once the old platform is closed, that data is often inaccessible or requires a paid export request. In iGaming, historical LTV data is particularly hard to reconstruct because it reflects player behavior across months of micro-transactions.
Registration events, first deposit events, and NGR postbacks should all be verified end-to-end before the overlap window opens. A single misconfigured postback parameter can cause an entire affiliate's conversions to go untracked, and in iGaming that gap may not surface until the weekly commission review, by which point dozens of players have been misattributed.
Affiliates need three things before the cutover:
A mass email is not enough for partners driving significant player volume. High-volume affiliates warrant individual outreach.
All pending and approved commissions should be settled before the closure date. The new platform cannot retroactively pay commissions for conversions it did not track, which means any unpaid balance on the old platform becomes a manual reconciliation task for finance.
Declaring the migration complete on closure day is how attribution gaps go undetected for months. The overlap window creates a data gap that needs active monitoring, not a checkbox.
Run a partner-by-partner comparison of the two weeks before cutover versus the two weeks after. A sudden drop in attributed conversions post-cutover usually means some affiliates have not yet swapped their links, not that performance has fallen.
Once the new platform has two to four weeks of clean data, compare NGR by affiliate cohort against the same period on the old platform. If the new platform is ingesting only "conversion plus amount" without the full deductions ledger, the NGR figures will not match, and finance will not be able to reconcile payouts.
Any player who registers or deposits without an affiliate attribution tag signals a broken or missing tracking link. If unattributed registrations spike above 10% of total new players in the first two weeks post-cutover, either the cutover was not communicated effectively or the new platform's tracking implementation has a gap.
Generic affiliate tools track that a conversion happened. They are not built to handle the revenue schema complexity, cross-device attribution gaps, or LTV measurement requirements that iGaming migrations surface. Intelitics is.
Intelitics ingests first-party data from game platforms via push and pull APIs through a normalization layer, so operators maintain a consistent view of player-level data even when two affiliate platforms are simultaneously active. The normalization layer reconciles revenue schemas in real time, which means finance is not manually deriving NGR from two environments with different deduction logic.
Intelitics uses cookieless tracking IDs that follow players across devices and sessions. Player journeys that start on one platform's link and convert after the switch are still attributed correctly, even when WebKit's 24-hour cookie cap would otherwise break the attribution chain. Server-side identity resolution eliminates the failure mode that cookie-based tracking cannot handle during a migration overlap.
Once the new platform is live, Intelitics' predictive lifetime value model generates player value forecasts within 72 hours of acquisition. Operators can verify that affiliate cohorts coming through the new platform are comparable in quality to cohorts from the old platform, without waiting weeks for deposit and revenue data to accumulate. Low-quality traffic sources get identified during the overlap window, not months later.
Running two iGaming affiliate platforms simultaneously is manageable within a two-to-four-week controlled overlap. Outside that window, it is a liability.
Three actions that separate clean migrations from six-month reconciliation projects:
If your current affiliate platform was not built for iGaming's revenue complexity, the migration is also an opportunity to fix that. Schedule a demo with Intelitics to see how the platform handles affiliate tracking, NGR normalization, and predictive LTV from day one of your new setup.