Skip to main content
Add your Google Tag Manager (GTM) container to a store, and storekit loads it on every page of that store and pushes ecommerce events to its data layer. You then choose in GTM where those events go: Google Analytics 4, Google Ads, Hotjar or any other tag.
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.
  1. Go to Stores → your store → Settings → Integrations → Google Tag Manager
  2. Enter your Google Tag Manager ID (format: GTM-XXXXXXX) and click Save
Repeat for each store you want tracked. The container also loads when your store is opened inside your storekit app, because the app shows the same ordering pages.

Brand Store Selection Page

Add a container to track your brand’s store selection page, both at order.storekit.com/stores/<brand-slug> and on your brand’s custom-domain landing page.
  1. Go to Settings → Brands and select your brand.
  2. Click Open Brand Designer, then open General.
  3. Enter your Google Tag Manager ID and click Publish changes.
Repeat for each brand. This setting only covers the store selection page. When a customer opens a store from the list, that store’s own container loads instead.
Use the same container for your brand and every store unless you need separate tag setups. Configure both the brand and each store; neither setting fills in the other.

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.
  • value is what the customer paid for the order, in pounds (or your store’s currency), after discounts.
  • Each item’s price includes its paid modifiers, so a £8.75 Teriyaki Steak with Add Salmon (£4.35) goes out at £13.10.
  • item_category is the product’s category. category carries the same value for older tags.
The full payload of every event is in Event Tracking.

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.
Use GTM’s Preview mode to check your tags before relying on them for reporting or campaigns. See Google’s Preview and debug containers.

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.
Expanded gives each product in an order its own row, so an order id repeats once per product. Compact summarises each order in a single row and omits the product columns; both formats include Order id and Order Code, so pick Compact if you only need order totals.
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.
storekit sets the Google consent mode defaults to granted for every category before your container loads.