Google Enhanced Conversions: how to set up server-side conversion tracking on Google.

What Google Enhanced Conversions is

Google Enhanced Conversions sends hashed first-party customer data (email, phone) alongside conversion events to Google Ads. Google uses the hashed data to match conversions to authenticated Google users, recovering attribution that was lost when browser cookies and IDFA stopped working reliably. Two modes exist: Enhanced Conversions for Web (Google Tag fires both pixel and hashed PII) and Enhanced Conversions for Leads (uploaded via API for offline lead conversion).

Google launched Enhanced Conversions in 2021 as the recommended response to iOS ATT and cookie deprecation. By 2024, it had become a default recommendation for any advertiser running paid Google Ads campaigns with conversion-based bidding strategies (tCPA, tROAS, Max Conversions).

Why every Google Ads advertiser needs it

Google's bidding algorithms train on conversion data. Without Enhanced Conversions, the algorithm sees only the conversions the browser pixel managed to fire — typically 60-75 percent of actual conversions post-ATT. With Enhanced Conversions, hashed first-party data lets Google match conversions to user profiles directly, raising the observed conversion volume by 15-30 percent and improving bid optimization.

Setup walkthrough

1. Enable Enhanced Conversions in Google Ads.Tools > Conversions > select the conversion action > Enhanced conversions section > toggle on.
2. Choose your implementation method.Google Tag (gtag.js), Google Tag Manager, or the Google Ads API. GTM is the most flexible for non-developer teams.
3. Pass first-party data to the conversion tag.Email, phone, first name, last name, address. Google handles the SHA-256 hashing in the gtag.js implementation.
4. Validate matched conversions.Google Ads shows a Match Rate metric per conversion action. Aim for 70 percent or higher.
5. Pair with Google Tag Manager Server-Side.For accounts running sGTM, the server-side path improves data quality and survives client-side blocking.

Payload format and required fields

Enhanced Conversions accepts at minimum hashed email (em) or hashed phone (ph). Additional fields (first name, last name, address) improve match rates further. Hashing is SHA-256 lowercase with whitespace trimming. The Google Tag handles this automatically; manual API uploads require explicit hashing.

Deduplication and double-counting

Enhanced Conversions does not double-count by default. The Google Tag fires the conversion once and includes the hashed PII as additional data on the same event. Manual API uploads need to use the same conversion_action and a unique gclid or conversion_id to avoid duplication.

Common implementation mistakes

Three failures. Sending un-normalized PII (uppercase email, phone with formatting) producing low match rates. Not enabling Enhanced Conversions in Google Ads before sending data. Missing the conversion action's user-provided-data setting.

Quick answers

What is Google Enhanced Conversions?

First-party PII (email, phone) sent hashed alongside Google Ads conversion events. Google uses the data to match conversions to authenticated user profiles.

Do I need Enhanced Conversions?

Yes if you run conversion-based bidding (tCPA, tROAS, Max Conversions). Without it, post-ATT conversion data is incomplete and bidding suffers.

How much lift in observed conversions?

Typically 15-30 percent more attributed conversions vs. pixel-only post-ATT.

What is the difference between Enhanced Conversions for Web and for Leads?

Web fires through gtag.js/GTM with the page conversion. Leads is for offline lead-to-sale conversions uploaded via API.

Does it work with sGTM?

Yes. Server-side Google Tag Manager passes the hashed data with the conversion event. Recommended for sGTM-equipped accounts.

How do I check match rate?

Google Ads shows match rate per conversion action. 70 percent or higher is the standard target.

Frequently asked

What is Google Enhanced Conversions?

Google Enhanced Conversions sends hashed first-party data (email, phone) alongside conversion events to Google Ads. Google matches the hashed data to authenticated user profiles, recovering attribution lost to cookies and iOS ATT.

Why did Google launch Enhanced Conversions?

Browser cookie restrictions and iOS ATT broke pixel-based conversion tracking. Google needed a way to maintain bidding signal quality. Enhanced Conversions launched in 2021 as the response.

How is Enhanced Conversions different from Meta CAPI?

Same fundamental idea (first-party data sent server-side) with different mechanics. Meta CAPI is a server-to-server endpoint that runs in parallel with the Pixel. Google Enhanced Conversions adds hashed PII to existing conversion tags.

What are Enhanced Conversions for Leads?

A variant for offline lead-to-sale conversions. Upload qualified-lead conversions via API with the lead's hashed PII. Google attributes them back to the original ad click.

Does Enhanced Conversions work for Performance Max?

Yes. Recommended for all conversion-based bidding strategies (tCPA, tROAS, Max Conversions, Performance Max). The improved signal directly impacts bidding optimization.

How does match rate work?

Google Ads reports match rate per conversion action. The percentage of conversions that Google successfully matched to user profiles. 70 percent or higher is the standard target; below 50 percent indicates implementation issues.

Does Enhanced Conversions require server-side tagging?

No, gtag.js and GTM both support it client-side. Server-side sGTM is the recommended implementation for accounts that have it, because the data quality is higher and the implementation survives client-side blocking.

How long does implementation take?

1-3 weeks for most accounts. Faster than Meta CAPI because Enhanced Conversions integrates into the existing Google Tag rather than requiring a parallel server-side stack.