pualien / trackie

A Chrome extension to enhance debugging of some frequently-used tag management platforms (Google Tag Manager, Tealium, Commanders Act, DTM) in combination with some frequently-used tags (Google Analytics, Google Analytics 4, GA Audiences, Ddm, Criteo, Adobe Analytics/Omniture, Floodlight, Comscore, Facebook, Bluekai, Youbora, Kinesis, Webtrekk, Segment)

Trackie

Debug and test tag manager and analytics implementations. Trackie 🐞 is a Chrome extension to enhance debugging 👨🏼‍💻 of some frequently-used tag management platforms 🌩:

• Google Tag Manager
• Tealium
• Commanders Act
• DTM

In addition Trackie intercepts ⚡️ a lot of most-used tag calls (page view, clicks, checkout...) 🕵🏻‍♂‍from:

• Google Analytics
• 💎 Google Analytics 4 property (GA4), formerly known as "App + Web" property
• GA Audiences
• Adobe Analytics/Omniture
• Floodlight
• Comscore
• Criteo
• Facebook
• Bluekai
• Youbora
• Kinesis
• Webtrekk
• Nielsen
• 💎 Segment track + identify

Tag calls can now be exported in csv 💾 in order to better view data collected offline!

Installation

To use the unpacked source version, enable Developer mode in the Chrome extensions page and Load unpacked extension from the checked-out src folder.

The latest official version is on the Chrome Web Store.

Use

A new panel will appear in Developer Tools titled Trackie, containing a page group and URL for each pageload in the tab, with each push to the dataLayer variable (in the case of GTM's array-based data layer) appearing in a subgroup.

1. Current URL / TMS logo (or X if no TMS found); click to collapse/expand this page
2. TMS container ID; becomes a dropdown menu if multiple containers are present
3. Data layer items; items with a + are objects containing sub-items and can be expanded one level by clicking + or expanded fully by shift-clicking +
4. Information on fired tags (GA, Floodlight, SiteCatalyst); click + here to see all parameters in the request
5. Trackie settings and information
6. Clear history

All items are in reverse chronological order (newest on top).

Note that vertical alignment between the data layer and any fired tags does not necessarily indicate a tie between the two. If a page contains only a data layer, or only tags, that side of the panel will expand to take up the width of the entire panel.

Settings

General

• show data layer presence: enable (default) or disable the TMS logo / X in each page group. Useful for disabling if you are using Trackie for e.g. pure GA debugging rather than tag management debugging.
• auto-collapse nested data layer variables: when this option is enabled (default), nested variables such as Google Analytics enhanced ecommerce will automatically be collapsed to save space.
• block tags from firing: requires use of the Chrome dev or beta channels. When this option is enabled, supported tags will be blocked from actually sending to the analytics platform. Note that blocking does not take the Tags selections into account (i.e. all supported tags are blocked, regardless of whether or not they are shown).

Tags

All supported tag types are shown by default; these can be individually disabled.

Ignored IDs

To filter out tags hitting specific analytics properties, enter the property IDs here.

Bug report - feature request

Feel free to open new issues following the issue templates

Misc

Trackie was built with and thanks to the following:

• DataSlayer
• Google Data Layer Helper Library
• Pure
• jQuery
• leanModal
• Open Sans
• Massimo Artizzu's O.o polyfill

Trackie is under the MIT License. See LICENSE.md.

trackie's Issues

Spacchettare i parametri all'interno delle URL

Sarebbe utile spacchettare i parametri all'interno delle URL (almeno dei principali Player come Facebook e Criteo) in modo da poter leggere la valorizzazione dei tag in modo più agile

Quindi, invece di vedere (metto una URL di esempio, non corrisponde al vero url della chiamata):

facebook.com?PRODUCTS:1=codice_prodotto,2=codice_prodotto,3=codice_prodotto&PRICES:1=price,2=price,3=price
PRODUCTS:1=codice_prodotto,2=codice_prodotto,3=codice_prodotto
PRICES:1=price,2=price,3=price

avere:
facebook.com?PRODUCTS:1=codice_prodotto,2=codice_prodotto,3=codice_prodotto&PRICES:1=price,2=price,3=price
P1_cod=codice_prodotto
P1_price=price
P2_cod=codice_prodotto
P2_price=price
P3_cod=codice_prodotto
P3_price=price

un po' come avviene per le custom dimension di GA, sia a livello di Hit/Sessione che a livello di Prodotto (Enhanced E-Commerce)