Meta tracking is configured separately. See Meta Pixel and Conversions API. To send these events to Google Analytics, see Google Analytics 4.
Setup
Configure Google Tag Manager separately for each store and, if you have one, your brand’s store selection page.- Go to Stores → your store → Settings → Integrations → Google Tag Manager
- Enter your Google Tag Manager ID (format:
GTM-XXXXXXX) and click Save
Brand Store Selection Page
Add a container to track your brand’s store selection page, both atorder.storekit.com/stores/<brand-slug> and on your brand’s custom-domain landing page.
- Go to Settings → Brands and select your brand.
- Click Open Brand Designer, then open General.
- Enter your Google Tag Manager ID and click Publish changes.
What’s Sent to the Data Layer
That list is fixed. Page views are not pushed as a separate event: your Google tag records them itself when the page loads.
The four ecommerce events follow Google’s GA4 ecommerce format: the event data sits under
ecommerce, and storekit pushes { ecommerce: null } first so items from the previous event are never carried over. The same fields are also sent at the top level of the event, so containers built on them before keep working. Each action is still one event, so nothing is counted twice.
valueis what the customer paid for the order, in pounds (or your store’s currency), after discounts.- Each item’s
priceincludes its paid modifiers, so a £8.75 Teriyaki Steak with Add Salmon (£4.35) goes out at £13.10. item_categoryis the product’s category.categorycarries the same value for older tags.
Telling App Orders From Website Orders
Before your container loads, storekit pushes the channel the customer is ordering through:
It has no event name, so it does nothing in GTM until a tag reads it. To report on it in Google Analytics, follow Split app and website orders.
Verifying Your Setup
1
Open Tag Assistant
In GTM, click Preview on your container, or go to tagassistant.google.com, and enter your store’s URL.
2
Walk through an order
Open a product, add it to your basket and start checkout. Each action should show as an event in Tag Assistant with your tags fired under it.
3
Check the event data
Click an event, then Data Layer, and check the
ecommerce values and order_channel are what you expect.Reconciling with Google Analytics
The purchase event storekit pushes to the GTM data layer carries two order identifiers:
So a transaction ID in Google Analytics is the order id. Open that order by putting the value at the end of the order page URL (
/orders/KhDx6jUFP) — searching for it in All Orders returns nothing, because that search box matches order codes only.
To match a batch of Google Analytics transactions against your orders:
1
Open All Orders
In the sidebar, click Orders, then All Orders, and set the date range and filters you want to export.
2
Export the orders
Click Export, then choose Expanded. storekit emails the CSV to the address you are signed in with.
3
Match on Order id
Match the Google Analytics transaction ID against the CSV’s Order id column; the Order Code column next to it gives the code your team uses for the same order.
The ID column in Analytics → Accounting → All Transactions is the payment provider’s reference for the charge, not the Google Analytics transaction ID. That report’s CSV export does contain the order id, in its Reference ID column — see Order and payment identifiers.