Google Ads server-side tracking means routing your conversion events through a server you control before they reach Google, instead of sending them straight from the visitor’s browser. In practice that server is a Google Tag Manager server container running on your own subdomain.
Unlike Meta, Google has no single endpoint called a Conversions API. The job is spread across a few mechanisms, which is why this reads differently from the Meta side even though the destination is the same.
How Google Ads server-side tracking actually runs
Your site keeps its browser tag. What changes is where it sends to: instead of
Google directly, it sends to your measurement address — something like
t.yoursite.com.
The server container receives that event and forwards it to Google Ads. Because the request now originates from a server, a content blocker in the browser has nothing to block, and a visitor who leaves the page does not take the request with them.
The same container can forward the same event to GA4, Meta and TikTok. That is usually the reason people set it up: one measurement, several destinations, one place to maintain.
Enhanced conversions
Enhanced conversions attach hashed first-party data — typically an email address your customer already gave you at checkout — so Google can match a conversion to a signed-in user more reliably.
They can be sent from the server container, which is generally the cleaner place for it. Hashing in the page means the value passes through the browser, where you have the least control over what else can read it.
What it will not repair
Consent. A conversion from a visitor who refused analytics storage is not recovered by sending it from a server. Server-side makes it easier to pass a consent signal through correctly, which is a different thing.
A wrong measurement plan. If the conversion fires on the wrong page or with the wrong value, it now does so from a server, more reliably.
Getting there
You need a Google Tag Manager server container, somewhere to run it on your own subdomain, and your existing web container pointed at it. Getting started walks through the setup, and GA4 server-side tracking covers the analytics half of the same container.
If you are earlier than that, what is the Conversions API puts the platforms side by side and client-side vs server-side tracking explains the mechanism.