Deduplicating three platforms from one server-side GTM container

The situation

An APAC enterprise SaaS company had invested heavily in a GTM Server-Side container setup. They were sending events to Meta, Google Analytics 4, and LinkedIn simultaneously from the server container. A technical audit before their Series B requested by their lead investor revealed significant overcounting across all three platforms.

The problem

The server-side GTM container was correctly receiving events — but each client tag (Meta, Google, LinkedIn) was firing independently on every event without platform-specific deduplication logic. Meta received events without event_id. LinkedIn received page views that were also being sent by the client-side Insight Tag. Google received events that were also firing from the client-side GA4 tag. Triple-layered deduplication failure.

What we did

1. Audited all three platform tags in the server container — none had deduplication fields configured
2. Added event_id to the Meta CAPI server tag using request header + timestamp hash as unique identifier
3. Disabled client-side LinkedIn Insight Tag — server container now sole source for LinkedIn events
4. Configured GA4 Measurement Protocol tag with client_id passthrough and session deduplication against client-side GA4
5. Built monitoring dashboard in Looker Studio to track event parity across all three platforms vs server event log

Why it worked

Server-side GTM is often set up as an additional data pipe rather than a replacement — resulting in client-side and server-side events both reaching platforms simultaneously. Each platform handles this differently: Meta requires event_id, GA4 requires matching client_id, LinkedIn has no native dedup and requires removing the client-side tag entirely. Getting all three right requires platform-specific configuration, not a generic server container.