TL;DR
- Enhanced conversions are a Google Ads feature that recovers conversion data lost to ad blockers and browser privacy restrictions.
- They work by hashing first-party customer data — email, phone, name — and sending that fingerprint to Google for matching against signed-in accounts.
- There are two variants: Enhanced Conversions for Web (on-site transactions) and Enhanced Conversions for Leads (offline CRM-to-click matching).
- Data is hashed with SHA-256 before it leaves your browser or server. Google never receives raw personal information.
- You can implement via the Google tag, Google Tag Manager (GTM), or the Google Ads API (server-side). Server-side is the most durable.
- Without it, every conversion from an ad-blocked or privacy-restricted session is invisible — and your Smart Bidding is optimizing on incomplete data.
What Enhanced Conversions Are — and the Problem They Solve
Enhanced conversions are a Google Ads feature that recovers conversion data lost to ad blockers and browser privacy restrictions by sending hashed first-party customer data to Google for matching.
Standard Google Ads conversion tracking works by firing a tag in the user's browser when they complete an action — a purchase, a form fill, a phone call. That tag drops a cookie and reports back to Google. It has worked this way for years.
It is breaking down.
Ad blockers, browser-level tracking prevention (Safari's Intelligent Tracking Prevention, Firefox Enhanced Tracking Protection), and users who simply decline cookie consent prompts all prevent that tag from firing. When the tag doesn't fire, the conversion doesn't register. You paid for the click. The sale happened. Google Ads has no idea.
Without enhanced conversions, a conversion completed by a user with an ad blocker or a privacy-focused browser setting is simply invisible to Google Ads — you paid for the click, but the result never registers.
The downstream effect is worse than a reporting gap. Google's Smart Bidding — Target CPA, Target ROAS, Maximize Conversions — learns from conversion signals. Feed it incomplete data and it optimizes for the wrong users. It bids less aggressively on the sessions most likely to convert because those sessions aren't showing up as conversions.
Campaigns optimizing on incomplete conversion data bid less aggressively for the users most likely to convert, which depresses performance even before you look at reporting.
Enhanced conversions address this at the source. Instead of relying solely on a cookie-based browser tag, they supplement the signal by capturing first-party data the user voluntarily submitted — their email address when they bought something or filled out your form — hashing it, and sending it to Google. Google then matches that hash against its own signed-in user database to attribute the conversion.
Why Browser Restrictions and Ad Blockers Break Standard Tracking
The mechanics matter because the solution only makes sense once you understand what's breaking.
A standard conversion tag is a piece of JavaScript that runs in the user's browser. It reads cookies, identifies the session, and pings Google's servers. Three things can stop it:
Ad blockers maintain lists of known tracking domains and scripts. Google's conversion tag URLs are well-known. A significant share of desktop users run ad blockers, and the adoption rate is higher among the tech-savvy audiences — developers, marketers, finance professionals — who often represent high-value conversions.
Browser privacy features like Safari's ITP limit how long cookies can persist and restrict cross-site tracking. Even without an explicit ad blocker, a user on Safari may have their conversion attribution window shortened or broken entirely.
Consent management failures occur when a user declines the cookie banner on your site. If your consent management platform is configured correctly, the Google tag should not fire for non-consenting users — which is the right legal posture but leaves a data gap.
None of these are going away. Browser vendors and regulators are moving in one direction: less third-party tracking, not more. The right response is to build your measurement infrastructure around first-party data you own, which is exactly what enhanced conversions are designed for.
Enhanced Conversions for Web vs. Enhanced Conversions for Leads
Google has built two distinct implementations under the enhanced conversions umbrella. They solve different problems.
Enhanced Conversions for Web
This is the implementation most e-commerce and lead-generation sites need first. It activates at the moment a user completes an on-site conversion — a purchase confirmation page, a thank-you page after a form submission, a checkout completion.
At that moment, the user has just given you their information: email, phone, name, possibly address. Enhanced Conversions for Web takes that data, hashes it in the browser or on your server before transmission, and sends the hash to Google alongside the standard conversion ping. If the cookie-based signal is blocked, Google can still use the hash to find the conversion in its own records.
The data is hashed with SHA-256 before it leaves your site or server, so Google never receives a raw email address — only an anonymized fingerprint it can match against signed-in Google accounts.
This implementation helps immediately with on-site conversions where the user has authenticated or submitted a form. It does not help with offline outcomes — phone calls that turn into signed contracts, for example.
Enhanced Conversions for Leads
This is the implementation for businesses where the real conversion happens offline. A user clicks your ad, fills out a contact form, and then — days or weeks later — becomes a paying customer after a sales call or consultation.
Standard tracking records the form fill as the conversion, which is fine as a proxy but means Smart Bidding is optimizing for people who fill out forms, not people who become customers. If your close rate varies significantly by traffic source or audience, that's a real problem.
Google offers two variants: Enhanced Conversions for Web captures on-site purchases and form fills, while Enhanced Conversions for Leads matches offline sales outcomes back to the original ad click.
Enhanced Conversions for Leads works differently. At the form-fill stage, you capture the user's email and store it in your CRM alongside the lead record. When that lead converts — when they sign a contract, make a purchase, become a client — you upload that email to Google Ads. Google hashes it, matches it to the original click, and records the actual business outcome as the conversion event.
This gives Smart Bidding a far stronger signal. It learns to optimize for the audience characteristics of people who became customers, not just people who raised their hand.
For any service business — law firms, home services, financial advisors, B2B companies — Enhanced Conversions for Leads is arguably more valuable than the web variant because it closes the loop between ad spend and actual revenue. This is a core part of how we build conversion tracking pipelines for clients at RGDM.
How Hashed First-Party Data Flows to Google
The privacy architecture is worth understanding clearly, both because it's technically sound and because you may need to explain it to a compliance-conscious client or stakeholder.
SHA-256 hashing is a one-way cryptographic function. You feed in an email address — user@example.com — and get out a fixed-length string of characters. You cannot reverse the hash to get the original email. Google receives the hash, compares it to hashes of email addresses in its own signed-in user database, and records a match if one exists. No raw personal data crosses from your server to Google's.
Before hashing, Google also normalizes the data: lowercasing the email, stripping whitespace, standardizing phone number formatting. This improves match rates because the same person may have submitted their email in slightly different formats across different touchpoints.
The entire process — normalization, hashing, transmission — is handled automatically by the Google tag or GTM when configured correctly. If you're using the API (server-side), your server does the hashing before sending the request.
Match rates vary depending on how many of your converting users are signed in to a Google account at the time of conversion. You won't see a 100% match rate, and Google doesn't publish a universal benchmark — match rates depend on your audience, your industry, and the quality of the email data you capture.
Setup: GTM vs. Google Tag vs. API
There are three implementation paths. The right one depends on your technical setup and how much durability you need.
Google Tag (gtag.js) — Simplest, Most Fragile
If you're already using gtag.js directly on your site, enabling enhanced conversions is primarily a configuration change in Google Ads plus a code update to pass customer data variables to the tag. Google's enhanced conversions setup documentation walks through the exact parameter structure.
The limitation: this still fires from the browser. An ad blocker that blocks the Google tag domain blocks the enhanced conversion signal too. It's better than nothing, but it's not the most resilient setup.
Google Tag Manager — Practical Middle Ground
GTM is the most common implementation path for sites that already have a GTM container. You configure the Google Ads conversion tag in GTM to include the user-provided data variables — email, phone, name — which GTM hashes before sending.
This works well and is faster to deploy than a server-side setup. The same browser-side limitation applies: a blocker that suppresses your GTM container also suppresses the enhanced conversion data. GTM's server-side container (sGTM) solves this, moving tag firing off the browser.
Google Ads API / Server-Side — Most Durable
Server-side implementation via the Google Ads API is the most resilient setup because it moves tag firing off the browser entirely, bypassing client-side blockers.
The Google Ads API lets you upload conversion events directly from your server, with hashed customer data included. Because nothing runs in the browser, ad blockers have no surface to intercept. This is the recommended path for high-spend accounts where measurement accuracy compounds into real money.
Server-side GTM (sGTM) is a middle path: your GTM container moves to a server you control, tags fire server-side, and you retain GTM's configuration interface without the browser vulnerability. This is often the most practical upgrade for clients already on GTM.
For clients running significant paid media budgets, we default to server-side implementations because the measurement fidelity difference is material at scale. You can see how this fits into a full conversion tracking build on our conversion tracking service page.
What to Expect After Turning It On
A few things happen after enhanced conversions is active and passing data.
Conversion volume goes up. You'll see conversions that were previously invisible start registering. This is real volume that was always happening — you just couldn't see it. Don't mistake the increase for a performance improvement; it's a measurement improvement. Baseline performance comparisons across before/after periods need to account for this.
Smart Bidding improves over time. Better signals in means better bid decisions out. The improvement is not instant — Smart Bidding needs a learning period to incorporate the new signal. How long depends on conversion volume and how much the new signal changes the picture.
Match rates need monitoring. Google Ads will report a match rate for the hashed data. If your match rate is low, check whether you're passing email consistently, whether normalization is happening correctly, and whether your audience is the type that tends to be signed in to Google accounts (B2C audiences tend to have higher match rates than B2B).
The data gap doesn't disappear entirely. Enhanced conversions improve measurement significantly, but they're not a complete fix for every missing conversion. Users who aren't signed into a Google account can't be matched. Users who completed the conversion on a different device from the one they searched on may not match. Enhanced conversions are a substantial improvement to the signal, not a claim of perfect attribution.
For a fuller picture of where conversions go missing and how to recover them across channels, the paid media management systems we deploy include enhanced conversions as a baseline requirement — not an optional add-on.
Frequently Asked Questions
What are enhanced conversions?
Enhanced conversions are a Google Ads feature that improves conversion measurement accuracy by supplementing standard cookie-based tracking with hashed first-party data. When a user completes a conversion — a purchase, a form fill — their submitted information (email address, phone number) is hashed using SHA-256 and sent to Google. Google matches the hash to its own signed-in user records, recovering conversions that would have been missed because of ad blockers or browser privacy restrictions.
Do enhanced conversions improve performance?
Yes, indirectly. Enhanced conversions do not directly change your bids or ads. They improve the quality and completeness of the conversion signal that Google's Smart Bidding algorithms use to optimize. More complete conversion data means Smart Bidding makes better decisions about which users to bid aggressively for — which tends to improve actual performance over time as the algorithms learn from a cleaner signal. The most immediate effect is better measurement; the performance effect follows as Smart Bidding incorporates the improved data.
What is the difference between enhanced conversions for web and enhanced conversions for leads?
Enhanced Conversions for Web captures on-site conversions at the moment they happen — a purchase, a thank-you page after a form — by hashing customer data submitted during that session. Enhanced Conversions for Leads is designed for businesses where the real conversion happens offline. You capture the user's email at the form-fill stage, then upload it to Google Ads when that lead later converts in your CRM. This closes the loop between the original ad click and the actual business outcome.
Is the customer data safe when using enhanced conversions?
The data is hashed with SHA-256 before it leaves your site or server. SHA-256 is a one-way hash — it cannot be reversed to recover the original email address. Google receives only the hash, uses it for matching, and does not store raw personal data. You remain the data controller; you decide what data to pass and can configure what fields to include.
What data can I send with enhanced conversions?
Google supports email address, phone number, first name, last name, street address, city, state, postal code, and country. Email is the highest-match field and is the primary variable most implementations rely on. Phone number is a secondary option. Sending multiple fields improves match rates because Google can attempt matching on more than one signal.
Do I need Google Tag Manager to set up enhanced conversions?
No. You can implement enhanced conversions using the Google tag (gtag.js) directly on your site, through Google Tag Manager, or via the Google Ads API for server-side uploads. GTM is the most common implementation for sites that already have a GTM container. The Google Ads API is the most technically involved but also the most durable, as it moves tag firing off the browser entirely.
How long does it take to see results after enabling enhanced conversions?
You should see hashed data flowing within a day or two of a correct implementation, assuming conversions are occurring. Match rate data appears in the Google Ads interface and can be monitored there. Smart Bidding improvements are slower to materialize — the algorithms need a learning period, which varies by account but is typically measured in weeks, not days. Conversion volume increases are visible sooner because previously untracked conversions start registering immediately.
Does enhanced conversions work with consent management platforms?
Yes, with configuration. If a user has declined cookie consent, your consent management platform (CMP) should prevent tags from firing — including the Google tag that would capture the enhanced conversion data. In a properly configured consent setup, enhanced conversions can only fire for users who have consented. This is the correct posture from a privacy standpoint. Some of the measurement gap from non-consenting users can be addressed through Google's consent mode, which uses modeled conversion data to fill gaps where consent was not given.
If your conversion data is incomplete, your paid media performance reflects that — whether you can see it or not. Enhanced conversions are the single highest-leverage fix for most Google Ads accounts running on Smart Bidding. If you want to audit what your current tracking is missing and build a measurement infrastructure around first-party data you actually own, book a strategy call.