Platform
No-code server-side tag manager
Pick a goal, map it to an ad-platform event in plain language, connect your ad accounts. Events flow server-side from your own domain, bot-filtered and consent-gated, with no container to host and no tags to wire.
What it is
A server-side tag manager sends your conversions to ad platforms from a server you control, instead of from the visitor's browser. DataCops is a no-code server-side tag manager: you choose a goal in the Event Manager, map it to a standard ad-platform event, and connect your ad accounts. There is no container to host and no tags to wire by hand.Old-style tracking runs in the browser, where ad blockers, Safari, and Brave strip a large share of it. Sending from a server on your own domain fixes that. The conversion leaves your side cleanly, every time.
Why the old way is hard
Server-side is not new. Google has a server-side version of Tag Manager. The catch is that it is built for engineers. To run it you have to stand up and pay for a tagging container, keep it running, and wire every tag, trigger, and variable by hand. Teams often spend one to two weeks on it.
And even after all that, it still forwards whatever it is given. It cannot tell a bot from a buyer, and it cannot hold a conversion back until you know it is real.
The Event Manager flow
DataCops replaces the container, tag, trigger, and variable wiring with a goal-first flow. The Event Manager is one list of every conversion you track, and it is configuration, not traffic. You describe what you want, and the DataCops script fires it.
-
Install once
Add the DataCops script and point a subdomain of your own domain at it. Collection now runs first-party, so it survives ad blockers and Safari.
-
Open the Event Manager
Every conversion in one place, with columns for the event, the page, what it sends as, and its status.
-
Choose a capture mode
Let the DataCops Pixel pick up your forms on its own, point and pick an element, use a hosted form, or turn on SignupCops. See the four modes below.
-
Map it to an ad-platform event
In plain language. For a goal like Signup or Purchase, DataCops chooses the standard event for you.
-
Connect your ad accounts
DataCops sends to 8 ad platforms. Meta, Google Ads, TikTok, LinkedIn and X connect with a sign-in. Microsoft Ads, Reddit and Pinterest connect with an API key. Every qualifying event fans out to all of them.
From then on, each captured conversion becomes one clean event, passes the consent and fraud gates, and is delivered server-side to every connected platform. You never wire a tag or a trigger.
Capture modes
The Event Manager offers four ways to capture a conversion. Use as many as you need.
| Mode | Type | What it captures |
|---|---|---|
| DataCops Pixel | Automatic | Finds the forms and buttons already on your site and captures every ad click ID on arrival. A real form submit becomes the conversion. Nothing to scan or set up. |
| Select manually | Point and pick | Point at any form, button, or page on your live site and name it. No code and no selectors. |
| Hosted form | Hosted | A form hosted by DataCops that carries first-party identity. Every submission is a Lead and comes with a risk score. |
| SignupCops | Signups | Captures signups the browser pixel cannot see, like Sign in with Google. Sent server-side and delivered as CompleteRegistration. |
What each goal sends
When you pick a goal, DataCops maps it to the standard event your ad platforms expect, so you do not have to know the exact event names.
| Your goal | Sends to your ad platforms as |
|---|---|
| Book a demo | Schedule |
| Signup | CompleteRegistration |
| Contact or lead | Lead |
| Purchase | Purchase |
| Add to cart | AddToCart |
| Something else | You choose |
Hosted forms always send as Lead. SignupCops always sends as CompleteRegistration.
What happens to each event
In server-side GTM, a tag fires and the data goes out. In DataCops, every captured conversion passes a fixed set of steps on the server first. You do not build these steps. They are the same for every site.
| Step | What it does | Default |
|---|---|---|
| Capture | The DataCops script records the conversion on your own subdomain and keeps the ad click id that brought the visitor. | On |
| Consent | The server re-checks the visitor's consent before every send. The built-in banner shows in Europe, and Google Consent Mode v2 is on. | On |
| Real people only | Blocks bots and datacenter traffic from a platform. VPN, proxy and Tor blocking are optional. | Off, set per platform |
| Destination rules | Leave a platform out of an event, or send only when a field matches a rule. | Send to all |
| Deduplication | A repeated order is caught before anything goes out, and each event carries one steady id across all platforms. | On |
| Delivery | Sent server-side to each connected platform in the format it expects. | On |
Every send, and every skip with its reason, is written to the delivery report. You can see exactly what each platform received and why anything was held back. In GTM you would need a separate logging setup for that.
Hold until qualified
Because delivery happens on the server, DataCops can wait before it sends. For lead businesses this is the biggest difference from a browser tag. A form fill is held, and only sent to your ad platforms once your CRM says the lead is good.
- HubSpot is checked every 5 minutes for leads that moved to a qualified stage.
- Any other CRM can release a lead through the qualification gate API, or send deals in through the DataCops webhook. Salesforce and Pipedrive connect this way, directly or through Zapier, Make or n8n.
- A held lead that is never released expires after 14 days and is not sent.
Your ad platforms then learn from leads that turned into real opportunities, not from every form fill.
DataCops vs server-side GTM
Same goal, very different amount of work.
| Server-side GTM | DataCops | |
|---|---|---|
| Server | A tagging container you host, pay for and keep running | Runs on a subdomain of your own domain, nothing to host |
| Setup | Tags, triggers and variables built by hand | Pick a goal in plain language |
| Bot filtering | Forwards whatever it is given | Real people only, per platform |
| Consent | A separate consent tool to connect | Built-in banner, re-checked on the server before every send |
| Waiting for the CRM | Not possible, the tag fires at once | Holds leads until qualified |
| Destinations | One tag per platform | One event fans out to all 8 platforms, counted once |
| Proof of delivery | Build your own logging | Delivery report with every send and skip |
DataCops also covers the parts around the tag manager: first-party capture, the consent manager, bot and fraud detection and offline conversions from your CRM. One tool replaces the stack.
Good to know before you start
- Install the DataCops script once and point one subdomain at it. That is the only technical step.
- Real people only starts off. Turn it on per platform when you are ready.
- Turn off a platform's own browser pixel for the events DataCops sends, so the same conversion is not reported twice.
- Shopify stores can use the DataCops Shopify app instead of the script.