One server.
Many destinations. Deduplicated.
GTM Server containers on Stape or your infra. GA4 reinforcement, Meta CAPI dedup, Google Ads conversions via server, Measurement Protocol from your backend, Consent Mode v2 for EU. Documented, monitored, transferable.
Four signal-degradation failure modes.
- 01
Client-side pixels losing 30–60% of events
Safari ITP, iOS in-app browsers, ad blockers, third-party cookie removal. Pure browser-side tags degrade silently. Bidding algorithms starve. Reported CAC drifts away from reality.
- 02
Server-side container set up — and then forgotten
Stape installed two years ago, GA4 server tag added, then nobody touched it. Meta CAPI absent. Consent Mode never wired. Measurement Protocol from CRM disabled. You have the cost without the benefit.
- 03
Consent Mode v2 missing for EU traffic
Required for EEA delivery in Google Ads, and required for modelled conversions in GA4. Without CMv2, opt-outs accumulate as quiet revenue loss in reports.
- 04
Backend orders never reach the ad platforms
PayPal, manual orders, B2B contracts closed outside the web flow. The pixel never fires. Measurement Protocol from the backend is the only path — and it's not running.
A server-side stack you can actually operate.
- 01Engineered
GTM Server container (Stape or self-hosted)
Provisioning, first-party domain mapping, custom transport URL. SSL, monitoring, log retention configured.
- 02
GA4 server-side reinforcement
Client-side gtag reinforced via server. Events de-duplicated against transaction_id. session_id preserved.
- 03
Meta CAPI with event_id dedup
Server-side CAPI matched to client Pixel via event_id, em, ph, fbp/fbc. Monitored match rate. Recovers 30–60% of lost iOS / EU signal.
- 04
Google Ads conversion via server
Server-side Google Ads conversion tag with Enhanced Conversions. Cookieless-resilient. Click ID preserved.
- 05Backend
Measurement Protocol from backend
Webhook from CRM / ERP / order system → server container → GA4 + Ads + Meta. Picks up PayPal, manual, and B2B orders the pixel can't see.
- 06
Consent Mode v2 wired through CMP
google_consent_default and google_consent_update from your Cookiebot / Complianz / Iubenda. Modelled conversions enabled. EU compliant and analytics doesn't die.
- 07
Match rate monitoring
Alerts on Enhanced Conversions match rate drops, CAPI match degradation, Unassigned channel spikes. Slack or email.
- 08
Documented runbook
Architecture diagram, secret management, on-call response, change procedure. Transferable to your team or to another vendor.
Audit, provision, verify, operate.
- 01
Free server-side audit
Phase 01 · 5 working daysInventory of what's currently firing client-side, what's missing, what would benefit from server-side, and what's already broken in your existing SS setup if you have one.
- →Tag inventory: client vs server
- →Match rate baseline (EC, CAPI)
- →Missing-event list: backend-only purchases
- →Architecture recommendation with cost estimate
- 02
Provision & wire
Phase 02 · Weeks 1–2Stape or self-hosted container. First-party domain. GA4, Ads, Meta tags. Consent Mode v2. Measurement Protocol from backend.
- →GTM Server container live on first-party domain
- →GA4, Ads, Meta CAPI tags configured
- →Consent Mode v2 verified against CMP
- →Backend webhook → MP wired end-to-end
- 03
Verification
Phase 03 · Weeks 2–3End-to-end testing. Dedup verified. Match rates measured against baseline. Backend reconciliation. Alerting deployed.
- →Dedup verified at scale (Pixel ↔ CAPI, gtag ↔ MP)
- →Match rate uplift quantified
- →Backend revenue reconciliation closed
- →Monitoring + alert channels live
- 04
Operate
Phase 04 · OngoingQuarterly schema review, secret rotation, version bumps, response to platform changes (e.g. new consent requirements, new attribution models).
- →Quarterly schema review
- →Platform change response (new requirements absorbed)
- →Documented runbook kept current
- →Optional: on-call retainer for incidents
Selected server-side work.
BuduProfi
MP + client_id setup; Unassigned channel reduced 80% → <10%.
Signal recovery +38%
Mill
Backend lead webhooks → GA4 MP; ads-grade attribution against the CRM.
Ember
Meta CAPI dedup; match rate stabilised; tracking decoupled from third-party cookies.
Ararat
Server-side CAPI rebuild; reported CAC reconciled against orders.
Common questions.
Stape is the default for most clients — managed infra, predictable cost, fast to provision. We move to self-hosted GCP/AWS when there's a specific reason: extreme volume, strict data residency, or an existing SRE team that wants ownership.
Match rate improvement is usually visible within 2–4 weeks once smart bidding has enough signal to recalibrate. Revenue reconciliation against the backend is immediate — you'll see the gap close as soon as MP starts firing.
No. Server-side reinforces client-side, it doesn't replace it. We maintain dual-tagging during transition and gradually retire client tags only where the server-side path is verified equivalent.
For EU/EEA traffic in Google Ads, yes — without CMv2 you lose access to remarketing and modelled conversions on consent-denied users. Outside the EU it's not legally required, but it's still good practice for global compliance.
Yes, as a retainer add-on. Most clients don't need it, but for accounts where tracking outage = real revenue loss in hours, we offer on-call coverage with documented response SLAs.
Pixel-only setup leaving money on the table?
Send the GTM container access. Five working days, written diagnostic, and a clear scope for what server-side would actually recover.
No long contracts · Free audit before any work