TDS
A TDS (Traffic Distribution System) routes traffic: it takes in a click and, based on rules — geo, device, OS, source, caps, time of day — decides where to send it: a specific landing page, offer, PWA flow, or trafficback.
How a TDS works
A TDS typically sits between the ad network and the final page: it receives a click with its parameters (sub-ID, IP-based geo, user agent), checks them against configured rules and caps, and redirects in real time — to the right flow, into a split test, or to trafficback if the click doesn't qualify.
TDS in PWA arbitrage
A dedicated tracker (Keitaro, Binom, Voluum) often plays this role, but basic routing — geo filters, anti-bot checks, visitor-sticky split tests — can be covered by APEX's built-in tools without a separate service, leaving an external tracker necessary only for complex multi-flow setups.
FAQ
- Do you need a separate TDS in front of a PWA?
- Not for a simple setup — one offer, one or two geos: built-in filters and split tests are enough. A dedicated TDS/tracker earns its keep once you're running many flows, sources, and offers at once.
- What's the difference between a TDS and cloaking?
- Cloaking specifically checks whether a hit is a bot or a human, a moderator or a real user, before showing the offer. A TDS is the broader concept of routing traffic by any rule — cloaking is usually just one function living inside a TDS.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free