Your affiliate platform works. Tracking fires, commissions calculate, partners get paid. That's the assumption that keeps teams from migrating. The reality: the platform isn't broken—it's just expensive in ways that don't show up on an invoice.
Not the license fee. The reporting lag, the manual commission workarounds, the spreadsheets your finance team runs every month because MyAffiliates or Income Access can't calculate NGR the way your deals are structured.
The platform isn't broken. That's the problem. It's just expensive in ways that don't show up on an invoice.
This article breaks down what a migration actually costs, how to run one without losing attribution or affiliate trust, and why the switching cost conversation is probably already overdue.
Your affiliate platform works. Tracking fires, commissions calculate, partners get paid. The migration conversation keeps getting delayed anyway, buried under a spreadsheet estimating what it would cost to move. The platform is not broken. It just costs more to stay than to leave, and that cost stays invisible until someone adds it up.
Switching costs are the full set of expenses, risks, and operational disruptions an operator absorbs when moving from one affiliate or analytics platform to another. Not just the new license fee, but the engineering time, tracking gaps, commission disputes, and affiliate trust erosion that follow a poorly planned cutover. In iGaming, these costs run structurally higher than in most other verticals because the platform sits at the intersection of real-money player data, affiliate commission calculations, compliance reporting, and first-party attribution.
A sportsbook running 200 active affiliates across three states faces different switching costs than a casino operator with 50 high-value partners in a single jurisdiction. The common thread: migration cost scales with the complexity of the data being moved, not just the size of the contract being signed.
Teams delay migration not because the current platform is good, but because switching feels harder to justify than staying. That inertia compounds. What starts as a reporting lag or a manual commission workaround becomes the accepted way of working, and the switching conversation gets pushed to next quarter.
AK Bets Affiliates, running on Income Access, updates statistics once per day at around 15:00 GMT. PartnersCasa, using NetRefer, refreshes daily at roughly 11:00 GMT. RevMasters, on MyAffiliates, processes most stats at 6am EST for the prior day. These are not edge cases. They are the documented update cadences of live affiliate programs.
Reporting lag is the gap between when a player event occurs and when it appears in the affiliate dashboard. In a vertical where player quality signals emerge within the first week of acquisition, a day-old dashboard means teams are reacting tomorrow to what happened today. Channel and partner decisions made on stale data compound into wasted spend over weeks and months.
NGR (Net Gaming Revenue) is gross player revenue minus bonuses, jackpot contributions, payment processing fees, and other deductions. Even when a platform claims to support RevShare, the underlying calculation depends on finance data that lives outside the affiliate system. One affiliate analytics importer, Voonix, notes that in certain integration scenarios, "signups can't be imported and Revshare income and CPA income will be mixed in the REV Income column" due to API limitations. That ambiguity is exactly what forces manual splitting and reconciliation outside the platform.
Platforms that cannot natively model NGR-based RevShare, negative carryover (the practice of carrying a negative NGR balance forward into the next commission period rather than resetting to zero), or hybrid CPA structures push teams into spreadsheets. Manual workarounds here are not just inefficient. They introduce payout errors that damage affiliate relationships.
Operators expanding into new jurisdictions need platforms with native geo-blocking, KYC workflow enforcement, and audit trail depth, meaning a time-stamped log of every commission change, approval, and affiliate action that regulators can inspect. Platforms that treat compliance as an add-on rather than core architecture create friction that scales with every new market entry. A platform that worked fine in one state becomes a liability when the operator launches in three more.
Legacy platforms attribute players to affiliates based on first deposits or registrations, not long-term revenue. Teams cannot answer whether their top affiliate by volume is also their top affiliate by player LTV. This is the leadership question that triggers the platform conversation: which partners are actually driving profitable players?
The platform is not failing. It is just answering the wrong question.
Most operators underestimate switching costs because they model only the direct costs and miss the indirect ones that accumulate during and after the transition window. Teams that model the full picture before cutover make better decisions than teams that discover the gaps mid-migration.
Getting the new platform live requires more than signing a contract. The direct cost categories operators consistently undercount:
NetRefer and MyAffiliates both publish typical go-live timelines of four to six weeks. The difference in timeline between platforms reflects the difference in integration architecture, though every operator still absorbs the cost of running both systems in parallel before committing to cutover.
The most damaging switching cost in iGaming is not financial. It is the tracking gap that opens when postback configurations break during cutover. Postback is the server-side signal that fires from the operator's backend to the affiliate platform when a qualifying player event occurs, such as a registration or first deposit. If postbacks misfire or stop firing during migration, conversions go unattributed, commissions cannot be calculated, and affiliates begin disputing invoices.
Cookie-based tracking makes this worse. PartnersCasa, a NetRefer-based program, explicitly uses 30-day cookies for attribution. WebKit's Tracking Prevention documentation shows that Safari caps expiry of cookies created in JavaScript on the landing page to 24 hours and disallows third parties from setting new cookies in many cases. A legacy flow that depends on browser-set identifiers persisting for weeks can lose attribution silently, showing up only as unexplained undercounting in the weekly reconciliation.
S2S (server-to-server) tracking bypasses browser cookies entirely by passing a click ID directly between servers. Intelitics documents server-to-server pixels that fire immediately when the system processes the appropriate transaction. Income Access markets a server-to-server event relay system with postback integration and near real-time tracking. MyAffiliates also supports S2S postbacks, though RevMasters clarifies that postbacks are not inherently real-time if the platform processes FTD data once a day.
Attribution gaps do not announce themselves. Teams usually find them in the weekly reconciliation, after the damage is done.
Migrating to a platform capable of connecting marketing spend to downstream player revenue requires operators to surface and clean data they may never have structured before: NGR by player, cohort-level deposit behavior, CAC to LTV ratio (what it costs to acquire a player relative to the revenue that player generates over their lifetime). Teams that skip this step migrate the data but not the intelligence.
Affiliates watch their dashboards daily. If reporting goes dark, numbers change unexpectedly, or payment timing shifts, they redirect traffic elsewhere, sometimes permanently. Affiliate trust does not recover on a platform timeline. It recovers on a relationship timeline.
Affiliate-side signals that indicate trust is eroding:
The migration starts before any new platform is configured. Teams need a complete inventory of what they are moving, a validation sequence that catches attribution gaps before affiliates notice them, and a communication plan that keeps partners informed before they start asking questions.
The migration starts with a complete inventory: affiliate accounts and tier structures, commission deal types (CPA, RevShare, hybrid, tiered), negative carryover logic, player-affiliate attribution records, and historical payout balances. Any commission logic that lives in a spreadsheet or in someone's memory needs to be documented before cutover. It will not transfer automatically.
SubID is the unique identifier appended to an affiliate's tracking link that allows the platform to attribute a player back to the correct partner and campaign. Every active affiliate link must be remapped to the new platform's tracking structure before traffic is redirected, with postback endpoints reconfigured and tested in a staging environment. SubID structures must be consistent across all traffic sources or attribution will break silently.
Parallel running keeps the old platform active while the new one tracks live traffic, allowing teams to compare attribution numbers between systems before committing to cutover. The parallel period typically lasts one full commission cycle so that payout calculations can be validated against both platforms before affiliates are paid from the new system.
If the numbers match, you have confidence. If they do not, you have found the problem before it becomes a dispute.
Before cutover, run through this checklist:
Top-performing affiliates should be briefed individually before the transition begins. The communication should explain what is changing, what is not changing, and what the affiliate needs to do (if anything) to update their tracking links. Affiliates who are surprised by a platform change are more likely to pause campaigns than affiliates who were briefed and prepared.
The right platform does not just perform better today. It is also easier to leave if you ever need to, because your data is portable and your integrations are clean. Teams evaluating platforms should treat future switching costs as a selection criterion, not just current feature fit.
Any platform being migrated to should treat S2S postback tracking as the default, not an option. Cookieless tracking IDs are persistent identifiers assigned server-side that follow a player across devices and sessions without relying on browser cookies, preserving attribution when ITP and third-party cookie deprecation would otherwise break it. Cookie-based tracking creates attribution gaps that worsen over time as browser privacy restrictions tighten.
Platforms with pre-built connectors to major gaming platforms eliminate the custom engineering work that makes migrations expensive. When the integration layer is standardized, switching costs on the next migration drop significantly because data can be exported cleanly and re-ingested by the new platform without custom development. Contrast this with platforms where the integration is bespoke: migrating away from them means rebuilding the connection from scratch.
Pre-built integrations are not just a convenience at onboarding. They are an exit cost at migration.
pLTV (predictive lifetime value) is an AI-generated forecast of a player's long-term revenue contribution, calculated from early behavioral signals like game choices, deposit patterns, and session behavior. Platforms that surface pLTV within 72 hours of acquisition give teams a forward-looking signal that changes how affiliates are evaluated and paid. Teams that have been optimizing on first deposits will need to recalibrate their commission structures when they can suddenly see which affiliates are driving high-LTV cohorts versus low-LTV volume.
Platforms that lock data inside proprietary formats or make export difficult increase the cost of every future migration. API access and data export capability should be treated as non-negotiable platform requirements, not premium features.
|
Capability |
Reduces switching cost |
Why it matters |
|
S2S postback tracking |
Yes |
Attribution survives cutover without cookie dependency |
|
Pre-built PAM integrations |
Yes |
Eliminates custom engineering on both entry and exit |
|
API data export |
Yes |
Clean data portability reduces future migration lift |
|
pLTV and cohort analytics |
Yes |
Surfaces player value signals that justify the migration ROI |
|
Cookie-based tracking only |
No |
Attribution breaks during cutover and degrades over time |
|
Proprietary data formats |
No |
Increases exit cost on every future platform change |
The post-migration audit compares the same time window across both platforms to confirm attribution parity. These are the metrics to monitor in the first full commission cycle after cutover.
Any gap in clicks, registrations, or FTDs signals a postback misconfiguration that needs to be resolved before the next payout cycle. The audit should cover the same calendar period on both platforms so that differences in attribution logic or tracking coverage become immediately visible.
The first commission payout from the new platform should be reconciled against what the old platform would have calculated for the same period. An unexplained commission difference, even a small one, creates the kind of trust damage that takes months to repair. Discrepancies need to be resolved with the affiliate before payment, not after.
The real proof of a successful migration is not tracking parity. It is the new intelligence the platform makes available. The first time a team can see that their highest-volume affiliate is generating players with below-average predicted LTV, the migration has paid for itself. This is the signal the old platform could never surface, and the answer to the leadership question that triggered the migration in the first place.
Switching costs are real, but they are manageable when teams model them before the migration begins rather than discovering them during it. The operators who delay migration longest are usually the ones who underestimated what staying was costing them in reporting latency, manual workarounds, and the leadership questions they could not answer.
If your team is currently spending time reconciling tracking discrepancies, calculating commissions outside the platform, or answering affiliate disputes that should not exist, the switching cost conversation is already overdue.
Three questions to answer before your next platform conversation:
Schedule a demo to see how Intelitics connects every affiliate dollar to downstream player value, and how the migration gets done without the downtime.