Blog

Audit your tag manager in 30 minutes

A focused walk-through that surfaces stale tags, missing dedup, broken triggers, and the tags nobody owns.

Most tag manager containers accumulate tags faster than they retire them. A 30-minute audit, run quarterly, surfaces the obvious problems before they become reporting incidents. Here is what to look at and in what order.

Minute 0-5: stale tags

Open the Tags list. Sort by Last Edited. Anything older than a year is a candidate for removal. Open each one and ask: is this still being used? Most teams find at least three tags that fire for projects that ended quarters ago. Pause them (do not delete; pause first), publish, and remove for good in two weeks if no one complains.

Minute 5-10: tags with no owner

For each surviving tag, check the description field. If it is empty, you have a tag with no owner and no documentation. Add a line: who owns it, what report uses it, when it was last reviewed. Keeping this updated is most of the value of an audit.

Minute 10-15: duplicate firing

Look for tags that fire on the same trigger. The most common duplicates: GA4 page_view firing both client-side and server-side, Meta Pixel firing twice (once via your GTM, once via a hard-coded snippet in the page header). Each duplicate is a data quality bug waiting to be noticed.

Minute 15-20: missing dedup keys

For every event that fires both client-side and server-side, check that you have a shared event_id. If not, your reports are inflated by however many events make it through both paths. The fix is documented separately for Meta and TikTok.

Minute 20-25: broken triggers

Open Variables and check anything ending in "Click", "Form", or "Element." Variables that return empty values most of the time are usually pointing at DOM selectors that have changed since the variable was created. Click your way through the site in preview mode to confirm; fix or remove what is broken.

Minute 25-30: version cleanliness

Look at the Versions tab. Every version should have a name and description. If you see "Unnamed Version" entries, those are commits without context. Going forward, name every version. This becomes your audit trail when something goes wrong months later.

For server-side containers, run the same audit on the sGTM workspace. The principles are identical, the surface area is smaller. If you have not done one before, expect to find at least one tag that has been firing on every page for a year and feeding nothing.