TagEasy

Tag inventory

The tag inventory scans your homepage HTML, identifies every tracking vendor loading on it (GA4, Meta, TikTok, Hotjar, Segment, Mixpanel, Klaviyo, Pinterest, LinkedIn — about 25 vendors in v1), and cross-references each one with your GTM container.

Three buckets to know about

  • Managed — loaded on the page andpresent in your GTM container. The healthy default.
  • Unmanaged (shadow tags) — loaded on the page but not in your GTM container. Usually means a developer added a script tag directly outside the official tagging process. Common pre-existing leftovers from before GTM rollout; sometimes intentional, sometimes drift.
  • Unused — present in your GTM container butnot loading on the page. Could be a dead tag whose trigger no longer fires, or a tag scoped to a different page. Worth checking — unused tags are a Consent Mode v2 risk (configured but never validated).

What the v1 scan looks at

TagEasy fetches your homepage HTML server-side and parses it for:

  • <script src> — direct vendor library loads (GA4, Meta SDK, Hotjar, etc.).
  • <img src> — tracking pixels (the classic fallback inside <noscript> blocks).
  • <iframe src> — iframe-based trackers.
  • Inline scripts — function calls like fbq('init'), gtag('config'), ttq.track(), etc.

What v1 doesn't catch (yet)

TagEasy v1 only inspects the HTML the server returns. Tags that are injected dynamically after the page loads — typically via JavaScript inside another tag — won't appear in the inventory. v2 will add headless-browser execution (Playwright) to catch those. For now, treat the inventory as a strong signal but not a complete catalog.

Cross-referencing your GTM container

TagEasy fetches your live GTM container via the Tag Manager API (the same connection that powers the health monitoring) to know which tags you manage. When the live API isn't available, it falls back to the GTM container TagEasy generated and persisted during setup.

v1 recognizes GTM tag-types like gaawc (GA4 Config) and awct (Google Ads conversion). Vendors loaded via Custom HTML GTM tags are NOT mapped in v1 — they may appear as "unmanaged" even though they're technically inside your container. Custom-HTML vendor matching is on the roadmap.

Plan

Tag inventory is a Pro-tier feature. See pricing or, for the broader monitoring picture, health monitoring and tracking plan.