Meta tracking is configured separately. See Meta Pixel and Conversions API.
What’s Tracked
storekit pushes standard e-commerce events to the GTM data layer:Setup
Google Tag Manager is configured separately for each store.- Go to Stores → your store → Settings → Integrations → Google Tag Manager
- Enter your Google Tag Manager ID (format:
GTM-XXXXXXX) and click Save
Use Cases
Google Tag Manager
GTM acts as a container for all your tracking tags. Once your GTM Container ID is added to storekit, you can manage all tags, triggers, and variables from the GTM dashboard without editing your store settings.Verifying Your Setup
After adding your GTM Container ID:- Install the GTM Preview browser extension
- Open your store in preview mode
- Verify that tags fire on page views, add to cart, and purchase events
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.