Enhanced Conversions on Shopify in the EU (Consent Mode Included)

Illustration: a stream of rose and cream squares passing through an open cream padlock and continuing as a gold line.

Enhanced conversions can be switched on in Google Ads and still send an empty email parameter on every order, and nobody notices because the toggle looks fine.

In the EU there is a second layer. Even when the data is there, consent decides whether Google is allowed to use it. This post covers where the hashed email originates on Shopify, which consent state allows it, and how to check it in Google Ads. For the full tracking review, start with the Shopify conversion tracking audit, since this one goes deeper on a single feature.

What enhanced conversions actually send

Enhanced conversions supplement your existing conversion tag. When a customer converts, your site sends hashed first-party data, and Google matches it against signed-in Google accounts that engaged with your ads. Google says it hashes the data with SHA256 before it leaves the browser, and the fields it names are email address, name, home address and phone number (About enhanced conversions, as of November 2026).

It rides on the purchase you already track, so if the purchase tag is wrong, enhanced conversions just attaches good data to a bad event. It also needs the data to exist on the page at the moment the tag fires, and on Shopify that is the part that goes wrong.

Where the hashed email comes from on Shopify

There are three realistic paths. They differ in who collects the email and who is responsible when it goes missing.

PathWhere the user data comes fromWhat you controlBest for
Google & YouTube appThe app, once you turn on enhanced conversions in its settingsVery little. One toggle plus the customer data termsSmall stores that want no maintenance
Shopify custom pixelCheckout data in the pixel event, which you pass to your tagEverything: fields, timing, consent logicStores that want one source for Google Ads, GA4 and Meta
GTM or Google tag on the storefrontYour own variables or automatic detection on the pageDepends on the setupStores with an existing container and a developer

The app. Google’s Shopify guide says you can turn on enhanced conversions when you first connect Google Ads, or later in the app’s Settings tab under Google Ads settings, and that you must review and agree to the customer data terms (Google & YouTube app setup, as of November 2026). That is all there is to configure, so when the match rate is poor there is almost nothing to inspect.

A custom pixel. Shopify’s checkout_completed event carries a checkout object with email, phone, billingAddress and shippingAddress, and each of them can be null (checkout_completed, as of November 2026). So if your code reads the email and passes it along without checking, some orders go out with an empty field. More on that below.

Custom pixels also run in a sandbox where not everything works, and Shopify states that adding and using them is unsupported by Shopify and that consent compliance is your responsibility (Custom pixels, as of November 2026).

The Google tag or GTM. Google’s tag setup offers automatic detection, CSS selectors or JavaScript variables, and a code snippet that sends hashed data directly. Code snippet data is always prioritized if you combine methods (Set up enhanced conversions for web using the Google tag, as of November 2026). Shopify’s checkout is not a normal storefront page. Scraping it for an email field is the weakest option here, so I pass explicit values from a pixel event.

Use one path per store, because if you can’t say in one sentence where your hashed email originates, you probably have two.

A banner alone isn’t enough.

Consent Mode v2 has four consent types. Two matter here:

  • ad_storage controls advertising cookies.
  • ad_user_data “sets consent for sending user data to Google for online advertising purposes” (Consent mode overview, as of November 2026).

Google’s consent mode table lists “Enhanced conversions: Hashed first party data” as disabled when ad_user_data is denied, along with user_id (Consent mode overview). Google’s own consent help says it directly: “The ad_user_data consent type is required for measurement use cases, such as enhanced conversions” (Set up and manage consent, as of November 2026). That page is written for Google tag users who receive data from end users in the EEA.

So the rule in plain terms: a visitor in the EEA who has not granted ad_user_data produces no hashed email in your enhanced conversions. Not granting also covers “not set”, since Google’s consent help describes a consent form as not granted when it is “not set or denied” (Set up and manage consent, as of November 2026).

That leaves two questions people mix up.

Does this kill measurement for those visitors? Not entirely. In advanced consent mode, tags load when the page opens and send cookieless pings while consent is denied, which Google uses for modeling. In basic mode, tags don’t load until the visitor interacts with the banner, and if they decline, nothing is sent at all (About consent mode, as of November 2026). Neither mode sends the hashed email for a visitor who denied ad_user_data. Enhanced conversions only recovers matches for visitors who consented. The general effects are covered in what happens if a user doesn’t give tracking consent and is consent mode necessary for accurate tracking.

Does the Shopify banner do this for you? It depends on which pieces you use. Shopify configures its cookie banner automatically for visitors in the UK and EEA when you have active markets there. It also says its banner covers Shopify’s own tools, and third-party cookies or pixels may need a third-party banner or custom logic. Shopify warns that if your regions don’t match a third-party banner’s regions, non-essential data can be processed before the visitor consents (Customer privacy settings, as of November 2026).

For app pixels, Shopify’s pixel manager only loads the pixel if the visitor has permitted every category it declared. For custom pixels you define the required privacy settings in the admin, and Shopify’s examples read the consent state from the Customer Privacy API and check it before sending event data (Pixel privacy, as of November 2026).

I could not confirm from Shopify’s or Google’s documentation how each Shopify consent category maps to the four Google consent types in every setup, so test it as described in the next section.

How to verify it in Google Ads

Do this on a real order, not only in diagnostics.

  1. Check the request. In Chrome DevTools, open the Network tab, filter for “google” and find the conversion request to googleadservices.com/pagead/conversion/ (some browsers use google.com/pagead/1p-conversion/). In the payload, look for the em parameter. A healthy one starts tv.1~em. followed by a hashed string. If nothing follows, the tag sent an empty parameter (Set up enhanced conversions for web using the Google tag, as of November 2026).
  2. Run it twice. Once after accepting all categories in the banner, once after declining. Accepted shows a hashed value. Declined shows none for an EEA visitor, and if it still shows a hash then your consent wiring needs checking.
  3. Open the diagnostics. In Google Ads go to Goals, then Summary. Hover over the tracking status of the purchase action, select Details, then the Diagnostics tab. Google says the report is available about 72 hours after implementation.
  4. Read the status. The report uses four: Excellent, Good (active, but more user data would improve matches), Needs attention (active, with errors to fix), and No recent data (nothing recorded in the last 7 days). Alerts don’t display with fewer than 20 conversions in the past 7 days (tag diagnostics report, as of November 2026).
  5. Look at the match rate. It is reported as Unknown value, INSUFFICIENT_VOLUME (fewer than 20 valid pings), NO_MATCHES, LOW (0 to 15%) or HIGH (above 15%). If the rate looks low on an EU store, consent is one possible cause, so look at the request in the Network tab first.

The em error codes are worth knowing. Google’s diagnostics page says tv.1~em. with nothing after it means the parameter is present but empty, e0 is a failed formatting check, e1 an unsupported browser, e2 a SHA256 failure from unexpected characters, and e3 a page that isn’t secure (tag diagnostics report, as of November 2026).

The failure modes to check

Duplicate sources. The app sends the purchase and a custom pixel or old GTM tag sends it too. Google’s Shopify guide tells you to check for duplicates when you track in the app and in a storefront or custom pixel, and to remove legacy tags. Google also says data sent through a method other than the one selected in Google Ads can go unprocessed, so a second source can send data that Google ignores. The audit covers how to count the sources.

Switched on, no data. The toggle is on, but the parameter is empty. Google lists the usual causes in the diagnostics: the data isn’t on the page when the tag fires, or selectors and variables fail on some browsers or devices. On Shopify, add one more: a checkout where email is null, such as an order where the customer never supplied one at that step. Guard for it, and log the case instead of sending an empty string.

Terms not accepted. Google says data sent before you accept the customer data terms isn’t processed, and without acceptance it isn’t collected at all. This is the easiest one to miss, because the tag still looks fine in DevTools. In diagnostics it appears as “Enhanced conversions not in use”.

Bad formatting. Emails without an ”@” or phone numbers without a country code trigger the formatting alerts. If you build the data yourself in a custom pixel, validate it before it reaches the tag.

Banner not wired to Consent Mode v2. The banner shows, visitors click, and Google tags never hear about it. Consent defaults must be set on every page before any measurement command, and the choice sent as an update when the visitor interacts, with wait_for_update for banners that load asynchronously (Manage consent settings, as of November 2026). A banner that only hides a popup does nothing for ad_user_data.

Mismatched regions. Your Shopify banner covers one set of countries and your third-party banner another. Visitors in the gap get tracked before they choose.

A short checklist

  • One source for the purchase and its user data.
  • Customer data terms accepted in Google Ads.
  • ad_user_data and ad_personalization defaulting to denied for EEA visitors, updated on choice.
  • A real accepted order shows a hashed em value. A real declined order doesn’t.
  • Diagnostics reads Good or Excellent after 72 hours, with enough volume for alerts to appear.
  • Banner regions match across Shopify and any other consent tool.

Re-check it monthly, since themes, apps and consent tools change.

Conclusion

On Shopify you need a clean hashed email on the purchase event and a consent state that allows you to send it, so fix the source first, wire consent second, and prove both on a real order before you trust the dashboard. If conversions are still missing afterwards, why some conversions go missing covers the wider causes. If you’d rather hand it off, we check all of this as part of our analytics implementation work. Schedule a call and send me your current diagnostics screenshot.

With Texonica, you get less hype more results.

We are determined to make your business successful. Reserve your free-no-obligation strategy session today.

Schedule a Call