How to Set Up Google Ads Enhanced Conversions: Step-by-Step Guide

Turning on Enhanced Conversions in Google Ads is only the beginning. The toggle itself is quick check a box, accept a compliance agreement, done. But that setting alone doesn't mean your first-party customer data is actually being captured and sent correctly. A successful implementation has three parts: turn it on, configure how data gets captured, and validate it's genuinely working — not just technically enabled.

This guide walks through all three, plus how to check Google's own diagnostics report rather than assuming a green status means success.

Worth knowing before you start: as of the 2026 update, Enhanced Conversions for web and Enhanced Conversions for leads are now handled through a unified setting rather than two separate feature switches. The steps below reflect that current structure, though the underlying implementation can still differ depending on how your conversions and customer data are actually collected.

If you haven't yet, it's worth reading our complete guide to Enhanced Conversions first for the concepts this guide assumes you already understand.

What You Need Before You Start

An existing Google Ads conversion action you want to enhance. Enhanced Conversions supplements a conversion you're already tracking, not a new tracking implementation from scratch.
A way to capture first-party customer data at the conversion point — typically the email address or phone number a customer provides during checkout or a form submission.
Google Tag Manager, the Google tag, or Google Ads API access, depending on which implementation method fits your setup. Google offers all three; which one applies depends on how your site is currently tagged.
Authority to accept Google's Customer Data Terms. Turning on Enhanced Conversions requires agreeing to these terms, which confirm your use of the feature complies with Google's data processing policies. If you manage multiple accounts under an MCC, this typically needs to be accepted per individual account, not once at the manager level.

Account-Level vs. Conversion-Level Setup

Google offers two ways to turn on Enhanced Conversions, and picking the right one matters for how much ongoing configuration you'll deal with. This is a separate choice from the 2026 web/leads unification — that change merged what used to be two different products; account-level vs. conversion-level is about scope (your whole account at once, or individual conversion actions), and that distinction still exists under the unified setup.

Account-level setup turns Enhanced Conversions on for your entire account in one pass, reducing the number of steps needed compared to configuring it action by action. This is generally the simpler route if you want Enhanced Conversions applied broadly rather than selectively.

Conversion-action-level setup lets you turn Enhanced Conversions on for individual conversion actions specifically, useful if you only want it applied to certain conversions rather than everything in the account. Existing accounts may still have conversion-level configurations from before the 2026 update — worth reviewing those rather than assuming a new account-level setting automatically overrides or resolves them.

Most businesses setting this up for the first time should start with account-level setup unless there's a specific reason to exclude particular conversion actions.

Step-by-Step: Turning On Enhanced Conversions

Account-level activation:

Go to Settings within the Goals menu in Google Ads.
Expand the panel for this setting — depending on your account's rollout stage, Google's own documentation refers to this as either the Customer data use panel or the Enhanced conversions panel, so look for whichever appears.
Check Turn on enhanced conversions.
Optionally check Turn on conversion-based customer lists if you want Google to use your conversion data to build customer lists for your account.
Select Agree and save.
Review the data terms shown, then select Agree and continue.
Follow the setup instructions for the data source you plan to use, such as your Google tag, Google Tag Manager, Data Manager, or an API connection — the unified setting accepts data from whichever of these you have in place, rather than requiring you to commit to a single method.

Conversion-action-level activation (if you're configuring a specific action rather than the whole account):

Go to Summary within the Goals menu.
Select + Create conversion action, or open an existing action you want to configure.
In the data sources panel, locate the Enhanced conversions section for that action.
Toggle it on.
Review and accept the data terms if prompted — this can require re-accepting even if you've already agreed at the account level.

Either way, turning on the setting itself is the easy part. It doesn't yet mean customer data is actually being captured and hashed anywhere — that's the next step.

Step-by-Step: Setting Up Data Capture with Google Tag Manager

Turning on the setting in Google Ads tells Google you're ready to receive enhanced data. Your website still needs to actually capture and hash that data before sending it. If you're using Google Tag Manager, here's the general path:
Open Google Tag Manager and go to your workspace.
Create a new tag. Select Tag Configuration, then choose Google Ads, then Google Ads User-Provided Data Event.
Fill in your Google Ads Conversion Tracking ID. This needs to match the conversion action you enabled Enhanced Conversions for in Google Ads — a mismatch here is one of the most common reasons setup silently fails.
Choose your data collection method. Google Tag Manager offers a few approaches: automatically detecting user-provided data on the page, specifying exact CSS selectors or JavaScript to pull the data from, or adding a code snippet directly. Automatic detection is the fastest to set up but works best when customer data fields (email, phone) are clearly labeled and present on the conversion page itself.
Set up your trigger. This determines when the tag fires — typically after a form submission or on the conversion confirmation page, depending on your setup.
Publish your container once configured. Nothing captures live data until the container is published.
Google handles the actual SHA-256 hashing of the customer data as part of this process — you're not writing your own hashing code, just configuring what data gets captured and when the tag fires.
If you're using the Google tag directly rather than Tag Manager, the process is conceptually similar: enable Enhanced Conversions in your account settings, then add a code snippet to your website that identifies which customer data fields to capture (email, name, address, and similar), formatted correctly (lowercase, whitespace trimmed) before Google's systems hash it.

Validating Your Setup

This is the step most setups skip, and it's the reason "I turned it on" and "it's actually working" often aren't the same claim. Google gives you two ways to check — one immediate, one more complete.

The fast technical check — right after setup:

Right-click on your website's conversion page and select Inspect.
Go to the Network tab.
Enter "google" in the search bar to filter network requests.
Find the request going to googleadservices.com/pagead/conversion/ (or a similar Google Ads conversion endpoint, which can vary slightly by browser).
Click into the Payload tab to see the actual parameters being sent.

If you see hashed customer data parameters (like em for hashed email) populated with a long alphanumeric string, that indicates hashed user-provided data was included in the request — confirming the tag fired and sent something. It's not full end-to-end proof that matching is working well; the Diagnostics report below is the stronger validation for that. If a parameter shows up but empty — for example em with no hash string following it — customer data wasn't available at the moment of conversion, even though the tag is technically firing.

The complete check — Google's own Diagnostics report:

Google Ads has a dedicated Enhanced Conversions diagnostics report that goes further than a single payload check, showing the health of your setup and how effectively you're recovering conversion data overall.

Go to Summary within the Goals menu.
Select the conversion action that has Enhanced Conversions enabled.
Select Diagnostics from the page menu at the top.
Review the health checks shown for that conversion action.

Two things worth knowing about this report: it typically takes 48–72 hours after implementation before it populates with meaningful data, so don't expect it to be useful immediately. And Google's own documentation notes that diagnostics alerts don't display for accounts with fewer than 20 conversions in the past 7 days — the feature is built with higher-volume advertisers in mind, so very low-volume accounts may not see much signal here regardless of setup quality.

Do the Network tab check immediately to confirm the tag is firing correctly. Come back to the Diagnostics report a few days later for the fuller picture.

Common Setup Mistakes

Mismatched conversion tracking IDs between the Google Tag Manager tag and the conversion action enabled in Google Ads — the single most common reason data doesn't flow despite everything appearing configured.
Assuming automatic detection works everywhere. It depends on customer data being clearly present and identifiable on the actual conversion page. If email or phone data lives on a different page than where the conversion tag fires, automatic detection may miss it entirely.
Never checking the Network tab. Skipping validation means the first sign of a problem is degraded ad performance weeks later, not an immediate, checkable confirmation.
Forgetting to publish the Tag Manager container. A correctly configured tag that's never published doesn't do anything live.
Not re-accepting data terms at the conversion-action level when required, leaving a specific action's Enhanced Conversions toggle effectively inactive despite the account-level setting being on.

Best Practices

Validate your setup with the Network tab immediately after configuration, then check Google's own Diagnostics report a few days later once it has data to show.
If your account has fewer than 20 conversions in the past 7 days, don't expect much signal from the Diagnostics report — Google says alerts may not be displayed at that volume.
Send as many customer identifiers as you have available — email, phone, and address. Google's own guidance is that providing more match keys increases the likelihood of a successful match; there's no single identifier that's categorically "best" on its own.
If you're implementing leads specifically, Google's own guidance recommends including both email and phone where possible — Google's documentation specifically notes email as a good identifier for leads because it's "highly unique" and "isn't prone to being reformatted" in a CRM, while phone adds further matching value alongside it.
Match conversion tracking IDs carefully between Google Tag Manager and Google Ads — double-check this specifically if setup doesn't seem to be working.
Choose your data collection method (automatic detection, CSS selectors, code snippet) based on where customer data actually appears in your conversion flow, not by default.
If managing multiple accounts under an MCC, confirm data terms are accepted per account rather than assuming a manager-level acceptance covers everything.
Revisit your setup after any website redesign or form changes — a working implementation can break silently when the underlying page structure changes.

Conclusion

The account-level toggle in Google Ads is straightforward. The part that actually determines whether Enhanced Conversions works is the data-capture configuration underneath it — making sure customer information is actually being identified, hashed, and sent, and then confirming that with an actual check rather than an assumption. The Network tab check gives you an immediate technical read; the Diagnostics report gives you the fuller picture once it has data to show. Together, they're the difference between knowing your setup works and hoping it does.

Frequently Asked Questions

Do I need a developer to set up Enhanced Conversions?

Not necessarily. Google Tag Manager's built-in configuration options (automatic detection, in particular) are designed to be usable without custom code. A developer becomes more relevant if you're implementing via the Google Ads API directly, or need custom JavaScript/CSS selector logic for a non-standard page structure.

How do I know if my setup is actually working?

Two checks. Immediately after setup, check the Network tab on your conversion page - look for a request to Google's conversion endpoint with hashed customer data parameters populated in the payload. A few days later, check Google Ads' own Enhanced Conversions Diagnostics report (Summary - select the conversion action - Diagnostics) for the fuller picture - it takes 48–72 hours to populate. A "Connected" or "enabled" status alone confirms neither.

What's the difference between account-level and conversion-action-level setup?

Account-level turns Enhanced Conversions on broadly, in fewer steps. Conversion-action-level lets you enable it selectively for specific conversions. Most businesses starting fresh should use account-level unless they have a specific reason to exclude certain actions.

Do I need to set this up separately for web and for leads?

As of the 2026 unification, Enhanced Conversions for Web and for Leads share a single account-level toggle rather than being entirely separate products. Implementation can still differ by use case: web conversions typically use customer data captured through website tagging at the point of conversion, while leads workflows can involve that same tagging plus offline conversion data supplied later through Data Manager or API-based connections, matched back against the original lead.

What happens if I don't accept the data terms?

Enhanced Conversions won't activate. Accepting Google's Customer Data Terms is a required step, not optional — it's Google's confirmation that your use of the feature complies with its data processing policies.