Google Enhanced Conversions: Setup Guide for Marketing Teams

Google's enhanced conversions attach hashed first-party data — email, phone, name and address where appropriate — to the conversion measurement you already run. When cookies and identifiers fall short, Google uses the hashed data to match conversions to signed-in users, recovering measurement a tag alone would miss.

The two variants

• Enhanced conversions for web. Your conversion tag sends hashed customer data alongside the conversion. Best when the conversion happens on your site and you have the customer's details at that moment (checkout, signup).
• Enhanced conversions for leads. For lead-gen: you capture contact details with the lead, then report the eventual offline outcome (qualified, closed) with the same hashed details, and Google matches it back to the ad interaction.

Related but distinct: offline conversion imports send conversions that never touched the browser at all. If your pipeline already joins CRM and revenue data, all three paths draw from the same prepared records.

Consent mode

In regions where consent applies, consent mode signals what the user allowed. With consent granted, enhanced conversions improve deterministic matching. Where signals are limited, Google relies on modeling. The practical rule: implement consent handling first, then enhanced conversions on top — sending hashed data without a valid basis is not a shortcut.

Setup options

• Tag-based: enable enhanced conversions in the tag configuration and map the fields where your conversion fires; normalization and hashing are handled by the tag.
• API-based: your backend or pipeline sends the data; you own normalization (trim, lowercase) and SHA-256 hashing, and gain the ability to send backend truth on your schedule.
• Managed pipeline: Vendo's conversion signals prepare identifiers and outcomes from your sources — storefront, payments, CRM — and deliver them in the format each Google surface expects, alongside the other platforms you run.

Common mistakes

• Inconsistent normalization across pages or systems, which silently lowers match rates
• Partial coverage — enhanced data on the purchase but not the signup, or on one domain of several
• Missing consent signals, which limit what Google can use regardless of what you send
• No verification loop — the diagnostics exist; teams often never open them

Measuring the result

Watch the per-action diagnostics, then compare Google-reported conversions against your source of truth over a stable window. As with any recovery work, separate truly recovered signal from reattribution — the signal recovery playbook shows a clean way to do it, and Vendo's signal recovery methodology documents the measurement logic.

For the whole landscape across platforms, start with the server-side tracking and conversion APIs guide; for the Meta side, see the Meta Conversions API guide.