Enhanced Conversions for Leads: The Complete Setup Guide

Quick Answer

Enhanced Conversions for Leads is a Google Ads feature that uses hashed first-party data (email or phone number, encrypted with SHA-256) to match offline conversions back to ad clicks when GCLID isn't available. Enable it in Google Ads under Goals > Conversions > Settings, then include hashed contact data in your conversion uploads alongside GCLID.

Enhanced Conversions for Leads closes the attribution gap GCLID alone can't cover. When a lead's Google Click ID is missing — stripped by a browser, blocked by iOS, or lost across devices — hashed first-party data gives Google a second way to match the conversion back to the original ad click.

If you're running offline conversion tracking and only using GCLID, you're leaving a significant portion of your conversions unattributed. This guide covers exactly how Enhanced Conversions for Leads works, how to enable it, and how to include it in your upload pipeline.

What Is Enhanced Conversions for Leads and How Does It Work?

Enhanced Conversions for Leads uses contact information collected during a form submission — typically email address or phone number — to match an offline conversion back to a Google Ads click.

The process works like this: when someone submits a form on your site, you capture their email or phone alongside any other attribution data. Before that contact data ever leaves your systems, you hash it using SHA-256 — a one-way encryption algorithm. The hashed value gets included in your offline conversion upload. Google then attempts to match that hash against its own hashed records for signed-in Google users, attributing the conversion to the correct campaign and ad click.

No raw personal data is sent to Google at any point. The hashing happens on your end before transmission.

Why Does Enhanced Conversions Matter If You Already Have GCLID?

GCLID match rates are declining. Three things are eating into them:

iOS privacy restrictions strip URL parameters including GCLID in certain contexts, particularly in-app browsers and some Safari configurations. A user who sees your ad in an iOS app and taps through to your site may arrive without a GCLID attached.

Cross-device journeys are common in B2B. A prospect sees your ad on their work laptop, doesn't click, then later searches on their phone and submits your form. No GCLID is present at form submission because the ad click happened on a different device.

Browser tracking prevention continues to expand. Firefox and Safari both apply varying degrees of parameter stripping depending on the referrer context.

Enhanced Conversions for Leads recovers these lost attributions. In practice, accounts running both GCLID and Enhanced Conversions typically see match rates 15 to 30 percent higher than GCLID alone.

What Do You Need to Enable Enhanced Conversions for Leads?

You need four things in place before you start:

First, a Google Ads account with at least one offline conversion action configured using Import as the source. You cannot enable Enhanced Conversions on tag-based or phone call conversions — only import-type conversions.

Second, you need to accept Google's customer data terms. This is a one-time step done during setup in the Google Ads UI.

Third, your forms must be collecting contact information — email address, phone number, or both. If your forms only collect name and company, you have nothing to hash and upload.

Fourth, your conversion upload pipeline needs to be updated to include the hashed values alongside GCLIDs.

How Do You Enable Enhanced Conversions for Leads in Google Ads?

The setup in Google Ads is straightforward. Go to Goals, then Conversions, then Settings. You'll see an Enhanced Conversions section. Toggle on Enhanced Conversions for Leads and follow the prompts to accept the customer data terms.

Once enabled, the setting applies to all import-type conversion actions in the account. You do not need to enable it per conversion action individually.

This step alone does nothing until you update your uploads to include hashed data.

How Do You Hash Contact Data Correctly for Enhanced Conversions?

Hashing errors are the most common reason Enhanced Conversions uploads fail silently. Google is strict about the format it expects.

For email addresses: lowercase the entire string first, then remove all leading and trailing whitespace, then apply SHA-256. The resulting 64-character hex string is your upload value.

For phone numbers: normalize to E.164 format first (plus sign, country code, number with no spaces or dashes — for example +14155552671), then apply SHA-256.

In JavaScript:

``` async function hashValue(value) { const normalized = value.toLowerCase().trim(); const encoded = new TextEncoder().encode(normalized); const hashBuffer = await crypto.subtle.digest('SHA-256', encoded); const hashArray = Array.from(new Uint8Array(hashBuffer)); return hashArray.map(b => b.toString(16).padStart(2, '0')).join(''); } ```

Do not hash the raw uncleaned value. A trailing space or uppercase character will produce a completely different hash and the match will fail.

What Should Your Conversion Upload Include?

A complete Enhanced Conversions upload includes the following fields alongside your standard GCLID conversion data:

The hashed email address (SHA-256 hex string). The hashed phone number if available (SHA-256 of E.164-formatted number). These fields are typically named hashed_email and hashed_phone_number in the Google Ads API.

You can include both. You can include just email. Phone alone tends to have lower match rates since phone numbers change more frequently than email addresses in Google's signed-in user records.

GCLID should still be included whenever it's available. Enhanced Conversions supplements GCLID — it doesn't replace it. Google will use whichever matching method produces the best result for each conversion record.

How Do You Validate That Enhanced Conversions Is Working?

After updating your pipeline, upload a test conversion and check the diagnostics in Google Ads under Conversions > Uploads. Look for three things.

First, your upload should show a Successful status with no errors. If you see "Hashed data format error," your normalization step is incorrect — recheck the lowercase, whitespace, and E.164 formatting.

Second, check the enhanced conversion match rate in the upload diagnostics. A match rate above 40 percent is solid for most accounts. Below 20 percent typically indicates a data quality issue — your hashed values aren't matching Google's records, often because you're hashing work emails that aren't associated with Google accounts.

Third, allow 72 hours after the first successful upload before drawing conclusions about match rates. Google processes these in batches.

What Is the Easiest Way to Implement Enhanced Conversions Without Custom Code?

Building the hashing logic, the upload pipeline, and the diagnostics layer from scratch takes significant developer time. FormTrackr handles all of it automatically.

The tracking snippet captures email and phone at form submission. Before any data leaves your system, FormTrackr hashes it using SHA-256 with correct normalization. When you mark a lead as MQL or Won in the dashboard, the conversion upload includes both the GCLID (if captured) and the hashed contact data. Upload logs show match status and any errors for every conversion attempt.

The result is full Enhanced Conversions coverage with no custom backend work and no CSV management.

Frequently Asked Questions