Platform
Server-side capture
DataCops captures from two places that never depend on each other: the first-party script on the page, and an optional edge worker that grabs the ad click before the browser can throw it away.
What it is
Server-side capture means DataCops records a visit and its ad click from your own infrastructure, not just from a script in the browser. The first-party script does most of it. For the clicks that vanish fastest, an optional Cloudflare Worker sits at the edge and catches the ad click the instant the visitor arrives, before iOS or Safari can strip it from the link.Two collectors, one clean record
There are two collectors and they never talk to each other, which is what makes this reliable. The first-party script runs on the page. The edge worker runs before the page, at Cloudflare. If one misses something, the other still has it.
DataCops joins the two on its server using the visitor's network address, browser, and a short time window, so the two halves become one clean record for the same visit. The ad click captured at the edge is attached to the visitor the script identifies. You never see two entries for one person.
What the worker recovers
Some visits leave before the page script can run, and some browsers strip the ad click from the link the moment the page loads. The worker sits earlier than any of that. On every real page view it reads the ad click IDs and campaign tags from the link and sends them to DataCops. It covers every major platform's click ID, so nothing is missed no matter where the traffic came from. A plain visit with no ad click is left completely alone.
The worker never blocks or slows the page. It hands the visitor straight to your site and does its work in the background. Bot detection is not its job. Your page script stays the final word on whether a visit is real.
Set it up
The edge worker is optional and takes about five minutes. You paste one ready-made Cloudflare Worker, set two variables, and add a route. The full worker code and the step-by-step setup live in the developer docs.