Standard Google Ads conversion tracking was built for a world where third-party cookies worked reliably across all browsers and devices. That world is gone. Between Safari's Intelligent Tracking Prevention, iOS App Tracking Transparency, Chrome's ongoing cookie changes, and users who simply clear their cookies between clicking an ad and converting, a meaningful percentage of your conversions are never attributed back to the campaigns that drove them. Enhanced conversions are Google's first-party solution to this problem — and for most advertisers running Google Ads today, they're no longer optional.
What Are Enhanced Conversions?
Enhanced conversions are a Google Ads feature that supplements your existing conversion tags by sending hashed first-party customer data — email address, phone number, name, and home address — alongside your conversion events. Google matches this hashed data against signed-in Google accounts to attribute conversions that standard cookie-based tracking would miss.
The key word is supplement. Enhanced conversions don't replace your existing Google Ads conversion tags — they layer on top of them. When a standard cookie match is available, Google uses it. When it isn't — because the user converted on a different device, cleared cookies, or is on a browser that blocks third-party tracking — the hashed customer data provides an alternative identity signal to complete the attribution.
Why Standard Conversion Tracking Has Gaps
Standard Google Ads conversion tracking relies on a cookie dropped when someone clicks your ad. When that user converts on your site, the conversion tag reads the cookie and sends the match back to Google. This works reliably when the same browser, on the same device, completes the conversion without blocking or clearing cookies.
That's a narrower scenario than most advertisers assume. Here's where signal is lost:
Cross-device journeys. A user clicks your ad on their phone during lunch, then converts on their laptop that evening. The click cookie is on the phone; the conversion happens on the laptop. Standard tracking misses the attribution entirely. According to Google's enhanced conversions documentation, cross-device conversions are one of the primary gaps this feature addresses.
Safari and iOS restrictions. Safari's Intelligent Tracking Prevention (ITP) aggressively limits third-party cookie lifespans — in some cases to as little as 24 hours. For campaigns with longer consideration cycles, the click cookie may expire before the user converts. iOS 14+ App Tracking Transparency has further reduced the signal available from Apple device users.
Privacy-focused browsers and extensions. Firefox, Brave, and browser extensions like uBlock Origin block or delete tracking cookies. Users on these browsers convert without any attribution signal reaching Google Ads.
Cookie clearing. Users who clear their browser cookies between clicking and converting — a small but consistent percentage — break the attribution chain entirely.
The cumulative effect is significant. For most advertisers, 10–30% of actual conversions go unmeasured in Google Ads, depending on traffic mix and audience behavior. This doesn't just affect reporting — it directly degrades Smart Bidding performance, because Target CPA and Target ROAS strategies are only as accurate as the conversion data they're trained on.
Enhanced Conversions for Web vs. for Leads
Google offers two distinct enhanced conversions products, and they solve different problems. Using the wrong one for your business is one of the most common implementation mistakes we see.
Enhanced Conversions for Web
Enhanced conversions for web is designed for businesses where the conversion completes on the website — purchases, demo bookings, account signups, subscription starts. The customer data is available on the conversion confirmation page (typically a thank-you page or order confirmation page) at the moment the conversion tag fires.
How it works: when your Google Ads conversion tag fires on the confirmation page, it also reads the customer's email address (and optionally phone, name, address) from the page — either from a form field the user just filled out, a confirmation element on the page, or a dataLayer variable. The tag hashes this data using SHA-256 before sending it to Google. Google then attempts to match the hash against a signed-in Google account and attribute the conversion to the originating click.
This is the right product for ecommerce, SaaS self-serve signups, and any business where the entire conversion journey happens on the site.
Enhanced Conversions for Leads
Enhanced conversions for leads is designed for businesses with a sales cycle: a prospect fills out a contact form or requests a demo on the site, but the actual conversion — a signed contract, a closed deal, a qualified appointment — happens offline, days or weeks later.
How it works: when the lead submits a form, your tag captures and hashes their email address and passes it to Google as a "lead" conversion. Later, when that lead converts in your CRM, you export the conversion data (including the hashed email and conversion timestamp) and import it back into Google Ads. Google matches the hashed email to the original lead form submission, then traces that back to the ad click that drove the lead — giving you a complete click-to-closed-deal attribution chain.
This is the right product for B2B companies, professional services, high-consideration purchases, and any business that closes deals offline or over the phone. For this model to work, your CRM needs to store lead emails in a way that can be exported for the offline conversion import.
How the Hashing Works
The privacy mechanism that makes enhanced conversions compliant is SHA-256 hashing. Before any customer data leaves the browser, the enhanced conversions tag converts the raw value — an email address like john@example.com — into a fixed-length hash string: 973dfe...a8b91f. This one-way transformation cannot be reversed to recover the original email address.
Google's matching process works because the same person's email, hashed the same way, produces the same hash value every time. Google maintains its own hashed database of signed-in Google account emails. When your hashed conversion data arrives, Google compares hashes. A match links the conversion to the account — and from there, to the ad click that account made. No raw email is ever stored or compared.
The data processing also respects Consent Mode V2: for EEA traffic, Google only uses the enhanced conversion data for matching when the user has granted ad_storage and ad_user_data consent. Without those consent signals, the data is collected but not used for matching — keeping your implementation compliant without requiring you to conditionally suppress the tag.
How to Set Up Enhanced Conversions for Web (via GTM)
The GTM implementation is the most common path for enhanced conversions for web. Here's the practical setup:
Step 1: Enable Enhanced Conversions in Google Ads
In Google Ads, go to Tools → Conversions → Settings → Enhanced conversions. Accept the customer data terms and enable the feature. This is required before the tags will accept and process the hashed data.
Step 2: Capture User-Provided Data with Your Conversion Event
Enhanced conversions needs to read customer data from your confirmation page. Common sources:
- A dataLayer push — the most reliable method. Have your developer push the customer data to the dataLayer on the confirmation page:
{'event': 'purchase', 'email': 'john@example.com', ...}. GTM reads it from there. - CSS selectors — GTM can scrape visible text from the page if the email or name appears in a confirmation message. Less reliable if page structure changes.
- JavaScript variables — if your site stores the customer object in a JS variable accessible on the confirmation page, GTM can read it directly.
The dataLayer approach is strongly preferred. It's explicit, reliable, and doesn't break when design teams update confirmation page layouts.
Step 3: Configure GTM Variables for Customer Data
In GTM, create Data Layer Variables (or JavaScript Variables, depending on your data source) to capture each field — email, phone, first name, last name. You only need email to get started; the others improve match rates but aren't required.
Step 4: Configure the User-Provided Data Tag in GTM
In your existing Google Ads Conversion Tracking tag in GTM, enable the "Include user-provided data from your website" option. Map the customer data fields to the GTM variables you created in Step 3. The tag template handles the SHA-256 hashing automatically — you never need to write custom hashing code.
Step 5: Test the Implementation
Use GTM Preview mode to walk through a test conversion. In the tag output, confirm that the user_data object is being populated with your hashed customer fields. Then verify in Google Tag Assistant that the enhanced conversion payload is included in the conversion hit. Allow 2–3 days after deployment for enhanced conversion data to appear in your Google Ads reporting.
How to Set Up Enhanced Conversions for Leads
The leads setup has two parts: capturing the hashed lead email at form submission, and importing the offline conversion when the lead closes.
For the tag side, the setup is similar to enhanced conversions for web — your lead form submission tag captures the hashed email and sends it to Google with a "lead" conversion event. The difference is what happens after: instead of Google attributing a completed conversion immediately, it holds the lead event and waits for the import.
For the offline import, you export closed deals from your CRM with the lead's email (or Google's gclid if you're capturing it at form submission) and the conversion timestamp. Google Ads accepts this as a bulk upload via the Conversions → Upload section, or via the Google Ads API for automated imports. Salesforce, HubSpot, and most major CRMs have native Google Ads integrations that can automate this process.
The lookback window for connecting an imported conversion to its original lead event is 90 days by default. Deals that close after 90 days won't be connected to the original click unless you extend this window in your Google Ads conversion settings.
Common Enhanced Conversions Mistakes
Implementing without enabling in the Google Ads account first. The GTM tag will fire but the data will be silently ignored if you haven't accepted the customer data terms and enabled enhanced conversions in Google Ads account settings. Always start in the Google Ads interface, not GTM.
Using "automatic" data collection. GTM's automatic collection method attempts to detect customer data from the page without any configuration — it sounds convenient, but it's unreliable. It depends on recognizing specific form field patterns and page structures that vary widely across sites. A dataLayer push from your backend confirmation logic is explicit, controlled, and won't silently break when your site is updated.
Sending unformatted data. Google's matching requires the email address to be lowercase and trimmed of whitespace before hashing. GTM's enhanced conversions template normalizes this automatically — but if you're implementing via gtag.js directly or via the API, you need to normalize the data yourself. A mismatch between how you hash and how Google hashes the same email will result in zero matches.
Conflating enhanced conversions for web with enhanced conversions for leads. B2B companies sometimes set up enhanced conversions for web (which fires at form submission and immediately reports a conversion) when they actually need enhanced conversions for leads (which defers the conversion until the CRM closes the deal). The result is that all leads count as conversions, which trains Smart Bidding on lead volume rather than actual revenue — often a significant bidding mistake.
Forgetting to audit existing conversion actions. Enhanced conversions only improves measurement on conversion actions where the feature is explicitly enabled. If you have multiple conversion actions in Google Ads — purchases, signups, phone calls, micro-conversions — each one needs to be evaluated and configured separately. A partial rollout means you're getting improved data on some conversions but not the ones that matter most.
Frequently Asked Questions
Enhanced conversions are a Google Ads feature that supplements standard conversion tracking by sending hashed first-party customer data — email address, phone number, name, and home address — alongside your conversion events. Google matches this hashed data against signed-in Google accounts to attribute conversions that are missed by standard cookie-based tracking, recovering signal lost to cross-device journeys, cookie restrictions, and browser privacy changes.
Enhanced conversions for web applies to online conversion actions — purchases, signups, form completions — where the customer's data is available on the conversion page at the time the conversion tag fires. Enhanced conversions for leads is designed for businesses where a lead submits a form on the site, but the actual conversion happens later offline. For leads, you capture the hashed email at form submission, then import the conversion back to Google Ads when the lead converts — linking the original click to the eventual sale.
Yes. Customer data is hashed using SHA-256 before it leaves the browser — Google never receives the raw email or phone number. The hashed value cannot be reversed to recover the original data. For EEA traffic, enhanced conversions must be used alongside Consent Mode V2: Google will only use the hashed data for matching when the user has granted ad_storage and ad_user_data consent.
Results vary by industry, traffic mix, and how much cross-device and privacy-restricted traffic your campaigns generate. Google has reported average improvements of 5–15% in measured conversions, with some verticals seeing significantly more. The gain is largest for advertisers with high mobile-to-desktop conversion paths, significant iOS traffic, or audiences that frequently clear cookies or browse in private mode.
Yes — they solve different problems. GA4-imported conversions still rely on GA4's own measurement, which has the same cookie and cross-device gaps as standard Google Ads tags. Enhanced conversions specifically add the first-party identity matching layer that closes those gaps. Running both GA4 conversion imports and enhanced conversions gives you the most complete picture and the strongest bidding signal.
Is Your Google Ads Conversion Tracking Costing You Performance?
Missing conversions means degraded Smart Bidding signals and inaccurate reporting. Get a free assessment of your current setup — we'll tell you exactly where the gaps are.
Get a Free Assessment