TagEasy
Back home
Browser extension

TagEasy Inspector

A Chrome extension that overlays every dataLayer push happening on the current page, and — when you paste your org's API key — annotates each push with the TagEasy tags that would fire on it. Built for the moment your QA workflow needs to answer “did purchase fire, and which tags did it trigger?”

Not on the Chrome Web Store yet

The developer-mode install below is the only way to get the Inspector today, and it is the same v0.2.0 package we intend to list. We'll announce the store listing on the changelog when it happens — no date promised until it is actually submitted.

Follow the changelog

Install today — Developer Mode

Three minutes. This is the same package we intend to list on the Web Store — you just load it from a zip instead of clicking “Add to Chrome.” Works on any Chromium browser (Chrome, Edge, Brave, Arc).

Download v0.2.0

24 KB · built May 25, 2026

  1. 1

    Unzip the file

    Most browsers will offer to unzip on download. If not, double-click the file to expand it into a tageasy-inspector folder.
  2. 2

    Open chrome://extensions

    Paste chrome://extensions in the address bar. On Edge it's edge://extensions, on Brave it's brave://extensions.
  3. 3

    Turn on Developer mode

    Toggle the “Developer mode” switch in the top-right corner of the extensions page. New buttons appear.
  4. 4

    Click "Load unpacked"

    Click the new Load unpacked button and select the unzippedtageasy-inspector folder. The extension shows up in your toolbar.
  5. 5

    Paste your API key (optional but recommended)

    Open Inspector in TagEasy's sidebar, generate or copy the key, click the extension's toolbar icon, and paste. Without a key it still shows raw dataLayer pushes; with one it also tells you which of your configured tags would fire on each push.
    Open Inspector settings

What it shows

  • Every dataLayer.push in real time, with the full payload
  • Which configured TagEasy tags would fire on each push (with API key)
  • Highlights tags that are blocked by a firing condition / A/B variant
  • Side-by-side: what GTM thinks vs. what you configured

Privacy

  • Reads dataLayer only on the page you have open
  • API key is stored locally in the extension; never sent to a third party
  • The TagEasy server is the only network call — for the tag-match lookup
  • Source is on GitHub