Enhanced Conversions for Leads: The Email Address Does All the Work
Your contact form already captures everything Google needs to match a signed project back to the ad click that generated the lead. The email address is the only identifier Enhanced Conversions for Leads requires. No GCLID hidden fields. No CRM integration. No new data to collect. The form you already have is sufficient.
Most content about Google Ads offline tracking still leads with the GCLID method—the older approach that requires capturing a URL parameter, storing it through your sales cycle, and uploading it alongside each conversion. Enhanced Conversions for Leads is simpler, more reliable for long sales cycles, and recommended by Google over the traditional method. Here is how it works and how to set it up.
What Enhanced Conversions for Leads Actually Does
When someone clicks your Google Ad, Google knows who they are. It has their email address associated with their Google account—the one they use for Gmail, Maps, Search. When that person fills out your contact form, they give you their email address too. Those two email addresses are the same person. Enhanced Conversions for Leads uses that match.
The process works like this:
- A lead clicks your Google Ad and submits your contact form, providing their email address
- You capture the email server-side at form submission
- The project closes weeks or months later
- You upload the lead’s email (hashed with SHA-256) alongside the conversion details to Google Ads
- Google matches the hashed email against its identity graph and credits the original click
The match happens even if the lead used a different browser to fill out your form, or visited your site multiple times before submitting, or if weeks passed between their first click and their eventual conversion. Email identity is persistent in a way that GCLID—tied to a single browser session—never is.
According to Measure School’s documentation, Enhanced Conversions for Leads produces higher match rates and more stable CPAs than the GCLID-only method. For service businesses with sales cycles measured in weeks, not hours, that difference is significant.
You may be interested in: Google Ads for Quote-Based Service Businesses: The Complete Blueprint
Why GCLID Breaks for Long Sales Cycles
The traditional offline conversion method requires capturing the GCLID—a URL parameter Google appends to your landing page URL when someone clicks your ad—and storing it through the entire sales cycle until the job closes.
Two problems compound for service businesses.
First: Safari’s Intelligent Tracking Prevention limits first-party cookies to 7 days (WebKit, 2024). If your typical quote-to-sign cycle runs three to six weeks, the GCLID stored in the browser cookie has expired long before the client signs. The conversion can never be matched back to the click.
Second: Ad blockers affect 31.5% of global users (Statista, 2024). For a meaningful share of your traffic, the GCLID capture script never runs at all. Those leads arrive with no GCLID attached, and any conversion they produce is permanently unattributed.
Enhanced Conversions for Leads bypasses both problems entirely. Email is captured at form submission—server-side, before any browser can interfere—and stored permanently. It doesn’t expire. It doesn’t get blocked. A lead who clicks your ad in January and signs in March can still be matched.
The Four Fields You Need
The Enhanced Conversions for Leads upload is deliberately minimal. When a job closes, you upload four things:
- Hashed email address: SHA-256 hash of the lead’s email, normalised to lowercase with no spaces
- Conversion action name: The name of the conversion action you created in Google Ads (e.g., “Signed Project”)
- Conversion time: ISO 8601 timestamp of when the conversion occurred
- Conversion value: Optional but strongly recommended—the actual job value in your account currency
That is the complete upload. No GCLID column. No campaign ID. No keyword data. Google resolves all of that from the email match on its end.
The hashing requirement is specific: SHA-256, applied after lowercasing the email and stripping leading and trailing whitespace. must be normalised to before hashing, or the match will fail. This normalisation step is where manual implementations most commonly break.
Setting It Up in Google Ads
The configuration lives in Google Ads under Tools → Conversions → Enhanced Conversions for Leads. Enabling it requires agreeing to Google’s customer data terms and confirming your website collects lead data. From that point, the setting applies to any conversion action you configure to accept enhanced data.
The upload itself can run three ways: manual CSV upload, Google Ads API, or Google Ads Data Manager via BigQuery. For any business processing more than a handful of conversions per month, manual CSV upload is the wrong choice—it requires someone to remember, export, and upload on a regular schedule. The failure rate on manual processes is high enough that most accounts running manual uploads have significant conversion gaps they’re unaware of.
BigQuery Data Manager is the automated path. When closed-job events land in your BigQuery conversion table with hashed email included, Data Manager pulls them to Google Ads on a scheduled run. No human step. No forgotten uploads. No conversion gaps from a missed week.
You may be interested in: BigQuery as a CRM: How Service Businesses Can Use Tracking Data as a Lead Database
Why the Data Is Already Ready
The friction point most businesses expect—hashing the email correctly, normalising it, getting it into a format Google accepts—is handled before the data ever reaches your upload.
Transmute Engine™ is a first-party Node.js server running on your subdomain (e.g., data.yourservice.com). When the inPIPE WordPress plugin captures a contact form submission and routes it via API to your Transmute Engine server, the email address is normalised and SHA-256 hashed automatically—per Google’s exact specification—before being stored in BigQuery. The hashed email sits in your conversion table from the moment of form submission, ready for upload the day the job closes. There is no post-processing step, no manual normalisation, no risk of hash format errors causing match failures. The data Google needs is already in the format Google requires.
Key Takeaways
- Email replaces GCLID as the matching identifier: Every contact form already captures it. No new data collection, no hidden fields, no CRM changes required.
- Long sales cycles are not a problem: Email identity is persistent—a lead who clicks in January and signs in March can still be matched. GCLID expires in 7 days under Safari ITP.
- Four fields complete the upload: Hashed email, conversion action name, conversion time, and conversion value. That is the entire payload.
- Normalisation must be exact: SHA-256 of the lowercased, trimmed email. Transmute Engine applies this at capture automatically.
- Automate via BigQuery Data Manager: Manual uploads fail silently. Scheduled BigQuery imports close the loop without human intervention.
Enhanced Conversions for Leads is Google’s method for matching offline conversions—signed contracts, closed jobs, phone sales—back to the original Google Ads click using a hashed email address. When a lead converts offline, you upload their SHA-256 hashed email alongside the conversion details. Google matches the hash against its identity graph and credits the original click. No GCLID required, no CRM changes, no hidden form fields.
Both work, but Enhanced Conversions for Leads has two structural advantages for service businesses. Email is captured reliably on every submission—GCLID can be lost to Safari ITP or ad blockers before the lead converts. Google also reports higher match rates with email because it can match across sessions and devices where GCLID would break. For long sales cycles, Enhanced Conversions for Leads is the more reliable path.
No. You only need the lead’s email address and the conversion timestamp—both captured at form submission. When the job closes, you upload the hashed email, conversion action name, conversion time, and optionally the job value. Your CRM doesn’t need to change at all.
SHA-256 is a one-way cryptographic hash—the original email cannot be recovered from the hash. Google specifies normalisation before hashing: lowercase, no leading or trailing spaces. Transmute Engine applies this normalisation and hashing automatically at event capture, so the email stored in your BigQuery table is already in the correct format for Enhanced Conversions upload.
Yes, and Google recommends it. When both are available, Google uses GCLID as the primary match and email as a fallback. For any conversion where the GCLID is missing—expired under Safari ITP or blocked by an ad blocker—the email match takes over. Running both gives you the highest possible match rate across all conversion scenarios.
The email address on your contact form has always been the key to closing the attribution loop. Enhanced Conversions for Leads just makes Google acknowledge it. seresa.io