Audit a Google Tag Manager container
Read the published GTM container to list every tag, trigger, event and parameter, and find tags with no trigger, paused tags and pixels hard-coded outside GTM.
Most tools can tell you a page loads GTM. SiteAud!tLint reads what is inside it: the published container served as public gtm.js, with no Tag Manager login needed.
What the Inside GTM tab shows
For every tag in each container: what it sends to, the event name and parameters, what triggers it, and whether it is paused or has no trigger. Measurement IDs held in Constant variables are resolved to the real ID, and Custom HTML tags are scanned for pixels and events.
Common findings
| Finding | What to do |
|---|---|
| GTM container not published or wrong ID | Check the GTM-XXXX ID in the snippet and publish a version in Tag Manager. Until then no tag in the container fires. |
| GTM tag without a trigger | Add the intended trigger or delete the leftover tag, then publish. |
| Marketing tag hard-coded outside GTM | Move the pixel into GTM (most have a template) so consent and testing are controlled in one place. |
| More than one GTM container | Fine for agency plus in-house setups, but check both do not send the same GA4 ID or pixel events. |
| More than one GA4 property | Confirm each ID is intended, such as a roll-up property, and remove old or test properties. |
Tips
Use GTM's Preview mode alongside the audit to confirm a fix before publishing. After publishing, run a new audit: fixed issues move to Needs fixing / fixed as fixed since the last audit.
Applies to SiteAud!tLint 0.7.0 and later. Current version 0.7.1.