Google Ads Enhanced Conversions: Setup, Hashing, and Benefits in 2026

Table Of Contents

• What Changed in Enhanced Conversions in 2026
• Standard vs Enhanced Conversions: What's the Difference
• How Enhanced Conversions Works — Technical Overview
• Setup Method 1: via gtag.js (Recommended for Developers)
  • Step 1: Enable Enhanced Conversions in Google Ads
  • Step 2: Configure the Conversion Action
  • Step 3: Add user_data to Your Conversion Event
  • Step 4: Implement Server-Side Pre-Hashing (GDPR-Recommended)
• Setup Method 2: via Google Tag Manager
• Verifying Enhanced Conversions Are Working
  • Check in Google Ads UI
  • Check via Tag Assistant
  • Check via Network Tab
• Enhanced Conversions for Leads (Offline Use Case)
• Common Issues and Fixes
• Quick Start Checklist
• What to Read Next

TL;DR: Enhanced Conversions fills the gaps in your conversion data caused by cookie blocking, ITP, and Consent Mode restrictions — by hashing first-party user data and matching it to signed-in Google accounts. According to Google, it improves conversion measurement by 5-15% on average. Run it on verified Google Ads accounts with existing conversion history to see the fastest impact.

Enhanced Conversions works by taking hashed first-party data (email address, phone number, name) that users submit on your site, and using it to match conversions back to Google's own user database — bypassing the limitations of cookie-based tracking. The result: more complete attribution data, better Smart Bidding signals, and more accurate reporting.

What Changed in Enhanced Conversions in 2026

• Enabled by default for all new Google Ads accounts created from January 2026 — opting out requires a manual action in conversion settings
• Enhanced Conversions for Leads is now listed as the primary offline conversion method in Google's documentation — manual GCLID upload is still available but not recommended for new setups
• SHA-256 hashing is now handled automatically by the Google Tag if you pass data in plain text — but server-side pre-hashing is still the recommended approach for GDPR compliance
• Consent Mode v2 integration: Enhanced Conversions works in modeling mode even when ad_user_data is denied — Google models likely conversions using aggregated signals
• According to Google, Enhanced Conversions improves bid optimisation accuracy, contributing to a 5% average improvement in conversion measurement for web and 5-15% for leads

Standard vs Enhanced Conversions: What's the Difference

How Enhanced Conversions Works — Technical Overview

1. User clicks your Google Ad → lands on your site
2. User completes a form or checkout (enters email/phone)
3. Your gtag.js fires a conversion event AND passes the user_data object
4. Google hashes the data with SHA-256 (or accepts pre-hashed values)
5. Google matches the hash against its database of signed-in Google users
6. If matched: conversion is attributed to the correct ad click — even if cookies were blocked
7. If not matched: standard cookie/GCLID attribution is used as fallback

The match rate typically runs 60-85% depending on how many of your users are signed into Google accounts.

Related: Google Tag (gtag.js) Setup and Troubleshooting for Google Ads 2026

Setup Method 1: via gtag.js (Recommended for Developers)

Step 1: Enable Enhanced Conversions in Google Ads

Go to Goals → Summary → Settings (gear icon) → Enhanced conversions. Toggle on "Turn on enhanced conversions for web". Accept the data terms.

Step 2: Configure the Conversion Action

In your conversion action settings (Goals → Conversions → your action), under "Enhanced conversions", select "Google tag" as the method.

Step 3: Add user_data to Your Conversion Event

// On your thank-you page or in your form submit handler
gtag('event', 'conversion', {
  'send_to': 'AW-XXXXXXXXX/YYYYYYYYYYYY',
  'value': 99.00,
  'currency': 'USD',
  'transaction_id': 'ORDER-12345',
  'user_data': {
    'email_address': '[email protected]',  // Google auto-hashes plain text
    'phone_number': '+12025551234',        // E.164 format
    'address': {
      'first_name': 'Jane',
      'last_name': 'Smith',
      'street': '123 Main St',
      'city': 'New York',
      'region': 'NY',
      'postal_code': '10001',
      'country': 'US'
    }
  }
});

⚠️ Important: When passing user data in plain text, Google hashes it client-side before transmission. However, plain text PII briefly exists in the browser's memory. For GDPR-compliant implementations, pre-hash with SHA-256 on your server and pass only hashed values in the user_data object. The format for pre-hashed values is a lowercase hex string.

Related: Google Ads Conversion Tracking Setup: GTM, Enhanced Conversions, and Everything in Between

Step 4: Implement Server-Side Pre-Hashing (GDPR-Recommended)

import hashlib

def sha256_hash(value):
    normalized = value.strip().lower()
    return hashlib.sha256(normalized.encode('utf-8')).hexdigest()

hashed_email = sha256_hash(user_email)
hashed_phone = sha256_hash(user_phone_e164)

Pass the hex string to user_data. Google recognises pre-hashed values automatically.

Running conversion-optimised campaigns with Smart Bidding? Verified Google Ads accounts with existing spend data reach Smart Bidding's optimal performance threshold faster than fresh accounts — you're not starting from zero conversion history.

Setup Method 2: via Google Tag Manager

For teams using GTM instead of direct gtag.js:

1. Open GTM → Tags → New → Google Ads Conversion Tracking
2. In "Enhanced conversions", select "User-provided data"
3. Create a new User-Provided Data variable: map your form fields to the corresponding data types (Email, Phone, First Name, Last Name)
4. Set the trigger to fire on your thank-you page or form submit confirmation

GTM's built-in template handles the hashing automatically. You don't need to write custom JavaScript.

Related: How to Set Up Offline Conversions and Link CRM Sales to Google Ads

Verifying Enhanced Conversions Are Working

Check in Google Ads UI

After 24-72 hours: Goals → Conversions → your conversion action → Diagnostics. Look for "Enhanced conversions data quality: Good". If it shows "Limited", the match rate is below 30% — check that form fields are populated before the conversion fires.

Check via Tag Assistant

Tag Assistant (Chrome DevTools) shows the user_data object in the event payload. Verify it contains at least email or phone. If the object is empty (user_data: {}), your tag is passing but Enhanced Conversions has no data to work with.

Check via Network Tab

Look for the conversion request to https://googleads.g.doubleclick.net/pagead/viewthroughconversion/. In the request payload (POST body), search for em (email) or pn (phone) parameters — these indicate Enhanced Conversion data was sent.

Case: B2C e-commerce, apparel vertical, Google Shopping + Search, $800/day budget. Problem: iOS 17 update (ITP) wiped 28% of conversion attribution. Smart Bidding was under-bidding on mobile because it saw far fewer mobile conversions than actually occurred. Action: Enabled Enhanced Conversions via gtag.js, passing hashed email from checkout form. Used GTM for the conversion event, server-side hashing in the checkout backend. Result: Attributed mobile conversions increased 31%. Smart Bidding re-calibrated within 2 weeks, raising mobile bids appropriately. ROAS improved from 2.4x to 3.1x. According to Google, average ROAS for e-commerce Shopping is 3-5x (Store Growers, 2025) — they crossed into the target range.

Enhanced Conversions for Leads (Offline Use Case)

For lead gen where the conversion happens offline (sales call, in-person meeting), Enhanced Conversions for Leads works differently:

1. User submits a form on your website → you store their email/phone
2. When the lead converts offline (deal closed, appointment kept), you upload that email/phone hash to Google Ads
3. Google matches the hash to the original ad click — even without a GCLID

This is more resilient than traditional offline conversion imports because it doesn't require GCLID capture in the CRM. The match rate is typically 50-75%.

Setup: Goals → Conversions → your offline conversion action → Enhanced conversions for leads → On.

⚠️ Important: Enhanced Conversions for Leads requires that the user submitted a form on your website at some point — Google needs to record the hash at the time of the form submission. If you're trying to match conversions from phone calls only (no web form), you need traditional GCLID-based offline conversion imports instead.

Common Issues and Fixes

Match rate below 30% Most likely cause: the user_data object is being populated after a partial form submit, or the email field is populated but the format is non-standard (has trailing spaces, uppercase). Normalise all data: email.trim().toLowerCase().

Enhanced Conversions "Limited" status Not enough data. Need at least 100 enhanced conversion events per month for Google to validate data quality. Below that, it works but shows "Limited" — keep running it, the status improves with volume.

Duplicate conversion events Both standard conversion tag AND enhanced conversion tag firing for same event. Check that you have a single conversion event with user_data attached, not two separate events.

GDPR / data transfer concern Google commits in its DPA (Data Processing Agreement) that Enhanced Conversion data is used only for conversion measurement and bidding, not for audience targeting or profile building. Review Google's EU-US Data Privacy Framework compliance documentation if your legal team requires it.

Case: Lead gen for finance vertical, $250/day budget, EU-focused campaigns. Problem: After Consent Mode v2 implementation, 45% of EU conversions dropped from reporting. Smart Bidding went into "Limited" status. Action: Enabled Enhanced Conversions for Leads — for users who gave consent, passed hashed email at form submit. For non-consented users, relied on Google's conversion modeling (built into Consent Mode v2). Result: Total attributed conversions (real + modelled) recovered to 92% of pre-Consent Mode levels. CPL in reporting stabilised at $83 vs the $147 seen during the data gap. Bidding strategy re-exited "Limited" after 3 weeks.

Quick Start Checklist

• [ ] Enable Enhanced Conversions in Google Ads → Goals → Summary → Settings
• [ ] Accept the customer data terms
• [ ] Add user_data object to your conversion event (gtag.js or GTM)
• [ ] Normalise data before passing: trim whitespace, lowercase email
• [ ] For GDPR: implement server-side SHA-256 hashing before passing to user_data
• [ ] For EU traffic: ensure Consent Mode v2 is in place — Enhanced Conversions models data for non-consented users
• [ ] Verify via Tag Assistant: user_data object contains email or phone
• [ ] Check Diagnostics after 72h: "Enhanced conversions data quality: Good"
• [ ] For leads: enable Enhanced Conversions for Leads on offline conversion actions

Need accounts with enough conversion history to test Smart Bidding performance? Browse verified Google Ads accounts — accounts with pre-existing spend data give Smart Bidding a head start on calibration.

What to Read Next

• Google Ads Offline Conversion Imports: Complete Setup Guide fo...
• Facebook Conversions API (CAPI): Setup & Benefits 2026
• Google Ads Glossary: 100+ Essential Terms Every Affiliate Mark...