dataLayer events in the Shopify customer events pixel
Shopify's Customer Events run inside a sandboxed web pixel, so which dataLayer events are present in AdPage's Customer Events Pixel?
Shopify's Customer Events run inside a sandboxed web pixel, which means the events fired on the checkout and thank-you pages do not show up in the normal dataLayer the way they do on the rest of your store. You cannot inspect them with GTM Preview mode or by typing window.dataLayer into the console.
This article lists every event AdPage sends from Customer Events, with a full example payload for each, so you can configure your tags without needing to debug them live.
Event overview
trytagging_user_data
Checkout & Thank you
Every page load
trytagging_begin_checkout
Checkout
When the checkout opens, immediately after trytagging_user_data
trytagging_add_address_info
Checkout
Every time the customer completes their full address
trytagging_add_shipping_info
Checkout
Every time the shipping method changes
trytagging_add_payment_info
Checkout
Every time the customer enters payment details and clicks pay
trytagging_purchase
Thank you
On the payment event from Shopify
In GTM, set up a Custom Event trigger matching the exact event name for each event you want to use. Note that trytagging_add_address_info, trytagging_add_shipping_info and trytagging_add_payment_info can fire more than once per checkout, so add trigger conditions if you need to deduplicate.
Shared objects
Three blocks repeat across most events. They are shown in full in every payload below, but you only need to understand them once.
marketing carries the session and click identifiers: the GA cookie values, client_id, session_id, session_count, the advertising click IDs (fbp, fbc, ttclid, ttp, gclid, gbraid, wbraid), the original referrer, UTM parameters, user agent and hostname. Identifiers that are not present in the session come through as null rather than being omitted, so your variables will always find the key.
user_data carries customer details. It contains two sets of fields for the same values: the current customer_* fields, and an older set (id, email, firstName, and so on). Always use the customer_* fields — the others are deprecated and kept only for backwards compatibility.
Page-level fields (event_time, page_referrer, page_location, page_title) appear on every event.
Checkout page
trytagging_user_data
Fires on every page load of the checkout.
trytagging_begin_checkout
Fires as soon as the checkout opens, directly after the trytagging_user_data event.
Note that at this point the customer fields are still empty — the visitor has not entered anything yet. customer_name reads undefined undefined because it concatenates two empty name fields.
trytagging_add_address_info
Fires every time the customer completes their full address details. This event adds a top-level email field and an address object alongside the usual blocks.
trytagging_add_shipping_info
Fires every time the shipping method changes. The value now includes shipping costs, and ecommerce gains a shipping_tier field.
trytagging_add_payment_info
Fires every time the customer enters their payment details and clicks pay. Structurally identical to the shipping event, except ecommerce carries payment_type instead of shipping_tier.
Thank-you page
trytagging_purchase
Fires on the payment event from Shopify. This is the event to use for your conversion tags. ecommerce now contains transaction_id, tax and shipping, and user_data.customer_id is populated because the order has created a customer record.
A few things worth knowing
Values are placeholders. All URLs, identifiers, names, email addresses and addresses in the examples above are anonymised. The field names and structure are exactly what you will receive.
item_product_id changes format on purchase. On the checkout events it matches item_id. On trytagging_purchase it is a hash instead. If you map this field to a tag parameter, expect two different formats and pick the one your platform needs.
item_variant changes on purchase. On checkout events it repeats the product name; on the purchase event it comes from the Shopify variant title, which is Default Title for single-variant products.
Some parameters can come through empty. shipping_tier, payment_type, coupon and shipping are empty strings in these examples. If your GA4 reports show blank values for these, that is why. Set a fallback in your variables if you need a value.
device is not populated. Shopify's sandbox does not expose device information, hence "__not_supported": true.
Last updated
Was this helpful?

