Enhanced conversions
Enhanced conversions is a Google Ads feature that supplements cookie-based conversion measurement by sending hashed first-party customer data — such as an email address the user provided — to match conversions that cookies alone would miss. The data is hashed (SHA-256) before transmission. It is one industry response to the decline of third-party identifiers, with its own consent and configuration requirements.
What this means
Enhanced conversions improve matching by attaching hashed first-party data to a conversion event. When a user completes a conversion and has provided data such as an email, name, or phone, the tag hashes that data (SHA-256) and sends it so the platform can match the conversion to an ad interaction even when the cookie-based path is incomplete.
This recovers attribution that purely cookie-based measurement loses to identifier restrictions, while keeping the transmitted values hashed rather than plaintext.
Requirements and limits
Enhanced conversions depend on the user actually providing first-party data and on you having the appropriate legal basis and disclosures to use it for this purpose. They do not conjure conversions out of nothing — they improve matching of conversions that occurred, for users whose data you legitimately hold.
They are also platform-specific implementations: the hashing, the supported fields, and the consent handling are defined by the platform's documentation, which is the authoritative reference for any deployment.
- Hashed first-party data (e.g. SHA-256 email) improves matching
- Requires user-provided data and proper consent/disclosure
- Recovers measurement, does not invent conversions
How it appears in analytics and logs
Recovered conversions that cookies could not match indicate enhanced-conversions matching is active; the lift comes from hashed first-party data, not from new tracking of unconsented users.
Diagnostic use case
Understand enhanced conversions when reconciling why a platform reports conversions cookies alone would not capture, and what first-party data it relies on.
What WebmasterID can help detect
WebmasterID is a first-party, observed-event tool and does not transmit hashed PII to ad platforms; it can serve as an independent baseline when you assess enhanced-conversions uplift claims.
Common mistakes
- Deploying enhanced conversions without a lawful basis for the data.
- Assuming it tracks users who never provided first-party data.
- Treating recovered conversions as brand-new demand.
Privacy and accuracy notes
Enhanced conversions hash identifiers (e.g. SHA-256 of email) before sending, and require appropriate consent and disclosure. This is educational, not legal advice — confirm your obligations with qualified counsel.
Related pages
- Modeled conversions
Modeled conversions are conversions a platform estimates statistically rather than observes directly. When direct measurement is blocked — by missing consent, cross-device journeys, or privacy protections — ad and analytics platforms model the likely conversions from observable trends and aggregated data, and report them alongside observed ones. Understanding which conversions are modeled is essential to reading attribution honestly.
- Offline conversion import
Offline conversion import (OCI) connects events that happen away from the website — a sales call that closes, an in-store purchase, a qualified lead in a CRM — back to the online ad click that began the journey. It works by capturing a click identifier (such as Google's GCLID) at the start and later uploading the offline outcome keyed to that identifier, closing the online-to-offline attribution loop.
- Consent and attribution
Consent is upstream of attribution: under frameworks like the EU's GDPR and ePrivacy Directive, storing or reading identifiers for tracking generally requires the user's consent. When consent is declined or withheld, the touchpoints those identifiers would have recorded never enter the data, so attribution operates on partial paths. Understanding consent is therefore inseparable from reading attribution honestly.
- Privacy-first analytics
First-party, observed measurement without PII transmission.
Sources and verification notes
- Google Ads Help — About enhanced conversionsDocuments hashed first-party data matching (SHA-256) and requirements.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.