Keep the container in your account
Google Cloud Run, or your existing infrastructure. Your project, your billing, your access - the container does not live in my account.
Server-side GTM on infrastructure you control
A server container in your own cloud, with GA4, Meta CAPI and the ad platforms routed through it. Deployed, documented and handed over - not rented from an agency dashboard.
Incoming event
purchaseServer containerCloud Run
GA4
Google Ads
Meta CAPI
Your cloud project, your access
Proposed architecture. This is an illustration of the service, not a live client deployment.
Own the path from an event to the platform
Collect through your own domain
Properly delegated, with the certificate and the DNS documented, so cookies are set first-party and survive.
Reconcile browser and server events
With deduplication against the existing browser tags, so you can run both while you verify rather than cutting over blind.
Illustrative interface with sample data. No live account is connected.
How it runs
- 1Measurement audit
- 2Container and domain
- 3Route and deduplicate
- 4Verify and hand over
What gets delivered
- A server container in your cloud
- A first-party collection subdomain
- GA4 and Meta CAPI routed server-side
- Consent Mode v2 wired correctly
- A spec your team can maintain
Scoped4-8 weeks, fixed scope agreed before it startsBook the audit call
Most engagements begin with the $3,000 attribution audit and move up only if it finds something worth building.
You probably need this if
- Meta reports materially fewer conversions than your CRM settles
- GA4 and your ad platforms disagree on the same week by more than rounding
- Event Match Quality is low and nobody is sure why
- Safari and iOS traffic converts "worse" than Android in a way the product does not explain
- Your tags are heavy enough to show up in Core Web Vitals
Written up in detail
Questions I get asked
What does it cost to run each month?
Hosting is usually the smaller number - a low-traffic container runs from tens of dollars a month, and scales with request volume rather than seats. The cost that matters is engineering time, which is why the spec and handover are part of the delivery.
Do we have to turn off the browser tags?
No, and you should not do it on day one. Both run in parallel with deduplication until the server-side numbers reconcile with what you already trust.
Will this get us around consent requirements?
No. Server-side tagging changes where events are collected, not whether you are allowed to collect them. Consent Mode v2 is part of the build for exactly that reason.
Can our team maintain it afterwards?
That is the point of the spec and the walkthrough. If you would rather not, the fractional retainer covers ongoing ownership at $2,500 a month.
Start with the audit
A read-only review of how your funnel is measured, and whether server-side is actually your constraint.