Definition
Enhanced Conversions are a Google Ads feature that improves conversion measurement by sending hashed first-party data (email, phone, name, address) alongside conversion events. Google matches the hashed data against signed-in Google users to recover conversions that would otherwise be lost to cookie restrictions, ad blockers, or cross-device behavior.
The Two Types of Enhanced Conversions: Web vs Leads
There are two versions of Enhanced Conversions. Both are responsible for handling different tasks. Most guides blur them together, which is why implementation goes wrong.
Enhanced Conversions for Web
- Sends hashed first-party data when a conversion happens on your website (form fill, trial signup, demo booked).
- Google matches the data against user accounts and recovers conversions that would have been lost to cookie restrictions or attribution decay.
This is the version most e-commerce and consumer SaaS accounts use.
Enhanced Conversions for Leads
Sends hashed first-party data the moment a lead is captured. This data is later used to attribute events like SQLs, opportunities, and closed-won deals.
This is the version B2B SaaS accounts actually need. It's the prerequisite for tracking conversions through long sales cycles without depending on GCLID plumbing alone.
The distinction matters because they solve different problems.
Enhanced Conversions for Web recovers lost same-session conversions. Enhanced Conversions for Leads enables cross-session attribution across the full B2B funnel.
SHA-256 Hashing and the Privacy Model
Enhanced Conversions never send raw personal data to Google. All first-party data is hashed using SHA-256 encryption before it leaves your website or CRM.
SHA-256 is a one-way cryptographic hash. This means it turns information, such as an email address, into a fixed string of characters that cannot practically be converted back into its original form.
Google matches hashed values against its own hashed user data. If the hashes match, the conversion gets attributed. If they don't, nothing is shared.
This is how Enhanced Conversions follow privacy regulations like GDPR and CCPA. You control the data. Google receives only the hashed information. Users are matched anonymously through cryptographic comparison, not through exposed personal information.
The Three Implementation Paths
There are three ways to implement Enhanced Conversions. Each has different technical requirements and different levels of control.
[table]
Path | How It Works | Best For
Google Tag Manager | Configure hashing and firing rules inside GTM | Most B2B SaaS accounts. Balance of control and simplicity
Google Tag (gtag.js) | Direct site-level implementation | Custom sites or accounts already using gtag.js
Google Ads API | Server-side implementation with full data control | Enterprise accounts needing strict data governance
[/table]
Google Tag Manager is the default recommendation for B2B SaaS. It gives you enough control to configure Enhanced Conversions properly without requiring engineering resources for every change.
The Google Ads API path is the most powerful and the most technically demanding. It's the right choice when you need server-side control or when you're already sending offline events through the API for other reasons.
Why This Is Step One of the Measurement Stack
Enhanced Conversions for Leads is the prerequisite for offline conversion attribution without complex GCLID plumbing. Here's why.
Before Enhanced Conversions for Leads, offline conversion imports required capturing GCLID at the form, storing it in the CRM, and later passing it back to Google once the conversion happens.
If any step of the GCLID capture breaks, the attribution breaks. And guess what? GCLID capture fails often. Cookies get cleared. Users switch devices. Forms don't capture the parameter correctly. Hence, be mindful that these steps are fragile.
Enhanced Conversions for Leads solves this by using hashed first-party data as the matching key instead of GCLID. When a lead converts to an SQL 30 days later, the CRM sends the hashed email back to Google. Google matches it against the original click. Attribution happens even if GCLID was never captured.
For B2B SaaS accounts building a real measurement stack, this is where you start.
Enhanced Conversions for Leads first. Offline conversion import second. Together they form the measurement layer that Smart Bidding needs to optimize toward real revenue.
For the full implementation guide covering Enhanced Conversions inside the broader tracking setup, our piece on offline conversion tracking for Google Ads walks through the technical steps.
And the guide on Google Ads attribution for B2B SaaS explains how attribution changes once you factor in Enhanced Conversions.
The Rule for B2B SaaS
- Enable Enhanced Conversions for Leads on day one.
- Use Google Tag Manager unless you have a specific reason to use the API.
- Configure the hashing correctly.
- Test the implementation before assuming it works.
This is step one of a working measurement stack, and every attribution decision depends on it being set up properly.
Book a Free Google Ads Audit