How do you set up enhanced conversions for Shopify?

Enhanced conversions attach hashed customer details to a conversion so that Google can match an order to an advertising interaction even when the usual browser identifiers are unavailable. The details are hashed before they leave the browser or the server, so what is sent is an irreversible representation rather than the address itself.

The benefit is coverage. A share of orders that would otherwise be unattributed become attributable, which improves the reported conversion count and, more importantly, gives the bidding more examples to learn from. On accounts using automated bidding, that second effect is usually the larger one.

It is not a replacement for consent. Where a visitor has declined, the data should not be sent, and enhanced conversions do not create permission that does not exist.

It also does not fix a broken tag. If your purchase event is not firing, or is firing twice, adding enhanced conversions will faithfully improve the matching of a number that was already wrong.

For most stores this is the right answer. Installing and connecting the official channel links your Shopify store to your Google Ads and Merchant Center accounts, sets up the conversion tracking for purchases, and provides the option to include customer-provided data with those conversions.

Before enabling it, accept the customer data terms in Google Ads, since the setting cannot function without that agreement in place. Then work through the channel's own settings for data sharing, and make sure your privacy policy describes what you are doing.

The advantage of this route is that Shopify's checkout provides the order data in a supported way and you are not maintaining custom code across theme updates. The limitation is flexibility: if you need to send the data to a server-side container or to combine it with other tags, you will want the second route.

After enabling it, leave it for a few days and then check the diagnostics in Google Ads, which report on how much enhanced data is being received and whether it is in the expected format.

Shopify's customer events system is the supported place for custom tracking on modern checkouts, replacing the older practice of pasting scripts into the order status page. A custom pixel subscribes to the checkout completed event and receives the order details, including the customer information you need.

From there, send the conversion with the user-provided data to your Google tag, or forward it to a server-side container if you run one. This is the route to use when you already maintain a tagging layer, when you want the same data going to several destinations, or when you want the event to originate from your server rather than the browser.

Format before hashing. Email addresses lowercased and trimmed, phone numbers in international format, names and addresses normalised the way Google documents. A poorly formatted value hashes to something that will never match, and the setup will appear to work while achieving nothing.

And respect the consent state inside the pixel. Shopify's privacy features expose the visitor's choices to customer events, so the code can decide whether to send anything at all.

Check three things after setup. That the purchase conversion is still recorded exactly once per order, which is easy to break while changing tags. That the enhanced data is being received, which the conversion diagnostics report on. And that the match rate is reasonable rather than near zero, since a near-zero rate almost always means a formatting error.

Compare a week of conversions before and after. You should see the conversion count rise modestly with no change in your actual orders, which is the expected signature of better matching. A large jump usually means duplication rather than improvement.

Then give the bidding time. More matched conversions changes what the automated strategies see, and the account will take a little while to settle in the same way it does after any measurement change.

After that, treat it as infrastructure. Re-check it after any theme change, checkout change, app installation or consent tool update, because those are the events that quietly break it.