Most operators assume the hard part of affiliate tracking is the build. It isn't. The hard part is everything that comes after.

How many operators have handed an engineering team a 12-month build timeline for affiliate tracking, then watched it quietly become a permanent line item?

The real challenge isn't the initial build. It's everything that comes after: commission disputes, compliance updates, postback failures, and a reporting portal that affiliates complain about every time they log in.

Generic platforms like Impact, TUNE, and Partnerize weren't built for this. They model a world where a conversion happens, a commission locks, and a payout follows. iGaming doesn't work that way.

This piece breaks down what a production-grade iGaming affiliate system actually costs to build, what it costs to maintain, and why platforms like Intelitics—with hundreds of pre-built integrations and a typical implementation window under 30 days—change the math on the build vs. buy decision.

Build vs. buy is fundamentally different in iGaming

Most operators approach affiliate tracking as a solved problem. They've seen it work in e-commerce, watched SaaS companies scale partner programs on generic platforms, and assume the same tools will translate. They don't.

A player's value unfolds over months or years, not in a single checkout event. Commission structures tie to net gaming revenue after deducting bonuses, taxes, processing fees, and chargebacks. Regulatory requirements change multiple times per year across jurisdictions. Generic affiliate platforms model the world around a conversion with a fixed payout. iGaming requires a system that tracks player behavior over time, applies configurable revenue formulas, and produces auditable commission statements that survive disputes.

The system requirements that don't exist in other verticals

Your affiliate manager is fielding a dispute from a top partner whose numbers are off by 15%. The commission calculation involves NGR deductions, a negative carryover clause, and three months of player activity across two devices. A generic platform wasn't built for that conversation.

A production iGaming affiliate and analytics tracking system handles requirements that don't exist in other verticals. These aren't edge cases. They're the baseline:

• FTD tracking (First-Time Depositor): Attributing a player's first deposit to the correct affiliate in real time, across devices. A player clicks an affiliate link on mobile, registers on desktop, and deposits days later on an app. The system connects those events without cookies.
• NGR-based commission calculation (Net Gaming Revenue): Deducting bonuses, taxes, and fees from gross revenue before calculating what an affiliate is owed. The formula differs by operator and changes with regulatory updates. One operator deducts processing fees and bonuses. Another includes game supplier costs and chargebacks. The system has to support contract-specific deduction logic, not a universal percentage.
• RevShare and CPA structures: Often running simultaneously across different partner deals. One affiliate earns 30% of NGR with negative carryover. Another earns a flat $150 CPA. A third gets a hybrid structure with tiered CPA based on deposit volume. The platform calculates all three models in parallel and reconciles them monthly.
• Negative carryover logic: Determining whether a player's net losses in one month offset the next month's commission. That's a commercial decision the system must enforce automatically, with an audit trail that survives disputes.
• S2S postback tracking (Server-to-Server): Passing conversion events directly between servers, not through a browser. Cookie-based tracking breaks under the conditions common in iGaming: ad blockers, cross-device play, and long attribution windows.

Generic tools break down on iGaming economics

Platforms built for e-commerce calculate a flat percentage on a confirmed transaction. The order is complete, the commission is locked, and the payout happens on a fixed schedule.

Impact defines an action as a conversion that goes pending then locked, with a payout tied to that action cost. TUNE's payout logic examples are e-commerce and SaaS style, with product-level payout assignment by passing a SKU back on conversion. Partnerize defines variable commission as a percentage of revenue or conversion and bonus commission as a flat amount. All three align to retail order economics, not iGaming player economics.

The gap shows up when an operator needs to deduct third-party game supplier fees from NGR before calculating affiliate commission, or when a player's negative net position in one month needs to carry forward to the next. Generic platforms can be flexible on payout rules, but they're not built around an iGaming-grade NGR ledger that ingests wagering, wins, bonus cost, and provider fees at the right grain, applies contract-specific deduction logic, and supports audit trails for why a partner got paid a specific amount. Purpose-built iGaming platforms collect player wagering economics at player level, including bets, wins, GGR, bonuses, third-party fees, and NGR, and send NGR postbacks. Generic tools don't.

If it needs a workaround to scale, it doesn't scale.

The true cost to build in-house exceeds initial estimates

Your engineering lead quotes 12 months and a team of four. That estimate is probably missing two years of what comes after.

The budget conversation focuses on the engineering team and the build timeline. The three-year total cost of ownership (TCO) includes compliance maintenance, ongoing integration work, fraud detection iteration, and the opportunity cost of engineering capacity diverted from the core product.

The first build costs $1.5M to $4M or more

Using 2024 U.S. median salary benchmarks from the Bureau of Labor Statistics, a lean MVP team includes one engineering manager or architect at $171,200 annually, three full-stack engineers at $133,080 each, one QA analyst at $102,610, one DevOps engineer at $133,080, and one project manager at $100,750. That's roughly $906,880 in annual base wages.

Employer costs for employee compensation show that wages are about 70% of total compensation and benefits about 30%, implying a loaded multiplier of approximately 1.42 times wages. Annual loaded compensation runs around $1.29 million. Over 12 to 18 months, that's $1.29 million to $1.94 million in loaded labor before non-labor overhead.

A more realistic production-grade build team adds two engineers to handle data and attribution logic, pushing annual loaded compensation to around $1.86 million. Over 12 to 18 months, that's $1.86 million to $2.79 million in loaded labor.

Non-labor costs typically add 15% to 35% of loaded labor, covering recruiting, cloud infrastructure, data warehouse, security review, penetration testing, and ongoing integrations with brands, payment and KYC events, and BI exports. The practical all-in build TCO for 12 to 18 months ranges from roughly $1.5 million to $4 million or more, depending on team size, location, and compliance scope. That's before year two maintenance.

Maintenance costs compound after launch

Launch is when the real cost clock starts. The ongoing cost categories that operators underestimate are the ones that surface only after affiliates are actively using the system with real money.

Compliance updates happen multiple times per year across jurisdictions. The UK Gambling Commission's LCCP change log shows roughly four to five formal updates per year over 2024 to early 2026. The UKGC also moved many licensees to quarterly regulatory returns effective July 1, 2024, forcing changes in how operators aggregate, retain, and export data. The Malta Gaming Authority issued an update to incident reporting requirements in April 2024 that changed the incident report mechanism via the licensee portal. In the U.S., the Michigan Gaming Control Board issued multiple technical bulletins in 2024 covering data logging, server and equipment location, and geofencing specs. Each update can require system-level modifications to reporting logic, data handling, or commission controls.

S2S postback maintenance requires ongoing work. Every new affiliate integration or tracking partner change requires postback reconfiguration and debugging, and affiliates use different tracking platforms with different event format requirements.

Commission model expansion requires schema-level changes, not configuration. Adding hybrid structures, tiered CPA, or sub-affiliate splits means new database fields, new calculation logic, and new reporting layers for both internal teams and affiliate portals.

Fraud detection requires continuous refinement. Bonus abuse, self-referral, deposit-and-withdraw schemes, and traffic arbitrage all require detection logic that adapts to new tactics.

Data reconciliation is a recurring engineering task. Matching FTD and NGR data across the game platform, CRM, and affiliate system requires ongoing work to handle late-arriving events, duplicate player records, currency conversions, and adjustments for chargebacks or bonus corrections.

Knowledge concentration risk compounds every time the team turns over. The engineers who built the core commission logic take the institutional knowledge with them, and the next engineer has to reverse-engineer why certain decisions were made.

Engineering stops building revenue-generating features

Every sprint cycle spent on affiliate infrastructure is a sprint cycle not spent on the product that generates revenue.

Operators who build in-house consistently report that affiliate engineering becomes a permanent tax on their product roadmap, not a one-time investment. The team that was supposed to ship new game integrations, improve retention features, or build predictive player segmentation is instead debugging postback failures, updating commission formulas, and responding to affiliate disputes.

Hidden costs break the business case

The costs in the previous section are visible if you look for them. These ones surface only after the system is live, and by then the budget decision has already been made.

Attribution failure triggers disputes and lost volume

A missing parameter causes an entire campaign's conversions to go untracked. The affiliate's numbers and the operator's numbers diverge. The affiliate notices first.

Attribution failure means any event where a player action, such as a registration, deposit, or wager, is not correctly linked to the partner who drove it. While iGaming-specific time-waste benchmarks are scarce, commission-based ecosystems show measurable reconciliation overhead. A CaptivateIQ report citing Alexander Group survey work states that 53% of sales managers surveyed spend two to three days resolving questions or disputes each pay period. In iGaming, the risk is plausibly higher because commissions are based on NGR, deductions, and adjustments rather than simple order value.

Affiliates who experience unexplained commission adjustments reduce their promotional effort and, in competitive markets, redirect volume to operators with cleaner reporting. Speed is useless if the data is wrong.

Commission logic is harder than it looks

Negative carryover logic, multi-currency NGR reconciliation, and player-level revenue adjustments all create edge cases that only surface under real production load, not in testing.

One operator might define NGR as gross revenue minus processing fees, bonuses, taxes, and chargebacks. Another might include payment processing fees, bonuses, loyalty rewards, gaming taxes, game supplier costs, and chargebacks. The system has to support both formulas, plus every variation in between, and produce audit trails that explain why a specific partner got paid a specific amount in a specific month. Operators who build in-house typically discover these edge cases during affiliate disputes, not during QA.

Jurisdictions and brands multiply cost

Each jurisdiction, whether MGA, UKGC, or individual U.S. states, may require separate reporting logic, data storage rules, or affiliate disclosure controls. Each brand requires isolated tracking, brand-specific commission structures, and separate affiliate portals.

Multi-brand, multi-jurisdiction operators are precisely the profile where in-house build costs diverge most sharply from initial estimates. The system that worked for one brand in one market has to be extended to support multiple brands in multiple markets, each with different regulatory requirements, different commission structures, and different affiliate relationships.

Analytics work gets underestimated

Affiliate tracking tells you who sent the player. Analytics tracking tells you what that player is worth. Connecting affiliate attribution to downstream player value, including deposits over time, NGR contribution, and churn behavior, requires a separate data layer that most build plans treat as a later phase. In practice, it is the capability that leadership most frequently asks for first.

Intelitics' pLTV capability generates reliable predictive lifetime value within 72 hours of acquisition. That's the specific outcome operators are trying to build toward, and the one that takes longest to replicate in a custom system. The analytics layer has to ingest player behavior data from the game platform, normalize it across brands and products, apply predictive models to forecast lifetime value, and expose those predictions to both internal teams and ad platforms for optimization. That's a separate engineering effort that extends the build timeline and adds to the ongoing maintenance burden.

Custom builds take 12–18 months; platforms launch in weeks

Time-to-market is the clearest differentiator between the two paths, and also the cost that is hardest to quantify on a spreadsheet. Every month the system isn't live is a month where budget allocation is based on incomplete data.

External dependencies slow in-house builds

Your engineering team controls the code. They don't control the game platform vendor's API documentation timeline, the regulator's certification queue, or the affiliate's expectations for a reporting portal that doesn't look like it was built in 2019.

Specific factors extend iGaming affiliate build timelines beyond initial estimates:

• Regulatory certification: Some jurisdictions require system-level approval before the tracking layer can go live, adding months outside the engineering team's control.
• Integration complexity: Connecting to platforms like GiG, Playtech, or White Hat Gaming via push or pull APIs requires coordination with the platform vendor, understanding their event schema, and testing under production load.
• Edge case discovery: Commission logic edge cases surface when real affiliates use the system with real players and real money, requiring rework after launch rather than during QA.
• Affiliate portal UX: Affiliates compare the operator's reporting portal to every other platform they work with. A subpar experience delays partner recruitment even after the system is technically live.

SaaS platforms launch in weeks to months

A purpose-built iGaming affiliate and analytics platform with pre-built integrations to major game platforms and ad channels can be deployed in weeks to low single-digit months, depending on commission structure complexity.

Intelitics offers hundreds of pre-built channel integrations and typically implements in under 30 days. The platform connects to the operator's game platform via existing APIs, ingests player data, normalizes it across brands and products, and starts tracking affiliate attribution and player value without requiring the operator's engineering team to build or maintain the integration layer.

Delayed insight compounds misallocation

Affiliates who would be deprioritized under LTV-based measurement continue receiving spend. Channels that look productive on a CPA basis but generate low-value players continue to scale.

The gap between what the marketing team believes about performance and what is actually true widens every month the system is delayed. The operator is paying affiliates based on first deposits, not lifetime value. The affiliates who drive high-volume, low-value players get the same or better treatment than the affiliates who drive lower-volume, high-value players. That misallocation compounds.

In-house builds make sense for a narrow operator profile

There are specific operator profiles for whom building in-house is a rational decision. Most operators do not match that profile.

Operators who should consider a custom build

The conditions under which building makes sense are narrow and testable. Use this as a filter, not a justification:

• Dedicated engineering headcount: A permanent team whose sole job is to build and maintain the affiliate tracking system, not borrowed capacity that gets reassigned when the next product deadline hits.
• Single regulated market: If the operator is only licensed in one market with no expansion plans, the compliance update frequency is lower and the system can be optimized for that market's specific requirements.
• Genuinely unreplicable commission logic: Deal structures that no existing platform can accommodate even with configuration, not just unusual structures, but ones that are architecturally incompatible with any available tool.
• Strategic intent to commercialize: A long-term plan to license or resell the tracking technology as a separate product line, giving the build investment a different ROI calculation.

Operators who meet at least two of these criteria have a legitimate case for building. Operators who meet fewer than two are likely underestimating the ongoing cost.

Most operators should buy instead

Operators scaling player acquisition across multiple channels, entering new markets, managing a growing affiliate partner base, and asking which partners drive profitable players rather than just first deposits are the operators for whom a purpose-built platform delivers faster time-to-value than any in-house build can match.

Intelitics is purpose-built for exactly this operator profile: fast-scaling sportsbook and iGaming brands running complex, multi-channel acquisition programs who need to tie every marketing dollar to downstream player value.

The decision framework: three-year TCO comparison

The decision framework matters more than any single cost figure. A three-year TCO comparison is the right unit of analysis, not the initial build cost vs. the annual SaaS fee.

The TCO scorecard includes hidden cost categories

The build path's costs are front-loaded in perception but back-loaded in reality. The initial estimate captures the first 12 to 18 months of engineering work. The ongoing costs surface after launch and continue indefinitely.

For the build path, include:

• Initial engineering salaries, including backfill for pulled capacity
• Infrastructure and hosting
• Compliance maintenance per jurisdiction, ongoing
• Affiliate portal UX investment
• Fraud detection development and iteration
• Opportunity cost of engineering diverted from core product

For the buy path, include the platform subscription or licensing fee, integration and onboarding cost, and any customization required beyond standard configuration. The buy path's costs are more predictable. The subscription fee is fixed, the integration cost is one-time, and the vendor manages compliance updates and fraud detection as part of the service.

A bought platform must prove these capabilities

Not all purpose-built platforms are equal. Verify these capabilities before committing:

• NGR formula flexibility: Can the platform support your specific deduction logic, or does it impose a fixed formula? Ask to see how the platform handles contract-specific deductions like payment processing fees, bonuses, loyalty rewards, gaming taxes, game supplier costs, and chargebacks.
• Negative carryover support: Is this native, or a workaround? Ask to see how the platform handles a player who generates negative net revenue in one month and positive net revenue in the next.
• S2S postback reliability: What is the documented uptime and error rate on postback delivery? Ask for SLA documentation and examples of how the platform handles postback failures and retries.
• Multi-brand and multi-geo isolation: Can commission structures, affiliate portals, and reporting be fully separated by brand and jurisdiction?
• pLTV integration: Can the platform connect affiliate attribution to downstream player value, or does it stop at first deposit?
• Pre-built game platform integrations: Which platforms are supported natively, and what does a new integration require?

Operators can reduce migration risk with parallel tracking

Switching anxiety is the primary objection that keeps operators on stale in-house systems or legacy platforms longer than they should be.

Migration risk is real but manageable when the vendor runs a parallel tracking period before cutover, provides documented data migration protocols, and has specific experience migrating live affiliate programs without breaking commission continuity. Intelitics' implementation process is designed to run parallel tracking during the transition window, with pre-built integrations to major game platforms that reduce the integration negotiation cycle. Implementation typically completes in under 30 days.

Conclusion

For most iGaming operators, the three-year total cost of building in-house affiliate and analytics tracking exceeds the cost of a purpose-built platform by a significant margin once compliance maintenance, engineering opportunity cost, and the analytics layer are included in the comparison. The operators for whom building makes sense are a narrow profile.

Before the next budget cycle, run the TCO comparison with all cost categories included, not just the initial build estimate. If the math is closer than expected, the compliance and opportunity cost categories are likely missing from the calculation.

Next step: Request a demo to see how Intelitics calculates three-year TCO for your specific operator profile.