Tracking & Analytics
Verifying tracking
How to confirm CBP events are firing into Google Tag Manager.
Verifying tracking
🛠 Dev
A quick checklist to confirm events are flowing from the store into GTM.
In the browser
- Open the live store and the browser dev tools console.
- Trigger an action (open the vehicle lookup, select a postcode, advance an installation step).
- Inspect
window.dataLayer— you should see a push whoseeventmatches the normalized name (e.g.cbp_drawer_open,cbp_postcode_select). See the data layer contract for expected shapes.
In GTM Preview
- Use GTM Preview/Debug (Tag Assistant) connected to the store.
- Because tracking runs inside Shopify's Web Pixel sandbox, confirm events appear as Custom Events in the Preview timeline.
- Check that your Custom Event triggers match the normalized
eventvalue (notsource_event_name). The catch-all regex is^cbp_.+.
This GTM instance runs inside Shopify's Web Pixel environment. Do not rely on GTM DOM triggers,
form listeners, or click listeners — they won't fire here. Use event-based tags triggered from the
dataLayer pushes.
Common gotchas
- No events at all — confirm the pixel is installed under Settings → Customer events with
the current
web-pixel.jscontents, and that the GTM container ID isGTM-T7Z4P3GQ. - Standard events but no
cbp_*events — the theme'sanalytics.jspublishes those; check the feature is actually present on the page and not erroring in the console. - Events in
dataLayerbut tags not firing — your GTM trigger name probably doesn't match the normalizedeventvalue.