Skip to content
whitead

Enhanced Conversions for Leads

glossary google ads updated 2026.05.06 6 min read
// contents · 8 sections
  1. What Enhanced Conversions for Leads is
  2. How EC for Leads works
  3. What changed in 2025-26
  4. Common misconceptions
  5. Does EC for Leads replace the GCLID in my CRM?
  6. Is EC for Leads a privacy risk under GDPR?
  7. Related concepts
  8. Sources

Enhanced Conversions for Leads (EC for Leads) is a distinct conversion-measurement tier built specifically for lead-gen accounts that close offline. It hashes form-submit PII, ships it to Google, and lets offline conversions stitch back to the original ad click long after cookies and ATT signals have decayed.

What Enhanced Conversions for Leads is

EC for Leads is the lead-flow variant of Enhanced Conversions. Where EC for Web supplements an on-page purchase or signup with hashed first-party data, EC for Leads is designed for journeys where the conversion that matters — qualified lead, opportunity, closed-won — happens days or weeks after the form submit, often inside a CRM. Google describes it as a way to "measure conversions that happen offline, like sales in a CRM, and tie them back to your Google Ads campaigns" using hashed customer data instead of GCLID-only matching (Google Ads Help, 2025-11-12). The hashed identifier (typically email or phone) is captured at form submit, sent through the conversion tag, and matched server-side to a logged-in Google account. When you later upload the offline outcome via Data Manager, Google joins it to the original click without needing a surviving cookie or GCLID.

How EC for Leads works

The pipeline has three handoffs that all need to fire correctly. First, the lead-form page captures user-provided data — email, phone, first/last name, address — and either hashes it client-side via the Google tag (enhanced_conversions: true) or sends it raw to a same-origin endpoint that hashes it before the request leaves your domain. Google requires SHA-256 with normalised inputs: lowercase, trimmed, country-coded phone in E.164 (Google Ads Help: format guidelines, 2026-01-08). Second, you create a conversion action of category Lead and link it to the lead source — typically the form. Third, when the lead converts inside your CRM, you push the qualifying event back to Google with the same hashed identifier and a conversion value, either through the Google Ads API, the Data Manager UI, or a partner connector (HubSpot, Salesforce, Zapier). Match rates depend on how many of your leads use a Google-account-linked email; B2B accounts where leads submit a personal Gmail typically see materially higher match than enterprise-only emails.

What changed in 2025-26

Three shifts re-prioritised EC for Leads in the past 18 months. Consent Mode v2 became enforceable across the EEA in March 2024, so any non-consenting visitor's cookie-based GCLID never reaches Google — modelled conversions partially fill the gap, but EC for Leads provides a deterministic recovery path when the user later consents at form submit (Google Ads Help: Consent Mode v2, 2025-09-22). Data Manager replaced the legacy "Conversions > Uploads" UI in 2024-2025, consolidating offline conversion import, customer match, and EC ingestion into a single surface (Google Ads Help: About Data Manager, 2025-10-14). And Google's 2025 measurement guidance positions EC for Leads + GCLID-in-CRM as the recommended baseline before any account is allowed to drive Smart Bidding to value-based goals (Google Ads & Commerce blog, 2025-04-22).

Methodology note. Whitead's audit checks for EC for Leads readiness by inspecting four signals: (1) presence of a Lead-category conversion action with EC enabled, (2) hashed-data fields visible in the Google tag's network payload at form submit, (3) at least one offline upload in the trailing 30 days via Data Manager or the Google Ads API, and (4) GCLID/GBRAID/WBRAID columns populated in the CRM lead record. We classify accounts where (1) is present but (2)-(4) are missing as "EC stub only" — the toggle is on but no data is flowing — which is the most common pattern in lead-gen audits. The fix-priority logic ranks "EC stub only" higher than "EC absent" because the misconfiguration silently falsifies the conversion picture Smart Bidding optimises against.

Common misconceptions

EC for Leads is sometimes treated as interchangeable with EC for Web or with Customer Match. They share the hashed-data primitive but solve different problems, and the Data Manager UI presents them side-by-side which adds to the confusion.

Does EC for Leads replace the GCLID in my CRM?

No. EC for Leads supplements GCLID — it does not substitute for capturing it. The GCLID (or GBRAID/WBRAID for iOS app journeys) remains the strongest match key for offline conversion import, and Google's own setup checklist still lists CRM-side click-id capture as step one (Google Ads Help: OCI prerequisites, 2025-12-03). EC for Leads is the recovery layer for clicks where the GCLID was lost — ATT-truncated, cookie-blocked, or simply mis-pasted by the lead.

Is EC for Leads a privacy risk under GDPR?

Hashed PII is still personal data under GDPR, so the legal basis is consent-based, not legitimate-interest by default. Google's data-use terms require advertisers to have a lawful basis to share the underlying data and to honour Consent Mode signals; the hashing happens client- or server-side specifically to keep raw PII off Google's ingest path (Google EU user consent policy, 2025-08-19). Practical implementation: consent banner gating on the form-submit tag, plus a documented retention policy for the hashes inside your tag manager.

EC for Leads sits at the intersection of measurement, bidding, and consent. See Enhanced Conversions for the on-page (web) variant, Conversion Tracking for the foundation it builds on, Consent Mode v2 for the EEA-specific consent layer, GCLID/GBRAID/WBRAID for the click-identifier flow it complements, and the finding Fix: Enhanced Conversions Not Enabled for the audit rule Whitead fires when EC is missing.

Sources

← Back to Wiki