Platform
No-code server-side tag manager: how DataCops works
DataCops is a no-code server-side tag manager with 400-day server-side cookies. It captures every real event on your site, removes the bots and fraud, honours consent, and sends only clean conversions to your ad platforms. This page explains the whole system, simply, from the problem it solves to the journey of a single conversion.
In short
Your ads only work as well as the data you feed them. Today most of that data is captured in the browser, where it is blocked, forgotten, or faked. DataCops moves the whole job to your own domain and to the server: it captures every real event, remembers the visitor for up to 400 days, throws out the bots and the traffic that never consented, and sends only clean, correctly attributed conversions to your ad platforms. No code, no container, no developer.The problem
Almost every store and site reports its conversions with a pixel that runs in the visitor's browser. That was fine ten years ago. It is broken now, in four ways at once:
- The data gets blocked. Ad blockers, Safari, iOS, and Brave strip browser pixels, so a large share of your real sales are never reported. The campaigns that are actually working look weak, and you cut the budget that was earning.
- The visitor gets forgotten. Browsers now erase tracking after about seven days. A shopper who clicks your ad today and buys in two weeks looks like a brand new stranger, so the ad that earned the sale gets no credit.
- The data is dirty. A raw pixel fires for bots, click farms, and fake traffic just as happily as for real buyers. You send that to Meta or Google, and it learns to find you more of the same.
- You cannot see what happened. A pixel fires and forgets. It never tells you if the platform accepted the event or dropped it, so a broken conversion path can go unnoticed for weeks.
The result is fewer conversions reported, worse attribution, dirty signal, and no visibility. Every one of these is a data problem, and DataCops fixes all four before a conversion is ever sent.
How it works, step by step
Follow one visitor, from the moment they click your ad to the moment the sale reaches your ad platform. This is the journey every conversion takes through DataCops.
-
1. It runs on your own domain
The DataCops script loads from your own site, not a third-party tracker, so ad blockers, Safari, and Brave cannot strip it. You capture your whole audience, not the slice that survives. See first-party capture.
-
2. It remembers the visitor
Each real visitor is given a 400-day server-side identity, so a return weeks later is still the same person, with their first ad click still attached. See the 400-day server-side cookie.
-
3. It catches the ad click, even when the browser drops it
The click ID that proves which ad drove the visit is captured first-party, and recovered at the edge on the server when the browser would have lost it. See server-side capture.
-
4. It checks the visit is real
Every visit gets one verdict, built from network signals, our own IP intelligence, email checks, and on-page behaviour, before anything is counted. See bot and fraud detection.
-
5. It checks consent
A first-party consent banner decides, for the visitor's region, whether the event is allowed, resolved on the server. See the consent manager.
-
6. It builds one clean event
Whatever the source, the event is assembled into a single record, who it was, their ad click, the value, the consent answer, and the fraud verdict, defined once in Event Manager.
-
7. It delivers, counted once, and logs it
The clean event is sent from the server to every ad platform and tool you have connected, never double-counted, with a log showing what went where and why. See CAPI delivery.
The pipeline
The same seven steps, in one line. Events come in, cross the same checks, and only the clean ones go out.
Everything it covers
DataCops is one connected system, not a bag of plugins. Here is the whole of it, and where to read more on each part.
It captures every event
Page views, add to cart, checkout, purchase, signups, and leads, across your whole site and your Shopify store.
It remembers every visitor
A 400-day server-side cookie keeps a returning shopper recognised long after the browser would have forgotten them, with their first ad click attached.
It checks every visit is real
Bots, click farms, VPNs, proxies, datacentres, and fake or disposable emails are caught by our own fraud, IP, and email services before anything counts.
It honours consent
A first-party consent manager decides, per region, whether an event is allowed, and holds the ones that were not opted in.
It sends clean conversions everywhere
The same clean event is delivered server-side to your ad platforms and, as real contacts, to your CRM and email tools.
It shows you everything
Clean, bot-filtered analytics of your real traffic, plus a delivery log of exactly what was sent to each platform and why.
Core concepts
If you read only four pages, read these. They do most of the work.
Why clean data wins
A conversion you send to Meta or Google is not just a number in a report. It is a lesson for the ad platform. Send it a bot and it learns to find more bots, and you pay for more fake traffic. Send it one real, verified buyer and it learns to find more real buyers.
That is the whole point of everything above. Every conversion that leaves DataCops has been captured on your own domain, tied to a real remembered person, checked for fraud, and checked for consent, first. Clean data in, better results out.
Send a conversion
If you would rather send events yourself, it is one request with your private key. DataCops checks it, matches it to the right person, and delivers it to every platform you have connected. No code changes on your site.
curl -X POST https://api.joindatacops.com/api/v1/conversions/zapier \
-H "x-dc-key: dcp_your_private_api_key" \
-H "Content-Type: application/json" \
-d '{
"event": "Purchase",
"messageId": "order-1001",
"properties": { "value": 49.0, "currency": "USD", "order_id": "1001" },
"context": { "traits": { "email": "[email protected]" } }
}'