Definition
A TDS, or Traffic Distribution System, is software that sits between an incoming click and its final destination and decides, per click, where to send it - based on rules such as GEO, device, operating system, browser language, traffic source, time, referrer, or a percentage split. It logs each click, applies filters, and routes accordingly, functioning as a programmable switchboard for traffic.
TDS software is dual-use. Legitimate uses include A/B split-testing of landing pages, routing users to the offer that is available and pays best in their country, sending mobile and desktop users to different pages, load-balancing, and filtering out obvious bot or proxy traffic before it hits a paid funnel.
The same capability also underpins cloaking - showing moderators, crawlers and rejected geos one page while sending everyone else to another - which is why TDS links on ad landing URLs attract scrutiny.
In context
In iGaming media buying, a TDS (standalone, or the routing layer inside a tracker like Keitaro) is standard infrastructure. Buyers use it to run several prelanders and landing pages in a controlled split, to geo-route a single campaign link across multiple operator offers, to keep a campaign live via failover when one landing page has an outage, and to pre-filter traffic so that data-centre IPs and known bad sources do not consume optimisation budget.
The compliance line is the same as for cloakers and rotators. Routing among disclosed, legitimate offers that all match the ad's promise, or splitting traffic for a genuine test, is normal optimisation.
Configuring the TDS so that the ad network's review systems see a compliant "white" page while real users are sent to the actual gambling offer is cloaking - a breach of platform terms that, in gambling, can stack with licensing and consumer-protection violations. Networks and operators test landing URLs from multiple geos, devices and crawler signatures specifically to detect TDS-driven divergence, so a TDS setup that behaves differently under review conditions is a direct risk to the account and the partnership.
Worked example
A buyer uses a TDS to split push traffic evenly across three prelanders for the same casino offer, geo-route to the correct operator per country, and drop data-centre IPs. All three prelanders carry the same offer and disclosures; the routing is testing and localisation, not cloaking, and behaves identically whether the visitor looks like a user, a crawler or a reviewer.
Related terms
Frequently asked questions
Browse more iGaming terms in our glossary.
← Back to glossary