Enhanced conversions and server-side tagging at a glance
Google documents enhanced conversions as a feature that supplements existing conversion tags with hashed first-party conversion data. The conversion action, its trigger and its counting rules stay as they were; what changes is the payload. The enhanced conversions guide explains the two variants: for web, where the tag sends the hashed data at the moment of conversion, and for leads, where hashed data captured at the form lets a later outcome from the CRM be matched to the click without storing the click identifier. The match depends on the person having been signed in to a Google account when they interacted with the ad, so where no match is possible the conversion falls back to what the click identifier could do.
Google's introduction to server-side tagging describes a second container type in Tag Manager that runs on infrastructure the business controls. The browser sends one stream of events to that server container, clients claim the requests, and server tags forward each event to the vendors. The server-side tagging guide tables what that improves (fewer vendor scripts on the page, one place to strip or withhold fields, cookies set by the site's own server, vendor credentials kept off the page) and what it cannot fix, such as events that are wrong at the source or visitors who declined consent. It also sets out the hosting and operations a server container needs.
So one is a feature of one platform's conversions and the other is a layer that sits under every vendor. The comparison of client-side and server-side tagging covers the general choice of where collection runs; this page is narrower. It asks which of the two fixes to reach for when conversion data is the problem, and it does not re-teach either setup.
Compare table
Enhanced conversions vs Server-side tagging
| Row label | Enhanced conversions | Server-side tagging |
|---|---|---|
| Problem it solves | Google Ads conversions lost because the click identifier was missing, blocked or expired | Too many vendor scripts, no single point of control over what vendors receive, short-lived script-set cookies |
| Platforms it serves | Google Ads only | Every vendor with a server tag: Google Analytics, Google Ads, Floodlight, Meta and others through templates |
| What data moves | Hashed email, phone, name or address with the conversion, or with a later upload for leads | The events the browser sends, reshaped on the server and forwarded to each vendor |
| Where it runs | In the existing conversion tag, in a web Tag Manager container, or through the Google Ads API | In a server container on the business's own subdomain, hosted on Google Cloud or chosen infrastructure |
| Setup effort | Accept customer data terms, enable the feature, supply the fields through the tag or data layer | Provision the server, map a custom domain, migrate tags, test, and remove the browser copies |
| Ongoing cost | Little beyond keeping the data capture working when forms change | Hosting that scales with traffic, image updates, monitoring and someone on call |
| Consent handling | The consent banner must gate the conversion tag so no hashed data is sent without consent | Respects the consent state the browser sends; the banner and consent mode stay client-side |
| What it cannot fix | A broken base tag, a wrong conversion definition, visitors not signed in to Google | Events wrong at the source, a weak data layer, visitors who declined consent |
| How to validate | Diagnostics tab on the conversion action, a tagged test conversion, a before-and-after count | Server preview from incoming request to vendor response, and a parallel run before cutover |
| Who owns it | The Google Ads or analytics specialist | Engineering for hosting and domain, analytics for the container's contents |
The rows on problem, platforms and ongoing cost carry the comparison. Enhanced conversions answer one question for one platform: can Google match more of the conversions that really happened? Server-side tagging answers a set of questions for every vendor at once: what leaves the browser, in what shape, from which domain and with which cookies. Its cost is ongoing, because a server container is software someone has to run. When the gap is narrow and specific to Google Ads, the narrower fix is usually the right first step.
When to choose enhanced conversions
Choose enhanced conversions when Google Ads records fewer conversions than the business can see happening, and the base tag is known to fire. The enhanced conversions guide lists where the gain tends to be large: long gaps between click and conversion, browsers that restrict storage, consent regimes where many visitors decline but later consent at the point of conversion, cross-device journeys, and lead-generation businesses adopting the leads variant. In each, the click identifier is the weak link and a hashed key offers a second route to the same ad interaction.
Choose it when the business already collects the first-party dataData a business collects directly from its own customers, visitors and users. at the conversion. A checkout knows the email address the customer just typed; a lead form knows the address it was given. Pushing those values into the data layer and letting the Google Ads tag hash them is the route the guide recommends for most sites, because the raw values stay in the browser and the implementation survives redesigns.
Choose the leads variant when the conversion that matters happens in the CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it.. The guide to connecting the CRM to ads and analytics covers the CRM's part: hold the same email or phone the tag captured, unchanged, and upload the outcome with it.
Do not expect it to fix the base setup. A trigger on the wrong event, a primary action measuring the wrong thing or a tag that does not fire leaves nothing to enhance, and the enhanced conversions troubleshooting page separates a broken implementation from one that is recording correctly but recovering little.
When to choose server-side tagging
Choose server-side tagging when the problem is control. If the business needs to decide exactly which fields reach each vendor, strip identifiers before they leave, or keep vendor credentials off the page, the server container is the only place that control exists. The server-side guide's decision table gives this the strongest case, alongside reliance on several vendors' server integrations and an audience that skews towards browsers restricting script-set cookies.
Choose it when the page carries many vendor scripts and speed is a problem. Moving vendors to server tags removes their scripts from the browser, provided the browser tags are removed once each vendor is migrated; keeping both double counts unless deduplicated.
Choose it when the gap spans platforms rather than Google Ads alone. A server container feeds Google Ads, analytics and Meta's Conversions APIServer-side event sharing with Meta. from one event stream, which is how the comparison of the Meta Pixel and Conversions API describes server events completing the browser's view on one platform.
Do not choose it as a first step when the data layer is immature, consent is broken or nobody owns the hosting. The server receives only what the browser sends, and the guide's test is blunt: name the requests that will leave the page, the vendors the server will call and the person who will answer when the endpoint fails. If any is blank, the case is not ready. The academy exercise on planning a riding equipment retailer's move to server-side tagging practises giving each of its measurement gaps the fix this page points to, putting an agency's all-at-once server proposal through that test and ordering the cutover vendor by vendor with a way back.
Decision table
| Situation | Choose | Why |
|---|---|---|
| Google Ads records fewer conversions than orders, base tag firing | Enhanced conversions | The gap is matching, and a hashed key closes some of it |
| Lead outcomes live in the CRM and the click identifier is hard to keep | Enhanced conversions for leads | The upload is matched on hashed lead data |
| Many vendor scripts and a page-speed problem | Server-side tagging | Vendor scripts move off the page |
| A policy requires control over exactly what each vendor receives | Server-side tagging | The server container is the only place that control exists |
| Several platforms' server integrations are needed at once | Server-side tagging, carrying enhanced conversions | One event stream feeds every vendor |
| Consent wiring is broken or missing | Neither, until consent mode is fixed | Both inherit whatever consent state the browser sets |
| The base conversion tag does not fire | Neither | There is nothing to enhance or forward |
| No owner for hosting and on-call | Enhanced conversions only | An unmaintained endpoint is worse than none |
Using both: enhanced conversions sent through a server container
Once a server container exists, enhanced conversions can travel through it. The server-side guide lists server tags for Google Ads conversions and describes server tags carrying enhanced conversions and offline matching from one event stream. The browser still supplies the user-provided data, through the data layer and the outbound tag, and the server's Google Ads conversion tag forwards it. Nothing about the feature changes: the same customer data terms, the same normalisation before hashing, the same diagnostics tab.
Two cautions apply at the cutover. Check that the hashed data still arrives in Google Ads after the conversion tag moves to the server; the server-side go-live work includes that check, and the diagnostics tab on each conversion action is where it shows. And move each vendor once: a conversion tag left in the web container beside its server copy counts twice. When the server receives nothing at all, the server-side troubleshooting page follows one request from the browser to the vendor to find the hop that breaks. The academy checkpoint on cutting measurement over to a server container tests both cautions beside the choice of fix for a matching gap, the endpoint's domain, which client claims each request, the side-by-side run and rolling back a cutover that fails.
Consent sits under both. Google's Consent ModeA Google tag feature that adjusts what tags collect according to the visitor's consent choices. documentation describes a consent state set in the browser that tags adjust to, and the guides on this site are consistent that neither enhanced conversions nor a server container is a way to measure people who declined. Consent mode models that remainder. A measurement plan is the place to write down which conversions each layer is meant to improve and how the improvement will be checked, before either is switched on. What counts as adequate consent is a legal question, not a tagging one.
A furniture retailer chooses where to start
Lumvoretti Furniture, an invented online furniture retailer, moves payment to an external provider's hosted page in March. Orders in its shop system hold at about 820 a month, but Google Ads conversions fall from 640 to 505. Tag preview on test orders shows the conversion tag firing on every confirmation page, so the base tag is sound and the loss is in matching after the redirect. An agency proposes a server-side container: an estimated 12 days of engineering for provisioning, domain mapping and migrating 7 vendor tags, plus hosting and on-call. The team checks the gap first. Meta, its only other paid platform, shows no comparable drop, and page speed is within its target. It turns on enhanced conversions for web through Tag Manager instead, pushing the checkout email into the data layer before the tag fires, consent-gated as before, in 2 days of work. After a six-week settling period, Google Ads records 590 conversions a month against 815 orders, and the diagnostics tab reads recording. The server-side project moves to next year's plan, when the retailer expects to add two more ad platforms.
The comparison library lists the other measurement pairs that are easy to confuse.
Common mistakes
- Building a server container to switch on enhanced conversions. The web container or the Google tag already supports the feature.
- Expecting either to fix a broken base tag. Fix the trigger and the conversion definition first.
- Treating either as a way round declined consent. Both inherit the browser's consent state; modelling handles the remainder.
- Hashing without normalising. Email and phone values must follow Google's format rules or nothing matches.
- Leaving browser tags beside their server copies. Migrate each vendor once, or conversions count twice.
- Skipping the check after cutover. Confirm enhanced conversions data still arrives once the conversion tag moves to the server.
- No owner for the endpoint. When a server container stops answering, every vendor behind it goes silent at once.
