CONNECTIONS / Shopify / Shopify to Google EC Web
Shopify checkouts, recovered for Google Ads.
Safari and in-app browsers drop a share of Shopify checkouts before Google's tag ever fires. Signals hashes the checkout's customer data and supplements your existing Google Tag conversions with it, recovering the purchases cookies miss.
- ● shopify → google.ec_web :: live
- > event Checkout completed value=298.00 AED
- hash sha256(email,phone)
- route google.ec_web enhance
- ✓ delivered · conversion enhanced
WHAT THIS ENABLES
Shopify to Google Enhanced Conversions
Shopify to Google Enhanced Conversions Web hashes the customer data collected at Shopify checkout and sends it alongside your existing Google Tag conversions, so Google Ads recovers purchases that cookie-based tracking alone misses.
- Checkout conversions recovered on Safari, in-app browsers, and any session where cookies do not survive.
- Smart Bidding trained on hashed, first-party checkout data instead of thinning cookie signal.
- Recovery layered onto the Google Tag you already run, with no separate conversion action.
WHAT FLOWS WHERE
Shopify to EC Web, mapped.
Shopify checkout data is hashed by Signals and sent to Google as an Enhanced Conversion tied to the same conversion action your Google Tag already reports, filling in identity where the cookie-based hit was thin or missing.
Shopify checkout data is hashed by Signals and sent to Google as an Enhanced Conversion tied to the same conversion action your Google Tag already reports, filling in identity where the cookie-based hit was thin or missing.
Built for the teams that own the number.
Teams told by Google to raise signal quality ahead of value-based bidding.
From kickoff to verified events.
-
Audit
Existing Google Tag or GTM setup and current Enhanced Conversions coverage reviewed against Shopify's checkout events.
-
Configure
Checkout customer data hashed and passed to Google's Enhanced Conversions endpoint alongside the standard purchase tag.
-
Verify
Recovered conversions confirmed inside Google Ads diagnostics before scaling budget on the improved signal.
What ships with this use case.
Purchase conversions Google Ads would otherwise undercount on Safari and iOS traffic.
Hashed first-party checkout data delivered per Google's Enhanced Conversions spec.
One Google Tag setup that keeps working exactly as configured, just backed by more identity.
What EC Web actually receives.
- ● signals :: event payload
- > POST /enhanced_conversions source=shopify.checkout
- hashed_email sha256 "b13f0a…" · hashed_phone_number sha256 "71cd8e…"
- order_id "#SH-30281" · conversion_value 298.00 · currency_code AED
- conversion_date_time "2026-07-19 11:04:00+04:00"
- ✓ accepted · enhancement applied
Adjacent moves on the same stack.
from Shopify
Shopify to every ad platform
Shopify to every ad platform is a single install that maps Shopify's order and checkout…
Learn morefrom Shopify
Shopify to Meta Click-to-Message
Shopify to Meta Click-to-Message Conversions ties a Shopify order back to the…
Learn more
same use case
BigCommerce to Google EC Web
Google Enhanced Conversions for BigCommerce: Signals recovers checkout conversions with…
Learn moregeneric
Google Enhanced Conversions Web
Datahash configures Enhanced Conversions Web with server-side user-data collection and…
Learn moreAsked on almost every call.
Does this replace the Google Tag already installed through Shopify's native integration?
No. Enhanced Conversions rides on top of the conversion action your Google Tag already reports. Signals adds the hashed customer-data layer to that same tag; nothing about the tag's placement or the conversion action itself changes. Your team keeps managing the Google Tag through Shopify exactly as it does today, with Signals only supplementing what it already sends.
What happens to a checkout where a shopper declined cookie consent?
Consent Mode v2 status is read per session, and no identifiable data is sent for a session that declined it. Google fills that gap with modeled conversions, exactly as it does for any Enhanced Conversions setup, so a checkout with no consent still contributes to Smart Bidding through Google's own modeling rather than a hashed match.
NEXT STEP