Postbacks for a TDS: how a sale on the offer's site finds its click
The TDS Worker sends a visitor to the offer and sees nothing after. A signed click token and a postback bring the sale back to the rule, the split and the ad network.
How a TDS on Cloudflare Workers sorts traffic before it reaches your server
Your domain can point at any host and still have every visitor sorted by country, device and bot class first. How the 301.st TDS does it, step by step.
A unique click id on a free Cloudflare redirect, no Worker involved
uuidv4() is banned in redirect targets, but cf.ray_id is not: a Single Redirect can stamp every click with its own id. Measured live, with the traps.
The conversion fires on someone else's domain. Here is how to attribute it.
Years of unanswered threads, even a €100 bounty on the question. The loop that closes it: a redirect hop that mints a click_id and takes the postback.
A redirect runs no JavaScript. Here is how to count the click anyway.
Web Analytics, Plausible and Umami are page beacons, so a 301 is invisible to all of them. A Worker plus Analytics Engine counts it on the free plan.
Your redirect is eating the gclid. Here is the 60 second test.
Google Ads flags redirects that drop click IDs and tells you to ask IT. Here is how to find the hop that drops them yourself, with curl, in about a minute.