Server Side Tracking, No Container to Build

Server-Side Tag ManagerYour Own Subdomain
8 Ad PlatformsBots Kept OutEvery Send Logged

Server side tracking sends your conversions from a server, so blockers and browser limits stop hiding them. DataCops does it with one script on your own subdomain and one DNS record. No GTM server container, no tagging server to host, no developer.

Setup in 5 minutes
No credit card

Every conversion, online and offline, checked before your ads learn from it

CaptureClean & RouteDistribute · CAPIInvalid trafficWebsiteForms · LeadsCheckoutSignupsCustom event+ any eventBot · VPN · Consent · ScoreMeta CAPIGoogle AdsTikTokLinkedIn+ every CAPIQualified?HighLevelShopify+ any CRM
trafficverifiedpendingconfirmedinvalid

Trusted by agencies and brands running paid media

AffilinoBigfishClever DigitalKeetraxLegendListingLogicNumeroStormZealdBurst Digital
Definition

What is server side tracking?

Server side tracking means your conversion events reach the ad platforms from a server, not only from a pixel in the visitor's browser. A browser pixel can be blocked, cut short by privacy limits or lost when the tab closes. A server-to-server send is not, so every ad platform you use hears about more of the sales and leads that really happened, and bid on better data.

DataCops is a server-side tag manager you do not have to build. One script loads from your own subdomain, set up with one DNS record, and DataCops runs the server that sends each event to every ad platform you connect, logged row by row.

DataCops is a no-code server-side tag manager: one script and one DNS record send your conversions server-side to eight ad platforms, checked for bots and consent.

Where each event goes

Browser pixel only
What your ads see today Visit Blocked or lost
With DataCops Visit Blocked or lost
Server-side GTM
What your ads see today Web container Your tagging server Ad platform
With DataCops Web container Your tagging server Ad platform
DataCops
What your ads see today Your subdomain DataCops server Ad platform
With DataCops Your subdomain DataCops server Ad platform
Why pixels miss

Why browser tracking loses conversions

Your ad platforms can only optimize on the conversions they receive. A pixel alone drops more of them every year.

Booking form
Name
Maria Lopez
Meta
Treatment
Root canal
Meta
Email
maria@mail.com
Meta

Blockers strip the pixel

Ad blockers and privacy browsers stop known tracking domains, so the purchase happens and the ad platform never hears about it.

The ad click, in the browser
Day 1Ad click saved
Day 8Safari clears the cookie
Day 23Deal won
No click left to match

The click is forgotten

Safari clears cookies set by a browser script after 7 days. A buyer who comes back next week looks like a stranger.

Leads sent to your ads
Real lead Counted
Bot lead Counted
Real lead Counted
Your ads now look for more bots

Bots are counted as people

Fake visits and form spam fire the pixel too, and every one teaches the campaign to find more of the same.

Events Meta received
Lead Received
Booked call Never seen
Deal won Never seen
The pixel stops at the form

No pixel sees what happens next

Once the visitor leaves the page, the pixel is done. Anything after that is invisible to it.

How server side tagging works in DataCops

The same idea as server-side GTM, with the server already running.

  1. Step 01
    Saved on yourdomain.com
    fbclid from Meta Kept
    gclid from Google Ads Kept
    ttclid from TikTok Kept
    Kept for up to 90 days

    The script loads from datacops.yourdomain.com and keeps the ad click ID on your own domain for up to 90 days.

  2. Step 02
    Cookie on yourdomain.com
    Set byYour own server
    Lasts 7 days 400 days

    A first-party visitor ID ties return visits together. Switch on durable identity for a server-set cookie of up to 400 days.

  3. Step 03
    Event match quality
    Good Poor
    Fewer conversions matched to a person

    A purchase, lead or signup is matched to the click ID, with hashed email or phone where you have them.

  4. Step 04
    Won deal sent
    Meta Sent once
    Google Ads Sent once
    TikTok Sent once
    LinkedIn Sent once

    It is checked for bots, consent and duplicates, then sent server-side to every platform you connected.

Every event is sent once per platform, and every send is logged with its status and reason.

What runs on your own domain

Capture Background

One first-party script, served from your own domain

  • Runs first-party from datacops.yourdomain, not a blockable third-party host
  • One script, one CNAME, live in about 5 minutes, no container to host
  • Server-side collection on Cloudflare's edge, close to every visitor
  • Captures click IDs at the network level, so fbclid and gclid still reach your CAPI feed after browsers strip them
  • Recovers 15 to 25% of the sessions other setups lose

Traffic Visibility

10%
20%
30%
40%
50%
60%
70%
80%
90%
100%

First-Party Script

~78%

Blockers and ITP cut your sessions

Server-side tag manager

GTM server side vs a server-side tag manager you do not host

Both move your tags off the browser. One is a project you build and host. The other is already running.

Server-side GTM

What you set up and keep running yourself.

  1. Web container in Google Tag Manager 1
  2. Tagging server on Cloud Run or a hosting service 2
  3. Server container, clients and tags per platform 3
  4. Custom domain pointed at the tagging server 4
  5. Someone to fix it when a platform changes its API 5

Google puts each Cloud Run server at about $45 a month and suggests at least 2 for production.

DataCops

The server is ours. The domain is yours.

  1. One script on your site done
  2. One DNS record: datacops.yourdomain.com done
  3. Connect Meta, Google Ads, TikTok and LinkedIn done
datacops.yourdomain.com  CNAME  (value from your dashboard)
Delivery log
every event, every platform, with a reason
Live
Purchase to Meta
Conversions API
Delivered
Purchase to Google Ads
gclid
Delivered
Lead to TikTok
Events API
Delivered
Lead to LinkedIn
to your mapped conversion rule
Delivered
Lead to Meta
flagged bot, Real people only on
Skipped
Delivery log

Server side tracking you can see

Most server-side setups are a black box until a number looks wrong. DataCops writes one row for every event and every platform.

  1. 1
    One event, every platform
    The same conversion goes to each platform you connected, with its click ID and hashed customer details.
  2. 2
    Nothing silent
    Delivered, held, skipped or failed, with the reason next to it.
  3. 3
    Your bidding stays yours
    Google Ads actions start as secondary until you make one primary.
  4. 4
    Bots kept out if you want
    Switch on Real people only per platform and flagged bots never reach that platform.

DataCops vs server-side GTM vs Stape

What it takes to run server side tracking each way. Checked September 2026 against Google's and Stape's own pages.

DataCops
Server-side GTM on Cloud Run
Stape hosting
Sends server-side events to Meta and Google Ads
Once you build the tags
Once you build the tags
Runs on your own subdomain
One DNS record
You map the domain
Custom domain
No containers to build
Web and server containers
Hosts your GTM containers
Hosting
Included
About $45 a month per server, 2 or more
Free to 10K requests, paid from $17
Keeps bot conversions out
Real people only, per platform
Consent banner and server consent check
Built in
You wire it
You wire it
CRM sales as offline conversions
HighLevel, webhook, CSV
Custom build
Custom build
Per-event delivery log with reasons
Preview mode and logs
Hosting logs
Good to know

What to know before you start

Three settings worth knowing on day one.

The long cookie needs your subdomain

The 400-day cookie is set only when the script loads from datacops.yourdomain.com, and only once you switch it on. On our shared CDN it is not set.

Bot filtering is a switch

Real people only is off by default. Turn it on per platform to keep flagged bots and datacenter traffic away from your ads.

Google Ads actions start as secondary

DataCops adds its conversion actions as secondary, so nothing changes your bidding until you make one primary.

Set up server side tracking

About 5 minutes. No container, no server, no developer.

  1. Step 1
    code

    Add the DataCops script
    Paste one script tag on your site.

  2. Step 2
    dns

    Add one DNS record
    Point datacops.yourdomain.com at DataCops. The dashboard shows the exact record.

  3. Step 3
    ads_click

    Connect your ad accounts
    One-click sign-in for Meta, Google Ads, TikTok, LinkedIn and X, an API key for Microsoft Ads, Reddit and Pinterest.

The offline gap

What server side tracking still misses: the sale after the form

Server side tracking only sees your site. When the lead becomes a sale in your CRM, send that stage too, matched to the original ad click.

HighLevel

Install once for your agency and pick the sub-accounts to connect. Each stage is sent as HighLevel reports it. Cancellations, no-shows and lost deals are never sent, and you can switch any stage off.

Sends Form leadBookedShowedWon, with valuePaid invoice
Offline conversions for agencies

Salesforce, Pipedrive and any other CRM

Post the sale to your private DataCops webhook with the customer's email or phone, the value and the order ID. Your CRM can send it directly, or through Zapier, Make or n8n.

Sends Any stage you postValue and currencyOrder ID

Google Sheets and CSV

On a paid plan, upload up to 20,000 past customers or sales from a CSV and pick the platforms to send them to. Rows go out with the date you send them, so use it to warm up an ad account. For sales you add to a sheet every day, send each row through Zapier or Make to your webhook.

Sends LeadPurchaseSchedule
See Ads Warmup
In short

Server-side tracking with DataCops, in short

DataCops is a no-code server-side tag manager: one script and one DNS record send your conversions server-side to Meta, Google Ads, TikTok and LinkedIn, with every send logged.

How DataCops does it

1

One script, one DNS record

The script runs on datacops.your-domain through one CNAME record, so ad blockers and Safari treat it as your site. With your DNS on Cloudflare, the free Worker reads click IDs and UTMs at the edge before the page loads. Click IDs are kept on the server for up to 90 days.

2

A visitor memory that survives Safari

A signed identity cookie set by the server lasts up to 400 days. It is off by default and is set only when the request arrives on your own datacops subdomain, never on the shared host. Safari caps cookies written by browser scripts at 7 days.

3

Server-side to the platforms, counted once

Meta, Google Ads, TikTok and LinkedIn receive the events, matched by click ID or hashed email and phone. Pixel and server events share an event ID. Google Ads conversion actions are created as secondary, so your bidding does not change by surprise.

4

Keep bots out

Every visit gets a bot verdict against 360+ billion IPs and 350+ monitoring points, with a Real people only switch per platform, off by default. Every form email is checked for disposable providers, domains with no mail server and an email risk score.

5

The sale after the form, and warm campaigns

HighLevel, HubSpot, any CRM by webhook and the DataCops Shopify app send the sale back. Ads Warmup sends up to 20,000 existing customers to Meta, Google Ads and TikTok, dated when you send.

6

Consent, analytics and a log

A first-party consent manager built on IAB TCF v2.2 and first-party analytics, a GA4 alternative, come from the same script, and a delivery log row shows each send as sent, held, skipped or failed with the reason.

Best for: teams who want server-side tracking without building and running a Google Tag Manager server container: lead gen, ecommerce, clinics, home services and agencies.

Free to start. See pricing.

When not to use DataCops

You need custom tags or GA4 feeds

DataCops does not send to GA4 and is not a container. If you feed GA4 or BigQuery from a server container, keep it for those. See Stape alternatives.

You want full control of the infrastructure

A server-side container on Google Cloud costs about $45 a month per server, with at least 2 instances recommended for production, and your team runs it. That control is the point for some teams.

You only need cheaper hosting

Stape lists a free plan up to 10,000 requests and Pro at $17 a month for 500,000. If your container works and only the bill bothers you, a cheaper host is the simple swap.

Google Ads is your only channel and traffic is clean

Google Tag Gateway plus Consent Mode may be enough. See Google Tag Gateway alternatives.

Sources

Platform rules checked October 2026. Rules change; check the platform's own page before you build.

FAQ

Server-side tracking sends your conversion events from a server to the ad platforms, instead of relying only on pixels running in the visitor's browser. Ad blockers, browser privacy limits and closed tabs cannot stop a server-to-server send, so your ad platforms see more of the conversions that really happened.

Server side tracking in 5 minutes

One script, one DNS record, every conversion sent server-side and logged.

Setup in 5 minutes. No credit card.

Live traffic quality

Updated just now

Visits · last 24h

487
Real users
35873.5%
Bots · auto-filtered
12926.5%

Without filtering, 26.5% of your reported traffic is bot noise inflating dashboards and draining ad spend.

Don't trust your analytics!

Make confident, data-driven decisions withactionable ad spend insights.

Setup in 2 minutes
No credit card