Which conversion tracking setup does Google need now: enhanced conversions, consent mode or server-side tagging?
Our answer
Turn on enhanced conversions with the Google tag on every page, serve tags through Google tag gateway and pass at least 3 identifier signals per conversion. Add a server-side container only when your spend justifies it.
- Confidence
- Medium
- Strongest proof
- 10 Google rules
- 1 practitioner, 5 opinions or claims
- Sources
- 6 sources
- 16 statements
- G
SP
New here? Take the 1-minute tour
Why this is the answer
3 reasons and our judgmentGoogle runs enhanced conversions as one on/off setting that takes hashed customer data from tags, Data Manager and API connections at once. From November 16, 2026, Data Manager also accepts encrypted data without hashing (PPC Land).
Google advises tag gateway, which serves tags from your own domain, and at least 3 identifier signals per event. By its own figures the gateway lifts observed conversions 14%, and enhanced conversions add 8% incremental ROAS on Search for value bidders.
A server container pays only past a spend point. PPC Rebels, an ad account rental agency, argues it starts at about $3,000 to $5,000 a month with 100 or more conversions, weighing spend times the 10 to 20% of signal recovered against build and upkeep.
Our judgment
Build in the order base tag, enhanced conversions, tag gateway, then a server container. Google's own pages treat the first three as standard setup, while the one source that puts a number on server-side payback shows no account data behind it. Before paying for a server container, run PPC Rebels' arithmetic on your own Google spend rather than taking its spend point as given.
Our judgment, built from Google and PPC Rebels: our reading of these sources, not a finding from any one of them.
What the sources say
16 statements from 6 sourcesGoogle says user-based Conversion Lift does not support web conversions imported from Google Analytics or GCLID imports without hashed PII, and asks for 7 to 14 days of conversion data first.
“GCLID imports without hashed PII can't be used in Conversion Lift, because the control group is not served an ad to click on.”
Google Analytics launched Data Manager, one admin hub for links, data streams and imports, and warns that activating the same data pipeline in both places can log conversions twice.
“this can log conversions twice.”
Google launched Data Manager in Google Analytics in beta on November 6, 2026, and warns that running the same data pipeline in both Analytics and Google Ads can log conversions twice.
“Don't activate an identical data pipeline in both interfaces together, as this can log conversions twice”
Google emailed server-side Tag Manager users that from January 11, 2027, Google Ads and its other ad tags will accept the full visitor IP address by default, with an opt-out. Google Analytics tags keep redacting it.
“Google Analytics tags will continue to apply IP redaction”
Google says that from June 15, 2026 offline conversion uploads move to the Data Manager API, and from June 2026 enhanced conversions for web and leads become one on/off setting.
“Starting June 15, 2026, offline conversions import and enhanced conversions for leads uploads will be migrated to the Data Manager API and blocked in the Google Ads API.”
Google says enhanced conversions add hashed first-party data such as email addresses to your existing conversions, matched to signed-in Google accounts that engaged with your ads.
“supplements your existing conversion by sending hashed first party conversion data (from your website tags or your imported offline events) to Google in a privacy safe way.”
Google recommends passing at least 3 identifiers per conversion event, all events and transaction IDs, and running tags through its tag gateway. Its claimed gains, such as 14% more conversions, give no method.
“We recommend passing at least 3 identifier signals per event.”
PPC Land reports that from November 16, 2026 Google's Data Manager will no longer require SHA-256 hashed customer data and will support encrypted data by default, touching Customer Match and enhanced conversions.
“Data Manager will no longer require customer data hashed with SHA-256”
Salvo Puglisi says direct-to-consumer brands should set up conversion tracking through GTM and server-side tools such as Stape.io.
“You need to set up your conversion tracking through GTM and Stape.io or other software”
Google advises scoping default consent settings to the regions where you show consent banners, so you do not lose measurement where banners do not apply.
“It is best practice to scope the default consent settings to the regions where you are surfacing consent banners to your visitors.”
Google's Stephen Chang says upgrading to Google Tag Gateway can recover 14% more conversions.
“We can get 14% more conversions if we upgrade to Google Tag Gateway.”
Matteo Zambon, who sells tag management services, says Google's visual tagging beta leaves the hard 20% of tracking, such as consent mode, server-side setups and Shopify checkout, still manual.
“None of this gets solved by clicking on a button on the page.”
PPC Rebels says server-side tagging starts to pay at about $3,000 to $5,000 monthly spend and 100+ conversions, assuming it recovers 10 to 20% of signal, a benchmark it shows no data for.
“Run both for one to two weeks and reconcile three numbers: conversions in the ad account, orders in the CRM, events in the server container.”
Taggrs, which sells server-side tagging, says Enhanced Conversions sends nothing when ad_user_data consent is denied, and pre-hashed emails never match; send the raw value and let the tag hash it.
“The fix is to always send the raw value and let GTM or gtag.js handle the hashing.”
PPC Land reports Google closed the legacy API path for offline conversion uploads from June 15, 2026. Teams not on the Data Manager API will get an error calling the old upload method.
“Teams that have not already adopted the Data Manager API will receive an error when calling the ConversionUploadService.UploadClickConversions method.”
Google Tag Manager release notes say Google tag gateway for advertisers became available with Akamai and Fastly on May 14, 2026, Google Cloud Platform on June 1, and Amazon CloudFront on June 3.
“Google tag gateway for advertisers via Google Cloud Platform is now available”
In the full answer
For readers who sign in- What to do this week3 steps
- The numbers behind it3 figures from cited sources
- Where each source standsA chart placing each source on the question
- The strongest disagreementThe best case against the answer, from a cited source
- How sure we areWhat its confidence rests on, and what would change the answer