Server-Side Tagging vs Server-Side Tracking

The recommended setup

If you want the most complete and accurate measurement stack, combine all three of these. Each layer solves a different problem:

Layer	What it adds
Server-side GTM	Faster page loads and full control over what data leaves your store
Google Tag Gateway	Serves Google's tag library and measurement requests through your own domain — longer cookie lifetimes and fewer browser blocks
ProfitMetrics	Captures every order from your platform and sends profit data (not just revenue) to ad platforms — enabling profit-based bidding

This combination gives ad platforms the strongest possible signal: client-side session data for AI bidding models, server-side conversions that ad blockers and consent declines can't break, and profit values that let you optimise for what actually matters to your business.

TIP: If you're not ready to invest in a full sGTM build, start with ProfitMetrics on its own. It's the biggest single improvement to your conversion data, it takes about an hour to set up, and you can add sGTM and Google Tag Gateway on top later when you're ready.

What is server-side tagging?

Server-side tagging moves your marketing tags out of the browser and onto a server you control — usually a server-side Google Tag Manager (sGTM) container running on your own subdomain.

It works like this:

The browser sends a request to your sGTM container.
The container processes that request and forwards it on to Google Ads, Meta, GA4, and any other destinations you've set up.
Each ad platform sees the request coming from your own domain rather than from a browser tag.

The two biggest benefits are site speed and data control. With less tracking JavaScript running in the browser, pages load faster, which helps both user experience and conversion rates. And because every request passes through a server you own, you decide exactly what data leaves your site and where it goes — you can filter, enrich, or strip fields before forwarding.

There are smaller benefits too — longer first-party cookie lifetimes under Safari's ITP, and a modest reduction in tags blocked by browsers — but speed and control are the main reasons to invest in sGTM.

What server-side tagging doesn't change is where the data comes from in the first place. The browser still has to fire the initial request. If the browser tag never runs — because of an ad blocker, a network issue, or the customer closing the tab — your sGTM container has nothing to forward.

What is server-side tracking?

Server-side tracking captures order data from the system that actually records the sale — your e-commerce platform, ERP, or payment processor — instead of from the customer's browser.

ProfitMetrics works this way. We connect directly to platforms like Shopify, BigCommerce, WooCommerce, Magento, Centra, and others using their official APIs and webhooks. Every completed order reaches ProfitMetrics, regardless of:

Whether the customer has an ad blocker
Whether the tag on the thank-you page actually fired
Whether the customer closed their tab before the page finished loading
Whether a network glitch stopped the tag manager from being reached

Once an order is in ProfitMetrics, we can send it on to your ad platforms using their server-side conversion APIs — Google Ads (Enhanced Conversions for Leads or offline conversion uploads), Meta Conversions API, GA4 Measurement Protocol, and others.

How consent fits in

Orders themselves always reach ProfitMetrics — that's how profit and margin reporting works, and the order record is business data your platform sends to us through the integration. Anything beyond that respects customer consent:

Visitor tracking data (session, click attribution, identifiers) is only stored if the customer has consented to tracking
Forwarding to ad platforms like Google Ads, Meta, and GA4 only happens if the customer has consented to that

If a customer declines tracking, their order is still recorded for your own profit and margin reports, but nothing about that order leaves ProfitMetrics for ad platforms.

Why many stores choose ProfitMetrics for conversions

If your main goal is to get accurate purchase data into Google Ads, Meta, and GA4, server-side tracking is usually the simpler and more complete option. Two reasons stand out:

You receive almost every order

Because orders are captured from your platform rather than from a browser tag, you don't lose data to ad blockers, tag misfires, customers closing tabs early, or network issues.

Approach	Where the data comes from	Typical capture rate
Browser-side tagging	A tag that fires in the browser on the thank-you page	60–85%
Server-side tagging (sGTM)	A browser tag fires, then the request is forwarded server-to-server	80–95%
Server-side tracking (ProfitMetrics)	Your e-commerce platform records the order	~100%

Setup takes an hour, not a project

A full server-side GTM setup is a project. You need to spin up a tagging server (or pay for a managed one), point a subdomain at it, rebuild your tag configuration, map your existing events into the server container, and test every destination. It often involves a developer or a specialist agency.

ProfitMetrics is much faster. For most platforms, you can connect your store, configure your conversions to forward to Google Ads, Meta, and GA4, and have full server-side tracking running in around an hour. There's no server to manage and no GTM rebuild.

This is why many stores that mainly want reliable purchase tracking pick ProfitMetrics rather than building out a full sGTM stack. The complexity isn't justified if you're not also planning to use sGTM for non-conversion events.

What can go wrong with each approach

This is where the practical differences show up:

Issue	Browser / server-side tagging	ProfitMetrics
Ad blockers	Partially affected	Not affected
Customer closes the tab too quickly	Affected	Not affected
Safari ITP / cookie limits	Partially affected	Not affected
Network errors reaching the tag manager	Affected	Not affected
Browser tag misfires or duplicates	Affected	Not affected
E-commerce platform API outage	Not affected	Affected

ProfitMetrics has one dependency the others don't: your platform's API or webhooks. In practice, that's much more reliable than the browser, and short outages are retried automatically.

Where Google Tag Gateway fits

Google Tag Gateway (GTG), previously known as First-Party Mode, lets you load Google's tag library and send measurement requests through your own domain instead of googletagmanager.com or google-analytics.com. Requests are routed through a path on your domain — for example, yourdomain.com/metrics — using a CDN integration with Cloudflare, Akamai, or Fastly.

GTG helps with:

Browser restrictions on third-party requests
Cookie lifetimes under Safari's ITP (especially when paired with server-side GTM)
Some — but not all — ad blocker rules

What GTG doesn't change: the Google tag still runs in the browser. If the browser never executes the tag, GTG can't help. Independent testing has reported uplifts in the range of 7–15% in reported conversions. That's a worthwhile improvement, but it's not the same as capturing every order.

Think of GTG as a way to make your remaining browser tags more reliable — not as a replacement for getting order data directly from your platform.

Other first-party serving approaches

Google Tag Gateway is one of several techniques that try to serve tracking requests from your own domain rather than from a third-party one. You may come across these other options — each solves a piece of the same problem with different tradeoffs:

Approach	What it is	Main limitation
CNAME cloaking / A/AAAA records	DNS-level routing that makes third-party tracking requests appear to come from your domain	Modern browsers — especially Safari — detect and block these patterns
FPID + CNAME from TMS providers	First-party ID and CNAME routing offered by tools like Adobe Experience Platform or Tealium iQ	Usually only protects the tag manager container, not the Google tag underneath. Mainly designed for backend data stitching
Pure server-to-server only	Conversion data sent straight from your backend with no browser tracking at all	Loses client-side session signals. Ad platform AI bidding performs best with both client and server signals
Custom loaders / edge workers	Custom JavaScript or CDN workers (e.g. Cloudflare Workers) serving tag scripts from your domain	Static scripts need manual updates whenever vendors change their tag code. Ongoing maintenance burden
Stape Gateway, Cloudflare Zaraz, similar CDN tools	Managed CDN-based first-party tag serving — similar in concept to Google Tag Gateway	Same principle as GTG: helps with browser blocking but doesn't change where the data originates

A note on pure server-to-server

ProfitMetrics uses a combination of client-side tagging aand server-to-server forwarding for conversions, designed to complement your client-side setup rather than replace it. You keep your browser-side tags for session and behaviour signals, and ProfitMetrics handles the order data reliably in the background. That combination is exactly why pairing ProfitMetrics with sGTM and Google Tag Gateway gives ad platforms the strongest possible mix of client and server signals..

Which approach to pick

Both server-side tagging and server-side tracking are valid. Which one fits depends on what you're trying to achieve:

If you mainly want reliable purchase tracking in Google Ads, Meta, and GA4 — ProfitMetrics gets you there in about an hour, with close to 100% of orders captured and profit-based bidding signals included.
If you want faster page loads and tight control over what data leaves your site — server-side GTM is the right investment, especially if you're also tracking lots of non-purchase events.
If you want the complete stack — combine all three: ProfitMetrics for conversions and profit data, sGTM for everything else, and Google Tag Gateway on top for first-party serving of Google's tags.

For most e-commerce stores, purchases are by far the most important events to measure — and server-side tracking through ProfitMetrics is the quickest path to better data in your ad accounts, with or without the rest of the stack on top.