Trafficback
Trafficback is the URL or page that non-target traffic gets routed to — bots, moderator/reviewer visits, wrong-geo clicks, duplicates, and other filtered-out hits. Instead of losing that traffic entirely, it lands on a safe page rather than the real offer.
What trafficback is for
It solves two problems at once: it hides the real landing page or PWA from a moderator or an anti-fraud bot, and it gives a rejected click somewhere to go — a content page, a banner, or a push opt-in — so even filtered traffic can be monetized to some degree.
Trafficback in PWA arbitrage
Paired with cloaking, trafficback is essential: the cloak checks each click and decides whether to show the real offer to a genuine user in the target geo or send them to trafficback instead. APEX builds this into its cloaking+anti-bot layer — bot/UA/datacenter/geo filters route unwanted traffic automatically, with no separate service to configure.
FAQ
- Where does trafficback usually point?
- Most often a neutral content page, a local-language info site, or a push opt-in page — something safe that won't raise a moderator's suspicion and won't expose the real offer.
- Can trafficback traffic be monetized?
- Partially, yes — you can run ads or collect push subscribers on the trafficback page, though its main job is protecting the real offer from moderation and off-target traffic, not generating revenue on its own.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free