Shopify payment info tracking in Google Ads
Track Shopify payment submissions with Customer events and GTM. Keep this milestone separate from purchases and verify its Google Ads tag.
Shahzada Ali Hassan, founder of Crisperchecked against 15 sources
Tools
The short answer
Use Shopify Customer events and GTM to measure payment-information submissions as a separate Google Ads conversion action. Shopifyshopify.dev exposes payment_info_submitted on the checkout page when a customer submits payment information. This guide is for store owners and implementers maintaining a custom pixel.
- Listen for
payment_info_submittedshopify.dev in Customer events. - The snippet pushes
add_payment_infoto GTM. - Conversion tags need an ID and labelsupport.google.com.
- If an existing integration already covers this event, inspect it before adding another sender.
- Steps and settings checked against Shopify and Google documentation on 25 October 2026.
FREE AUDIT
NO LOGINCheck what Meta and Google can count on your site
- Your site
Crisper- Meta and Google count it
Enter your website to see how good its tracking is, and whether Meta is likely restricting it.
On this page 7 sections
- Does submitting payment information mean a purchase is complete?
- How do I add the custom pixel in Shopify?
- What code tracks Shopify payment submissions?
- How do I set up the Google Ads tag in GTM?
- How do I test payment submissions on Shopify?
- When is this the wrong setup, and what can go wrong?
- What changed in this guide
01Does submitting payment information mean a purchase is complete?
Submitting payment informationshopify.dev and completing a purchaseshopify.dev are distinct Shopify events. Test both steps separately and reserve your Purchase trigger for the completed order.
02How do I add the custom pixel in Shopify?
Prepare this walkthrough in a development store with a test GTM container. Shopify suggests testing pixels in a dev storehelp.shopify.com before adding them to a live store.
1. Open Customer events and check the loader
- In the test store, open Settings > Customer events > Add custom pixel.
- Name the pixel.
- Review its Customer privacy settings using Shopify's pixel instructionshelp.shopify.com, and use settings that match your consent plan.
Shopify's GTM tutorialhelp.shopify.com uses the container loader as JavaScript without script tags. The snippet below includes a loader.
- Replace the snippet's GTM placeholder with the ID of a test container that only your development store loads.
- If this pixel already loads GTM, keep that loader once and append only the event subscription and its helper.
Done when the editor is open, the privacy settings are recorded and the pixel contains one loader for the intended test container.
03What code tracks Shopify payment submissions?
Subscribe to payment_info_submitted and push the mapped values into the data layerdevelopers.google.com, the object GTM reads for events. The Shopify event referenceshopify.dev documents the fields used below.
2. Add the event subscription
event.data.checkout supplies currencyCode, totalPrice.amount, shippingLine, totalTax and lineItems, as listed in Shopify's payload referenceshopify.dev. The callback is the function that runs when Shopify delivers this event.
- Add the snippet below to the pixel's code.
- Save and connect the pixel in the test store following Shopify's connection stepshelp.shopify.com.
// Initialize the dataLayerwindow.dataLayer = window.dataLayer || [];(function (w, d, s, l, i) { w[l] = w[l] || []; w[l].push({ "gtm.start": new Date().getTime(), event: "gtm.js" }); var f = d.getElementsByTagName(s)[0], j = d.createElement(s), dl = l != "dataLayer" ? "&l=" + l : ""; j.async = true;
95 more lines of JavaScript
- Copy and download
- Emailed to you
Unlock this snippet
Three details, and the full code is yours
No account needed. Unlock once and every snippet on the blog opens.
Done when Customer events shows Connected and the saved code contains the payment_info_submitted subscription once.
Shopify's event referenceshopify.dev allows product and variant IDs to be null, and checkout line items can have a null variant. The filter keeps only rows whose product and variant IDs are strings with non-empty trim() results before mapping items. It preserves each retained ID unchanged. The event and its value stay intact even when no valid item remains.
The GTM event is add_payment_info; the Shopify subscription is payment_info_submitted. The tag must listen for the former because that is what the snippet pushes.
The address mapping reads shippingAddress.province, the region field in Shopify's referenceshopify.dev. The retained user_data object is not mapped into the basic Google Ads tag below; keep enhanced-conversion work separate.
Shopify defines a discount code as the title of a DISCOUNT_CODE applicationshopify.dev. The snippet filters that type before joining its titles, so an automatic discount name is not presented as a code.
This revision keeps page details in page_data without changing browser history. history.pushState requires a same-origin URLdeveloper.mozilla.org; the event push no longer depends on that extra operation succeeding.
04How do I set up the Google Ads tag in GTM?
Use Google Ads Conversion Tracking for this checkout milestone. Google's tag instructionssupport.google.com describe the ID and label fields.
For an observation-only test, use a separate secondary conversion action and keep it out of custom goals. Google says secondary actions appear in All conversions and are not used for bidding, except when included in a custom goalsupport.google.com.
3. Create the variables and event trigger
A Data Layer Variable reads a named value for a tag, and a trigger tells GTM when to run a tag.
- Create each Data Layer Variable in the table below, using Version 2, which reads dots as nested fieldssupport.google.com.
- Create a Custom Event triggersupport.google.com with event name
add_payment_info. - Turn regular-expression matching off on that trigger and save it.
DLV - Value
- Data layer variable name
- ecommerce.value
- Purpose
- Checkout or item amount
DLV - Currency
- Data layer variable name
- ecommerce.currency
- Purpose
- Currency from Shopify
Done when the saved variable names and paths match the table and the trigger's saved event name is add_payment_info.
4. Map the tag fields
- In Google Ads, open the intended conversion action.
- Open Tag setup > Use Google Tag Manager.
- Copy its Conversion ID and Conversion Label into the GTM tag; Google distinguishes the account ID from the action-specific labelsupport.google.com.
- Set the remaining tag fields and trigger as shown in the table below.
- Check the associated Google tag is present in the test container; Google's remarketing instructions require it for optimal browser compatibilitysupport.google.com. The Google tag IDsupport.google.com is distinct from your
GTM-container ID. - Save the event tag.
Conversion ID
- Setting for this walkthrough
- Your test action's account Conversion ID
Conversion Label
- Setting for this walkthrough
- The label for your add_payment_info action
Conversion Value
- Setting for this walkthrough
- 0 for this observation-only example
Currency Code
- Setting for this walkthrough
- {{DLV - Currency}}
Transaction ID
- Setting for this walkthrough
- Leave empty; this is not an order
Trigger
- Setting for this walkthrough
- add_payment_info
Done when the saved event tag's fields, destination and trigger match your test plan.
The snippet retains the checkout total in ecommerce.value for inspection, but this example sends an explicit zero conversion value. GTM sends zero when Conversion Value is empty or undefinedsupport.google.com; setting it explicitly makes this example's choice visible.
05How do I test payment submissions on Shopify?
Use Customer events > Test to inspect the event with Shopify Pixel Helperhelp.shopify.com, then inspect the Google request separately. Start with the test store and test container prepared above.
5. Publish the version in the test container
Changes saved in a workspace do not run yet. Google sayssupport.google.com you need to publish workspace changes to make them operational.
- Open the test container that only your development store loads.
- Select Submit, then choose Publish and Create Version.
- Name the version and publish.
Do not publish to a container your live store loads; move the tested setup there through your normal release process.
Done when the test container's Versions list shows your version as published and the pixel code loads that container's ID.
6. Follow one test action through the setup
- Open the connected custom pixel and choose Test using Shopify's testing stepshelp.shopify.com.
- Exercise the consent choice for your test and check that Pixel Helper's consent status matches that choice.
- Submit payment information during a test checkout.
- In Pixel Helper, check that
payment_info_submittedis listed, and inspect the payment-submission event before comparing any later purchase event. - Inspect the pixel's console entry and data-layer push for
add_payment_info: the event name should match your saved GTM trigger, and the expected fields should contain the test values. - In browser developer tools, inspect the outgoing Google Ads conversion request: it should use the milestone action's ID and label, the explicit zero value and the expected currency, rather than the Purchase label.
- Record the test time, event ID, container version and observed request fields.
- Run the subscription locally with null, empty, whitespace-only and non-string values for each ID field.
- Include a null-variant checkout line, a mixed list with a valid line, and an all-invalid list.
- Repeat with amounts of 0 and a nonzero amount, passing retained items through any downstream formatter.
Done when every check above matches, the notes identify what passed and any missing or repeated request that still needs investigation, and in the local runs the event, currency and value stay intact, genuine IDs remain unchanged, and no mapped ID is blank or replaced by a product name.
06When is this the wrong setup, and what can go wrong?
Use this guide when you need to maintain this custom event mapping. Shopify advises reviewing available apps before creating a custom pixelhelp.shopify.com; if an app already handles the job, inspect that integration first.
- Using the Purchase conversion label for payment submission: the tag would use the purchase action's identifiersupport.google.com for a different step. Use a dedicated milestone label.
- Adding a second sender without checking the first: Shopify warns overlapping pixel installations can count events twicehelp.shopify.com. Inventory the existing event sender before adding this one.
- Saving a tag without checking the actual request: a filled-out tag is only a configuration. Match the request fields to your recorded test action.
If you also need storefront coverage, the Shopify Google Ads page-view guide walks through the separate page-view trigger.
07What changed in this guide
- 25 October 2026: Added the Shopify event explanation, Google Ads tag mappings and test checks; preserved existing event names and corrected payload handling. Corrected the address region lookup and discount-code mapping. Removed the history update before the event push. Added the isolated test-container publication procedure and published-version check. Filtered items missing either product or variant IDs and added null-item checks without changing event values. Replaced the repeated introduction with the next event-specific check. Rejected whitespace-only and non-string item IDs while preserving genuine IDs, and added formatter checks for mixed and invalid items.
Sources
15 sources
- 1payment_info_submittedshopify.dev↩
- 2Conversion tags need an ID and labelsupport.google.com↩
- 3completing a purchaseshopify.dev↩
- 4Shopify suggests testing pixels in a dev storehelp.shopify.com↩
- 5Shopify's pixel instructionshelp.shopify.com↩
- 6Shopify runs custom pixels in a sandboxhelp.shopify.com↩
- 7Shopify's GTM tutorialhelp.shopify.com↩
- 8data layerdevelopers.google.com↩
- 9history.pushState requires a same-origin URLdeveloper.mozilla.org↩
- 10Google says secondary actions appear in All conversions and are not used for bidding, except when included in a custom goalsupport.google.com↩
- 11Version 2, which reads dots as nested fieldssupport.google.com↩
- 12Custom Event triggersupport.google.com↩
- 13Google's remarketing instructions require it for optimal browser compatibilitysupport.google.com↩
- 14Google tag IDsupport.google.com↩
- 15Google sayssupport.google.com↩

