Server-side tracking, built as infrastructure rather than as tags.
Moving collection off the browser is the only structural fix for ad blockers, ITP and consent gating. But a container that forwards GA4 and nothing else recovers almost nothing — the gains come from the Conversions API layer, first-party identity and deduplication built around it. This is that whole build, not the container on its own.
The container is the easy part
Provisioning a server container takes an afternoon. What decides whether it recovers anything is the architecture around it: whether identifiers survive ITP, whether browser and server events deduplicate, whether consent is enforced or merely trusted, and whether the payload carries enough for a platform to match it to a person. Those are the things we design first and the container second.
You own the result
The GTM account stays yours, the infrastructure code is handed over as Terraform or Helm, and the raw events stream to your own warehouse in parallel. Whether we run it or you do is a procurement decision, and we price it the same either way.
- Server container with a custom tagging domain, DNS and TLS
- Conversions API layer across Meta, Google Ads, TikTok, LinkedIn, Pinterest, Snapchat and Reddit
- event_id deduplication between the browser pixel and the server
- Server-set first-party identifiers that survive ITP
- Consent Mode v2 evaluated in the container, per destination
- Bot, datacenter and AI-crawler filtering before anything is billed for
- Sites under roughly 10,000 sessions a month — the recovery will not pay for the running cost, and we will say so
- Anyone who wants the container without the CAPI and consent work. That combination is what does not work today
Tell us what your stack looks like.
You will get a reply from the engineer who would do the work, usually within one business day, and it will contain an actual opinion rather than a calendar link.