Google Ads Enhanced Conversions for Leads on Shopify: Should You Enable It?

TL;DR

A Shopify store with no lead forms anywhere on it can still need a setting called enhanced conversions for leads. That is not a quirk of your account. It is how Google's API is built: hashed identifiers ride on ClickConversion.user_identifiers, and that field is governed by the leads opt-in [1]. The confusion comes from the setting's other half, the web row, which is the one that takes a method selection and the one you can break by changing it. Google is merging the two into a single switch during 2026 [4], which means the screen you see depends on when your account migrates.

Key Takeaways

• The leads row's method dropdown offers exactly two choices, "Google tag" or "Google Tag Manager", chosen "based on how you instrument your Tag on your website" [2]. There is no Google Ads API option in it, and none is needed.
• Server-side uploads carrying hashed customer data require the leads opt-in regardless of what you sell: Google's developer documentation says you "must populate the user_identifiers field" when using enhanced conversions for leads, imported through UploadClickConversions [1].
• Two account-level prerequisites gate it: accepted customer data terms and the leads setting enabled [1]. Until both are true, Google rejects identifier-carrying uploads with CUSTOMER_NOT_ENABLED_ENHANCED_CONVERSIONS_FOR_LEADS [5].
• The separate web enhanced-conversions row is the one that accepts a Google Ads API method, and it works through conversion adjustments rather than through click conversion uploads [3].
• If your web row already reads as active and managed through the Google tag, leave it alone. Changing the method on a live row is the most common way merchants break enhanced conversions they already had.
• Starting April 2026, Google Ads accepts user-provided data from website tags, Data Manager and API connections at the same time. Starting June 2026, web and leads merge into one on/off switch and method selections disappear from the account [4].
• Accounts are migrating gradually. Some still showed the two-row layout in September 2026, so both screens are current depending on where you land.

Why an ecommerce store gets asked about a leads setting

Start with what the name promises and what the plumbing does.

The name promises lead capture: a form on your site, a contact record, an offline sale weeks later, an import that ties the two together. Almost no Shopify store works that way.

The plumbing is narrower and stranger. Google's developer documentation for enhanced conversions for leads through the Google Ads API states, in one line, that "when using enhanced conversions for leads, you must populate the user_identifiers field", on ClickConversion objects imported using ConversionUploadService and its UploadClickConversions method [1]. That is the same object and the same method a server-side Shopify tracking app uses to upload a purchase. Attach a hashed email to it and, as far as Google's API is concerned, you are on the leads rail.

The prerequisites are stated in the same document as account settings you can query directly: customer.conversion_tracking_setting.accepted_customer_data_terms and customer.conversion_tracking_setting.enhanced_conversions_for_leads_enabled, with the instruction that you "must opt in to enhanced conversions for leads and accept the customer data terms" [1]. Miss either and the upload does not silently degrade to a conversion without identifiers. It is rejected, with CUSTOMER_NOT_ENABLED_ENHANCED_CONVERSIONS_FOR_LEADS [5].

So the honest framing for a merchant is: this toggle authorizes customer data on API-uploaded conversions. The word "leads" describes the use case Google designed it for, not the boundary of what it controls.

What the leads dropdown actually offers

Here is where the public documentation genuinely misleads, so it is worth quoting rather than paraphrasing.

Google's page on upgrading an offline conversion import to enhanced conversions for leads says: "You'll check the toggle to turn on enhanced conversions for leads, and then select 'Google tag' or 'Google Tag Manager' based on how you instrument your Tag on your website." Step 5 of the same procedure repeats it: "Select either Google tag or Google Tag Manager based on what you use on your website" [2].

Two options. Both of them tag options. Meanwhile the same help documentation lists "Support in Data Manager, Google Ads API, and third-party import methods like Zapier and Hubspot" as ways the data can arrive [2].

That reads like a contradiction and is not one. The dropdown governs on-page lead-form capture, which is how the identifiers get collected in a tag-based setup. Data Manager, the API and third-party connectors are import routes for data you already hold. They are not choices in that menu, and picking "Google tag" while your data arrives via the API is the correct configuration, not a compromise.

The asymmetry is real and it is the whole source of the confusion: the web enhanced-conversions row is the one that can take Google Ads API as a method, and Google documents that path as working "similar to other conversion adjustments" [3]. Web enhanced conversions use adjustments. Leads use identifiers on the click conversion itself. Same feature name, two different mechanisms, two different rows in the same settings screen.

The row you should not touch

Open the Goals icon, then Conversions, then Settings in Google Ads and you will find both rows. Treat them differently.

That last row is the expensive one. A store running Shopify's Google & YouTube channel will usually see the web row already active and managed through the Google tag, because the channel carries its own enhanced conversions toggle. Switching an active row's method to Google Ads API is risky because Google warns that data sent by a method other than the one selected may not be processed [7], and unless something else is sending web enhanced conversion adjustments, you have removed a working feature and replaced it with nothing.

The pattern is easy to fall into because older setup guides say "select Google Ads API" without distinguishing the two rows, and because the leads row is where an API user actually belongs. Read the row label before the method dropdown. That single habit prevents the entire failure.

For the tag-side setup and how to confirm it is working, enhanced conversions setup and verification is the walkthrough. For everything at the account level, including the settings that decide whether an upload is accepted at all, the Google Ads settings that actually matter covers the same screen from the server-side angle. Neither is restated here.

April and June 2026: the two settings become one

Google published the timeline itself, and it explains why two merchants can compare screenshots and disagree about what exists.

"Starting in April 2026: Google Ads will simultaneously accept user-provided data from website tags, Data Manager, and API connections." And: "Starting in June 2026: Enhanced conversions for web and leads will be combined into a single feature with a simple on/off switch. You will no longer see different method selections in your Google Ads account" [4]. Accounts that had already accepted the customer data terms are migrated automatically, and the unified control lives in settings under a customer data use panel with a single turn-on action [4].

The rollout is gradual. Accounts were still showing the separate rows and the method dropdown in September 2026. So there are two correct answers to "what should my screen look like", and which one applies to you is a question of migration order rather than configuration:

• Old layout. Two rows. Leads takes Google tag or Google Tag Manager only [2]. Web can take Google Ads API when it is not already configured [3].
• New layout. One switch. No method selection anywhere. All three sources accepted at once [4].

Google's own leads page now opens with the combined single-setting banner [2], which is why the screen you see depends on your account's migration state rather than on anything you configured.

If you land on the new layout, most of the anxiety in this article evaporates, because the decision that used to be a method dropdown is now a yes. If you land on the old one, the row-by-row table above still governs. Do not assume you have the new screen because a guide published this month describes it.

For where Data Manager fits into this and what changes for server-side Shopify tracking generally, Data Manager API versus the Measurement Protocol covers the wider shift.

So should you enable it?

Three cases cover nearly every Shopify store.

Your tracking app uploads conversions with hashed customer data. Enable it. Without the opt-in and the accepted terms, those uploads are rejected outright [1][5], so this is not an optimization. It is the precondition for the uploads working at all.

You track only through tags, via the Google & YouTube channel or your own GTM setup, and import nothing offline. The leads toggle adds nothing for you. Your enhanced conversions live on the web rail, already configured through the tag, and the correct action is none.

You upload conversions without identifiers, for example click conversions carrying only a gclid. No opt-in required, because no user_identifiers field is populated. The moment you turn on identifier sending, the first case applies. Uploads without a click ID are a different topic, covered in Google Ads conversions without a gclid.

One thing to check on the app side before you flip anything: enhanced conversions are typically off by default in a tracking app, because sending hashed customer data is a decision the merchant should make deliberately. In WeltPixel Conversion Tracking the control is an "Enable Enhanced Conversions" toggle in advanced settings, off unless you turn it on, and Google Ads conversion tracking itself sits on the app's Plus plan, which is an app subscription tier and has nothing to do with Shopify Plus. When it is on, the app sends SHA-256 hashed email and phone (phone normalized to E.164 before hashing), plus hashed name with country and postal code. Street address is never part of the Google Ads identifiers.

FAQ

Do I need enhanced conversions for leads if my Shopify store has no lead forms?

Yes, if something uploads conversions to Google Ads through the API with hashed customer data. Google's documentation requires the user_identifiers field for enhanced conversions for leads and gates it behind the account-level opt-in plus accepted customer data terms [1].

Why does the dropdown only show Google tag and Google Tag Manager?

Because that dropdown describes how lead-form data is captured on your site. Google's own instruction is to "select either Google tag or Google Tag Manager based on what you use on your website" [2]. API and Data Manager are import routes listed elsewhere on the same page, not options in that menu.

Will turning on the leads setting break my existing web enhanced conversions?

No. They are separate rows with separate mechanisms: leads uses identifiers on uploaded click conversions [1], web uses conversion adjustments [3]. What breaks things is changing the method on an already-active web row.

What error do I get if I upload identifiers without enabling it?

CUSTOMER_NOT_ENABLED_ENHANCED_CONVERSIONS_FOR_LEADS [5]. It is an account configuration error, not a data error, so retrying the same payload after enabling the setting works.

My account only shows one enhanced conversions switch. Where did the rows go?

You have been migrated. From June 2026 Google combines web and leads into a single on/off feature and removes method selections from the account [4].

If you want the upload side handled from your order record rather than from a browser tag, WeltPixel Conversion Tracking [6] sends Google Ads click conversions server-side with gclid, gbraid or wbraid and the Shopify order ID as the transaction key, across nine integrations.

Before you change anything, take a screenshot of the settings screen as it is today. When the unified switch arrives, that screenshot is the only record of what your account used to do.

Sources

1. Google Ads API documentation, "Enhanced conversions for leads" setup (must populate user_identifiers on ClickConversion; imported via ConversionUploadService / UploadClickConversions; prerequisites customer.conversion_tracking_setting.accepted_customer_data_terms and customer.conversion_tracking_setting.enhanced_conversions_for_leads_enabled), developers.google.com/google-ads/api/docs/conversions/enhanced-conversions/leads-setup, accessed September 7, 2026
2. Google Ads Help, "Upgrade offline conversion import to enhanced conversion for leads" (select "Google tag" or "Google Tag Manager"; support in Data Manager, Google Ads API and third-party import methods), support.google.com/google-ads/answer/14274408, accessed September 7, 2026
3. Google Ads Help, "Set up enhanced conversions for web using the Google Ads API" (process similar to other conversion adjustments), support.google.com/google-ads/answer/13261987, accessed September 7, 2026
4. Google Ads Help, "Updates to your enhanced conversions settings" (April 2026 simultaneous acceptance from tags, Data Manager and API; June 2026 single on/off switch with method selections removed; automatic migration), support.google.com/google-ads/answer/16884284, accessed September 7, 2026
5. Google Ads API, conversion upload error enum CUSTOMER_NOT_ENABLED_ENHANCED_CONVERSIONS_FOR_LEADS, developers.google.com/google-ads/api/reference/rpc/v22/ConversionUploadErrorEnum.ConversionUploadError, accessed September 7, 2026
6. WeltPixel Conversion Tracking, Shopify App Store listing, apps.shopify.com/weltpixel-conversion-tracking, accessed September 7, 2026
7. Google Ads Help, "Set up enhanced conversions for web using the Google tag" (data sent by a method other than the one selected may not be processed), support.google.com/google-ads/answer/13258081, accessed September 7, 2026