Which platforms support server-side Google Tag Manager?

Server-side Google Tag Manager (sGTM) supports many advertising and analytics platforms, like GA4, Google Ads, Meta, TikTok, Pinterest, LinkedIn, Snapchat, Klaviyo, and ActiveCampaign. E-commerce data layers are available for CMSs including WordPress, Shopify, Lightspeed, Magento, WooCommerce, and PrestaShop. Mobile apps on iOS and Android are also supported.

Where each platform goes (web container, server container, or both) determines whether your conversion data is accurate.

This article explains the why behind each placement decision, what breaks when you get it wrong, and what sGTM hosting providers like TAGGRS handle at the infrastructure level that the container setup alone can't fix. And if you already know your platform(s), use the interactive checker below to jump straight to the configuration steps.

What is a GTM server container, and what does it host?

A GTM server container runs on a hosted server and executes tags server-to-server, separate from the visitor's browser. It works alongside the standard GTM web container using a two-container architecture:

1. web container, which runs in the visitor's browser and executes client-side tags
2. server container, which runs on a hosted server (such as TAGGRS) and executes tags server-to-server.

The server container is where the real work happens. When it's configured correctly, it sets first-party cookies that last up to over 365 days. And this matters now more than ever because Safari's ITP caps browser-set cookies at 7 days, and Safari represents approximately 17% of global browser market share as of early 2026. (source: StatCounter, Browser Market Share Worldwide)

Simply put, almost 1 in 5 of your sessions is losing tracking data by default if you're only running client-side.

TAGGRS sGTM hosting is a managed Server-side Tracking provider that hosts your GTM server container on an independent European infrastructure. It works alongside Google Tag Manager using two containers:

TAGGRS sGTM hosting works across any website stack. The rule is: if it works with Google Tag Manager, it works with TAGGRS too. So, CMSs with dedicated data layer support include WordPress, Shopify, Lightspeed, Magento, WooCommerce, and PrestaShop. Mobile apps on iOS and Android are also supported.

Where to place the container?

Every platform gets placed in 1 of 3 configurations. This is an architectural decision that affects whether conversions are counted correctly, whether cookies survive ITP, and whether data leaves your infrastructure before or after consent is applied. Here is the breakdown:

Configuration	What it means	When to use it
Web container only	Tag runs in the browser. No server component.	Not relevant for sGTM setups.
Server container only	All data flows from the server. No browser tag.	When the platform does not support deduplication, or when the browser tag is unnecessary.  Note: without an existing client-side GTM setup, a server-only configuration requires a custom tracking implementation, both frontend event collection and backend event forwarding need to be built and maintained from scratch.
Both containers	Browser tag sends data to the server container, which forwards it to the platform. The web container can also send data to the server side without sending anything directly to a platform. Deduplication is only required when both the browser and the server send to the same platform simultaneously.	When the platform benefits from both browser signals and server reliability.

Which container does your platform belong in?

Not sure where to place a specific platform? Use the checker below. Select a platform and get the container placement, the deduplication requirements, and the exact configuration steps.

Platforms that go in the server container only

Advertising platforms

Google Ads Server-side Tracking requires 4 components in sequence:

1. GA4 Config tag (web container)
2. GA4 server tag (server container)
3. Conversion Linker tag (server container)
4. Google Ads Conversion Tracking tag (server container)

According to the FAQs our Support gets, the Conversion Linker is the step most often missed. Without it, click data doesn't attach to conversions correctly and attribution breaks. Google Ads Remarketing runs through the same chain.

Google Ads Remarketing also runs server-side only, using the same GA4 dependency.

TikTok is server container only, too. TikTok's pixel does not support event deduplication at the level required to run browser and server tracking simultaneously. Running both without guaranteed deduplication inflates conversion counts.The server tag sends events to TikTok's Events API and automatically transforms required user data (email, phone) to lowercase and hashes it using SHA256 before transmission.

Verify your setup in TikTok's Events Manager before enabling any parallel tracking.

CRM and marketing automation

Klaviyo does not support event deduplication. Running both browser and server sends duplicate events to Klaviyo. Configure server-side only. The tag communicates directly with Klaviyo's API and supports adding contacts, tracking on-site activity, and sending event parameters.

ActiveCampaign connects with the ActiveCampaign API server-side. The tag supports 3 action types: track events, create or update a contact, and create or update a contact while tracking an event simultaneously.

Platforms that require both the web container and the server container

Analytics

Google Analytics 4 isn't optional in a server-side setup. The GA4 Config tag in the web container sends data to the server container, which feeds every downstream tag, including Google Ads. There is no server-side Google Ads setup without server-side GA4 in place first.

Deduplication for GA4? It’s not required. Session continuity is handled automatically across both containers.

Advertising platforms

Platform	Why both containers?	Deduplication required?	Matching parameter
Meta	Meta recommends running browser pixel and server CAPI simultaneously to maximize match rates and event coverage.	Yes	event_id must match between web and server events
Pinterest	Browser tag + Conversions API run in parallel, same dual-signal logic as Meta.	Yes	Advertiser ID + event deduplication key
LinkedIn	Insight Tag runs client-side; server tag sends conversion events via LinkedIn CAPI.	Yes	conversionId
Snapchat	Snap Pixel (web) + Snap Conversions API (server) run in parallel. Tag automatically normalizes and hashes user parameters.	Yes	event_id

But, what deduplication means in practice? Deduplication happens when the same conversion event fires in both the browser and the server, so the platform receives it twice. Without deduplication logic (a shared event ID that tells the platform "these two events are the same") your conversion counts inflate. For Meta specifically, this means ROAS reporting becomes unreliable.

E-commerce: CMS-specific data layers

Server-side Tracking is only as good as the event data reaching the server container. For e-commerce, that means a correctly structured data layer: one that passes purchase, add-to-cart, and product view events with the right parameters.

TAGGRS has dedicated data layer configurations for CMSs including WordPress (with WooCommerce), Shopify, Lightspeed, Magento, and PrestaShop.

Each CMS has a different data layer structure. Using the wrong event format causes conversion events to arrive at the server container with missing or malformed parameters: the most common reason server-side Google Ads tracking appears to work but underreports conversions.

Mobile apps: iOS and Android

TAGGRS supports server-side tracking for mobile apps on iOS and Android. App events route through the server container using the same infrastructure as web tracking. This is relevant for teams running Google Ads App campaigns or Meta app install campaigns where browser-side tracking is not available and SDK-level event data needs a server relay before reaching ad platforms.

Which setup matches your tracking stack?

Google Ads + GA4 only 

Configure GA4 in both containers. Google Ads runs server-side only. This is the minimum viable sGTM setup for teams starting out.

Google Ads + Meta + GA4 

Add Meta CAPI with event_id deduplication. This is the most common agency configuration. It covers the two highest-spend platforms and delivers the largest signal recovery gain for most clients.

Google Ads + Meta + TikTok + LinkedIn + Klaviyo 

Every platform above applies. At this scale, infrastructure management — container uptime, multi-client access, credential rotation — becomes the operational constraint, not tag configuration. TAGGRS's managed hosting and role-based access controls are built for this environment.

E-commerce stack (Shopify / WooCommerce / Lightspeed) 

Start with CMS-specific data layer configuration before setting up any platform tags. An incomplete data layer produces missing parameters at the server level, and no tag configuration can compensate for events that never formed correctly upstream.

FAQs

Which platforms require event deduplication in server-side GTM? 

Meta (Facebook CAPI), Pinterest, LinkedIn CAPI, and Snapchat CAPI require event deduplication when running both browser and server tracking simultaneously. TikTok does not support deduplication and must be configured server-only to avoid inflated conversion counts.