TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › SYMPTOM FILES › SYM-035

SYMPTOM FILE SYM-035 FILED 07 NOV 2026 · REVISED 11 NOV 2026

Enhanced Conversions in GTM: which setup method to use and how to verify it.

ALSO FILED AS
  • “Enhanced Conversions Google Tag Manager setup”
  • “which Enhanced Conversions method to use in GTM”
  • “Enhanced Conversions automatic vs manual vs code”
  • “User-Provided Data variable GTM”
  • “Include user-provided data from your website”
  • “Google Ads User-Provided Data Event tag”
  • “Enhanced Conversions dataLayer GTM”
  • “how to verify Enhanced Conversions in Tag Assistant”

Baris Asa, tracking consultant, London · Last checked: November 2026

On a shop, the method to use is Code: the site hands the customer’s email to Tag Manager with the order, and the Google Ads conversion tag sends it. Setup is three steps. Turn Enhanced Conversions on in Google Ads and accept the customer data terms. Turn on Allow user-provided data capabilities in the Google tag. Attach a User-Provided Data variable to the conversion tag. To check it, read Google Ads Diagnostics after 48 hours, or ask for a test order that shows a hash after tv.1~em..

Enhanced Conversions sends the customer’s email (or phone, or name and address) with the Google Ads conversion, hashed with SHA-256, so Google can match the sale to a signed-in Google account when the click id or cookie is lost. What it is, and the four gates it fails at, are on file as F-402 . If it is set up and Google Ads says it isn’t working, start with Enhanced Conversions not working in Google Ads. Not sure Tag Manager is your route at all? See the Enhanced Conversions overview.

Two people are involved. Whoever owns the Google Ads account flips one switch. Whoever runs your tags does the rest. If neither can show you a test hit with a hash in it, it isn’t done.

“Method” in this note means how the Tag Manager container collects the email. It isn’t the method dropdown some Google Ads accounts still show (that’s covered in the switches below).

Which GTM method fits your site?

MethodWhere the email must beBreaks whenUse it for
AutomaticShown on the page as the tag firesIt isn’t shown, or another email isSimple confirmation pages
CSS selectorsIn a page element you can point atThe theme changesA page automatic misreads
CodeIn the dataLayer or a JS variableThe data arrives after the tag firesShops: the default
User-Provided Data event tagIn a form on an earlier pageThe form never really submitsLead forms, multi-step forms
GOOGLE TAG MANAGER · four ways to collect the email, and where each breaks · method comparison from Google's Tag Manager setup guide

If you only read one row: on a checkout, Code. The order confirmation already knows the customer’s email, and the shop can hand it over in the dataLayer (the order details a site passes to Tag Manager) with the purchase. The page layout can’t break it. Timing can, and that is covered below. Google’s guide also gives code data priority when methods are combined.

Step 1: the two switches

  1. Google Ads (account owner). Goals, Settings, Enhanced conversions: turn it on and accept the customer data terms. Nothing is processed before the terms are accepted. If the account still asks for a method, choose Google Tag Manager.
  2. The Google tag in GTM (whoever runs your tags). Open the Google tag’s settings and turn on Allow user-provided data capabilities.

Neither switch changes the other. Google Ads can say “on” while the container sends nothing.

Step 2: attach the variable to the conversion tag

This is the step most setups skip. A User-Provided Data variable does nothing until a tag sends it.

On the Google Ads Conversion Tracking tag, tick Include user-provided data from your website and select the User-Provided Data variable. The tag then sends it as user_data with that conversion. Google’s guide also shows user_data added as an event parameter on the Google tag, which applies it more widely. A setting on the event overrides the tag-wide one.

For Code, keep it on the conversion tag. A variable on a Google tag that fires at page load is read before the purchase reaches the dataLayer, and goes out empty.

While you are in that tag, check the Conversion ID and Conversion Label are the ones on the action you bid on. Clean data sent to an old label lands on an action nobody reads.

Step 3: choose how the variable collects the email

Automatic: quickest, least control

Set the variable to Automatic collection. Google scans the page for anything that looks like an email, phone or address when the conversion tag fires.

It works on a confirmation page that prints “We’ve sent your receipt to [email protected]”. It fails quietly in two cases: the theme doesn’t print the email, or it prints another one, such as a support address in the footer, which then goes out with every order. Exclude your own contact elements in the Google tag settings (Add exclusions).

CSS selectors: the page shows it, automatic misses it

Set the variable to Manual configuration. For each field, create a DOM Element variable with the CSS Selector method and leave the attribute name blank.

To find a selector: right-click the email on the page, Inspect, right-click the highlighted element, Copy, Copy selector. Prefer an element ID: Google calls IDs the most stable. A long chain like div:nth-child(3) > span is the one that breaks.

The theme release is the one I see most. The order still counts, the email field goes out empty, and nobody notices for weeks.

Code: the one I’d use on a shop

Set the variable to Code and point it at a variable that returns the customer’s details as an object. The values come from the site, not from what is visible on the page.

On the order confirmation, the shop pushes the email with the purchase:

dataLayer.push({ ecommerce: null });
dataLayer.push({
  event: "purchase",
  customer: { email: "[email protected]", phone: "+447700900123" },
  ecommerce: { transaction_id: "100231", value: 84.00, currency: "GBP" }
});

In GTM, create Data Layer Variables for customer.email and customer.phone, then a Custom JavaScript variable that returns the object Google expects:

function () {
  return {
    email: {{DLV - customer.email}},
    phone_number: {{DLV - customer.phone}}
  };
}

Rules for the values. Every value is a string. Remove a field you don’t collect rather than sending it blank. Send the phone in E.164 (+447700900123: plus sign, country code, no spaces), and send it with an email: Google’s Google tag guide won’t accept a phone on its own, and the GTM guide recommends pairing it. An address needs first name, last name, postcode and a two-letter country code, all four.

You don’t hash anything. The Google tag normalises and hashes the plain values before they leave the browser.

Code breaks on timing. If the conversion tag fires on the page view and the push lands a moment later, the email goes out empty and the order still counts. Fire the conversion tag on the custom event (purchase) that carries the email. Why tags fire before their data exists is on file as F-103 , with the fix in GTM tag fires before the dataLayer is ready.

The User-Provided Data event tag: the form is on an earlier page

Some sites collect the email on one page and record the conversion on another: a lead form that redirects to a thank-you page, or a multi-step checkout. Google’s answer is a separate tag.

  1. Create a Google Ads User-Provided Data Event tag and enter the conversion tracking ID. It must match the conversion action’s ID and label.
  2. Give it a User-Provided Data variable (Automatic, Manual configuration or Code).
  3. Trigger it on Form Submission, All Forms. Google says this trigger is required.

The tag keeps the hashed data in an ads cookie for the session, links it to the conversion when that happens, and deletes what never links. With Consent Mode, that cookie follows ad_storage.

It relies on a real form submit, and a form built in JavaScript may never fire one. Check the trigger fires in Preview. If it doesn’t, push the email to the dataLayer when the form is sent and use Code on the thank-you page instead.

Enhanced Conversions only sends the hashed email for visitors whose ad_user_data (the consent signal for sending customer data to Google for advertising) is granted. For a visitor who declines it, no email goes out. That is correct. What happens to the conversion itself is Consent Mode’s decision, not Enhanced Conversions’. The fault is a banner that never updates ad_user_data to granted after an accept: then the customers who said yes lose it too. Fix the wiring and every customer who agreed brings a matchable conversion with them. That wiring is F-201 , and the check is in How to check Consent Mode v2 is actually working.

How do I verify it worked?

If you don’t run the container: open Google Ads, Goals, Summary, Diagnostics, about 48 hours after setup. Excellent or Good on the action you bid on: working. Needs attention or No recent data: send this page to whoever runs your tags. Alerts stay hidden under 20 conversions in seven days, so on a small account ask for the test below instead.

For whoever runs the tags, before publishing and again after:

  1. In GTM, click Preview and connect Tag Assistant to the site. Accept the cookie banner.
  2. Place a test order (or send the form) with an email you will recognise.
  3. In Tag Assistant, open the Google Ads conversion hit and read its em parameter:
    • a long hash after tv.1~em.: sent. Working.
    • tv.1~em. with nothing after it: sent empty. Timing (Code) or a selector (Manual).
    • no em parameter: the variable isn’t attached. Check Allow user-provided data capabilities on the Google tag and the user-provided data option on the conversion tag.
    • a code after it (e0 to e3): Google’s error codes, read in the diagnostics note.
  4. Repeat with the banner declined. An empty or missing value there is expected.

Checking a live site without Preview, from the browser’s network tab, is the test order in the diagnostics note.

What breaks after it works

  • A theme release moves the element a CSS selector pointed at.
  • A new confirmation page stops printing the email that automatic detection read.
  • A container clean-up moves the conversion tag to a page-view trigger, ahead of the push.
  • A new conversion action replaces the old one, and the tag still carries the old label.

Each leaves the order counting and the email empty, and Google Ads shows Missing user-provided data. Keep the test order on the release checklist. When a container has no owner between releases, running that check is part of the GTM consultancy work I do for brands and their agencies.

Common questions

How do I set up Enhanced Conversions in Google Tag Manager, and which method should I use?

Turn it on in Google Ads (Goals, Settings, Enhanced conversions) and accept the customer data terms. In GTM, turn on Allow user-provided data capabilities in the Google tag, then give the Google Ads conversion tag a User-Provided Data variable. On an online shop, set that variable to Code and feed it the email the site pushes to the dataLayer with the purchase: the page layout can’t break it, and Google gives code data priority. Automatic suits a confirmation page that shows the email. CSS selectors suit a page where automatic picks the wrong field. The User-Provided Data event tag suits forms on an earlier page.

How do I check Enhanced Conversions is working in GTM?

Without GTM access: in Google Ads, Goals, Summary, Diagnostics, about 48 hours after setup. Excellent or Good is working. Needs attention or No recent data goes to whoever runs your tags. With GTM: place a test conversion in Preview with the cookie banner accepted and read the em parameter on the Google Ads conversion hit in Tag Assistant. A long hash after tv.1~em. means the email was sent. tv.1~em. with nothing after it means it went out empty. No em at all means the variable isn’t attached to the tag.

Do I still choose Google Tag Manager as the method in Google Ads?

Google changed this in two steps: from April 2026 Google Ads accepts data from tags, Data Manager and the API together, and from June 2026 web and leads are one on/off setting with no method to pick. If your account still shows the method dropdown, choose Google Tag Manager: Google warns that data sent through a different method may not be processed. The methods in this note are something else: how the GTM container collects the email.

Is automatic detection good enough for Enhanced Conversions?

On a simple confirmation page that prints the customer’s email when the conversion tag fires, yes. It reads the page, so it misses an email the page doesn’t show and can pick up the wrong one, such as a support address in the footer. Exclude those elements in the Google tag settings and check a test hit before you trust it.

Do I need to hash the email myself in GTM?

No. Pass the plain values in the User-Provided Data variable and the Google tag normalises and hashes them with SHA-256 before they leave the browser. If you send values you hashed yourself, the normalisation is yours: trim, lowercase, phone in E.164 such as +447700900123.

Who sets up Enhanced Conversions in GTM?

Two people. Whoever owns the Google Ads account turns it on and accepts the customer data terms. Whoever runs your tags builds the variable, the dataLayer push and the consent signal, and should be able to show you a test hit with a hash in it. That second part is the work I do for brands and their agencies, as Synctag: Google Ads conversion tracking.

Sources

Read on 7 November 2026:

  • Google Ads Help, set up enhanced conversions for web using Google Tag Manager (Allow user-provided data capabilities; automatic, CSS selectors or JavaScript variables, code; Add exclusions; DOM Element variables with CSS Selector, element IDs most stable; Custom JavaScript variable returning an object; user_data parameter; event-level settings override tag-wide; code snippet data prioritised; values as strings, unused fields removed; E.164 phone, recommended with an email; address fields; User-Provided Data Event tag with matching ID and label and a required Form Submission trigger; session ads cookie following ad_storage; diagnostics about 48 hours; method dropdown and April 2026 single setting)
  • Google Ads Help, updates to your enhanced conversions settings (read 11 November 2026: April 2026 tags, Data Manager and API accepted together; June 2026 one setting, no method selection)
  • Google Ads Help, set up enhanced conversions for web using the Google tag (Goals, Settings, customer data terms; nothing collected before acceptance; April 2026: tags, Data Manager and API accepted together; data sent by another method may not be processed; phone not accepted alone)
  • Google Ads Help, about the enhanced conversions for web tag diagnostics report (reading em in Tag Assistant: hash, tv.1~em. empty, missing parameter; e0 to e3; statuses; alerts hidden under 20 conversions in 7 days; Missing user-provided data)
  • Google tag platform, Google Ads conversions with server-side Tag Manager (User-Provided Data variable types: Automatic collection, Manual configuration, Code; event parameter name user_data)
  • Google Ads Help, about enhanced conversions (SHA-256 hashing, matching to Google accounts signed in when they engaged with the ad)
  • Google tag platform, consent mode overview (ad_user_data denied disables hashed first-party data for enhanced conversions)

← back to the reading room