PPC & Conversion Tracking
Enhanced Conversions for Leads: The Complete Technical Setup Blueprint
, 3 minute read
Enhanced Conversions for Leads is set up in four parts: turn the feature on in Google Ads and accept the customer data terms, capture and hash the lead's email or phone on the form, store that value and the click ID in the CRM, then upload closed leads with the same hashed identifier, conversion time and value.
What the feature actually does
A standard offline conversion import depends on one thing: the Google click ID surviving from the ad click to the closed sale. In practice it gets lost. The visitor switches devices, calls instead of filling in the form, or the CRM field was never mapped.
Enhanced Conversions for Leads gives Google a second way to make the match. You send a hashed copy of the email address or phone number the lead gave you. Google hashes the same details for its signed-in users and compares the two. No readable personal data is exchanged, and the match works even when the click ID is gone.
It supplements the click ID. Send both whenever you have both.
Step 1: Account settings
In Google Ads, open the conversion settings, turn on enhanced conversions for leads and accept the customer data terms. Choose how the website will supply the data: the Google tag, Google Tag Manager or the API.
Create a conversion action for each outcome you intend to upload, for example Qualified Call and Closed Sale, and set the one that means revenue as primary.
Step 2: Normalize, then hash
Hashing is unforgiving. An address typed with capitals and a trailing space produces a different hash from the same address in lowercase, unless you normalize first. Google's rules:
- Email: trim whitespace and lowercase. For gmail.com and googlemail.com addresses, remove the dots before the @.
- Phone: convert to E.164, the international format with a plus sign and country code, such as +17472499821.
- Both: hash with SHA-256 and send the lowercase hexadecimal string.
In any server environment that supports the Web Crypto API it is a few lines:
async function sha256Hex(value) {
const bytes = new TextEncoder().encode(value);
const digest = await crypto.subtle.digest("SHA-256", bytes);
return Array.from(new Uint8Array(digest), (b) => b.toString(16).padStart(2, "0")).join("");
}
The audit form on this site does exactly this on the server before the lead is stored.
Step 3: What the CRM must hold
Every lead record needs five fields beyond the usual contact details:
- The click ID:
gclid, orgbraidorwbraidfor some iOS traffic - The normalized email and phone, or their hashes
- The time the lead was created
- A stage that someone keeps current
- A value, once known
Phone leads need the same fields. That means the call-tracking platform has to pass the click ID and the caller's number into the CRM, which is the subject of the GCLID-to-CRM loop.
Step 4: The upload
When a lead reaches the stage you are tracking, send it to Google Ads. Through the API, one conversion looks like this:
{
"conversion_action": "customers/1234567890/conversionActions/987654321",
"gclid": "Cj0KCQiA...",
"conversion_date_time": "2026-11-21 10:15:00-08:00",
"conversion_value": 8400.0,
"currency_code": "USD",
"user_identifiers": [
{ "hashed_email": "a3f1c2...e9" },
{ "hashed_phone_number": "7c2b90...04" }
]
}
Upload at least daily. Include the timezone offset in the timestamp. Deduplicate, so a record that changes twice is not sent twice. And stay inside the window: Google rejects conversions uploaded more than 90 days after the click.
Step 5: Verify
A setup that runs without errors can still match almost nothing. Check three things in the first two weeks:
- The diagnostics for each conversion action in Google Ads, which report on recent uploads and flag formatting problems
- That uploaded conversions appear against campaigns within hours, not days
- That the count in Google Ads is plausibly close to the count in the CRM for the same period
Low match rates almost always trace back to normalization: spaces, uppercase letters, phone numbers without a country code.
Privacy and consent
You must have the right to share the data. That means a privacy policy that says so and, where the law requires it, consent before collection. Regulated fields carry additional duties. Healthcare practices in particular should read our notes on HIPAA-conscious tracking before sending anything.
Let it steer
Once the loop runs, the last step is to let it drive the account. Make the closed-sale action primary, attach real values, and move the bid strategy to one that uses them. Why that matters is the subject of our piece on Smart Bidding without offline conversions, and the full service is described under offline conversion tracking. To see where calls enter this picture, read call tracking attribution done right.
Questions this article raises
Do I still need the GCLID if I use enhanced conversions?
Yes, capture both. The click ID is the most precise match. Hashed identifiers recover the conversions where it was lost.
Can I hash data in the browser?
The Google tag can hash in the browser for the on-site capture step. For uploads from your CRM, hash on the server, where you control normalization and can test it.
What is the difference between enhanced conversions for web and for leads?
The web version improves measurement of conversions that happen on your site, such as purchases. The leads version is for sales that close offline after a form or a call.
Talk to the person who will actually do the work
No account coordinator, no discovery deck. Call and describe what the phone should be ringing for, or send the site and we'll trace where the signal is leaking.