Skip to content

Data tracking · Server-side tagging

Tracking that ad blockers cannot quietly erase.

Server-side Tag Manager moves tracking off the browser and onto a server you control. Fewer lost conversions, faster pages and one place to decide what data leaves your site. We set it up when it earns its keep, and tell you plainly when it does not.

Own domain A first-party endpoint you control
Fewer lost Conversions surviving blockers and ITP
Lighter Fewer scripts running in the browser
Controlled You decide what each vendor receives
What we do

Four things, in this order.

01 Decide honestly whether you need it. Meaningful ad spend, a real share of blocked visitors, or strict data controls. For most small sites a clean client-side setup is enough, and we will say so.
02 Host it properly. A tagging server on Google Cloud Run or a managed host, on a subdomain of your site, with the running cost written down before anything is built.
03 Move the right tags. GA4, Google Ads and Meta Conversions API move server-side. Consent is enforced there too; server-side is not a way around the banner and we will not build it as one.
04 Verify the difference. Client and server counts compared, events deduplicated with shared IDs, match quality checked. If the gain is small, we tell you and switch it off.

The audit

What we usually find in the first hour.

Server-side setups are often sold, not needed. Here is how the bad ones look.

Wrong reason

  • —Built to avoid the consent banner
  • —A copy of every client tag, doubling everything
  • —No running cost ever mentioned

Half migrated

  • —Client and server both firing
  • —No event IDs, so nothing deduplicates
  • —Meta match quality worse than before

Unowned

  • —Runs on the agency’s cloud account
  • —No monitoring when it stops
  • —Bills that arrive as a surprise
How it works

Three weeks, then a routine.

Week one Measure what is being blocked today and what it costs you. Decide together whether to proceed.
Week two Tagging server provisioned on your account and subdomain, container built, consent enforced, all on staging.
Week three Parallel run against the client-side setup, counts compared, deduplication confirmed, cut over.
Every month Server health and cost checked; match quality reviewed in the note.

Part of data tracking, which is inside every maintenance retainer. As standalone work it is quoted after the audit.

Keep reading

Let’s look at your site together.

Thirty minutes with Ali. He will ask about the business first, then go through the site with you on the call.

Book a call with Ali
Ali Demirci
Ali Demirci
Founder
What we would fix first
The handful of things actually holding it back.
What we would leave alone
Usually more than you expect.
Whether we are a fit
And we will tell you if we are not.

Common questions

Do we need it?+

Probably not, if you are a small site with modest ad spend. It becomes worth it when blockers and Safari are hiding a real share of conversions or when spend is large enough that a few percent matters.

What does it cost to run?+

Hosting is usually tens of dollars a month, scaling with traffic. We write the estimate down before building and it runs on your account, so there are no surprises.

Does it get around consent?+

No, and we will not build it to. Consent applies server-side exactly as it does in the browser. Anyone offering otherwise is offering a liability.

Does it help Meta and other ad platforms?+

Yes. Meta’s Conversions API, and the equivalents from LinkedIn and TikTok, run from the same server with the same consent and deduplication.