Operations & Governance
Operations & Governance
Tag & GTM Health
Review your live GTM setup.
An on-demand setup audit of the live GTM container version. It checks configuration errors and duplicates inside GTM, not live event firing, site coverage or platform reconciliation.
Already a customer? Open Tag & GTM Health in your workspace
- On demand
- Runs on opening the page or pressing Refresh
- Live version
- Read-only configuration audit inside GTM
- No history
- Results are not saved as an audit history
- Review configuration before relying on your container.
- Identify possible duplicates within GTM.
- Re-run the audit after publishing your fixes in GTM.
Audit the published version
Connect GTM read-only and open Tag & GTM Health. The audit reads the live container version when you open the page or press Refresh. No audit history is saved.
- Read-only GTM connection
- Live published container version
- On demand, with no saved history
Find setup issues inside GTM
Review missing configuration, duplicate identifiers inside GTM, Google Ads Conversion Linker and Consent Mode signals. These are configuration findings, not measurements of what fired on your site.
- Duplicate GA4, Google Ads and Meta identifiers inside GTM
- Conversion Linker and Consent Mode signals
- No site-wide or platform reconciliation
Work findings by severity
Find Universal Analytics leftovers, paused tags, tags without firing triggers and generic naming. Each finding names affected tags and a recommended change.
- Universal Analytics leftovers
- Paused and untriggered tags
- Naming and unused-trigger hygiene
The shift
What changes once Tag & GTM Health is running
Same team, same accounts. The difference is that the decision is already measured before anyone opens a spreadsheet.
Before
- Container configuration is reviewed tag by tag in GTM.
- Duplicate identifiers are difficult to compare across tags.
- Legacy and untriggered tags clutter the live version.
With Hookology
- The live version is checked against setup rules on demand.
- Possible duplicates inside GTM appear with affected tag names.
- Severity and recommendations guide the next GTM review.
A setup audit checks the configuration, not whether every event reached its destination.
Inside the product
Tag & GTM Health - example findings
Example data, not a live container audit. Your findings come from the selected client's connected GTM container and its live version. This does not measure event firing, coverage or reconciliation.
- Review configuration before relying on your container.
- Identify possible duplicates within GTM.
- Re-run the audit after publishing your fixes in GTM.
Workspace / Tag & GTM Health
Tag & GTM Health
Northwind Apparel
Tag & GTM Health - example data
Illustrative findings from a live-version setup audit
Audit scope
GTM
Configuration only
Audit timing
On demand
Open page or Refresh
History
Not saved
Re-run after publishing
Review affected tags, publish your fixes in GTM, then press Refresh. No live firing or coverage is measured.
In practice
How Tag & GTM Health works week to week
From connecting your accounts to the review call, here is the shape of it, plus the questions teams ask us most before they start.
Step 1
Connect GTM read-only
Choose a connected container for the selected client in Data sources. Disconnected containers must be reconnected before auditing.
Step 2
Audit the live version
Open Tag & GTM Health or press Refresh to read the published container configuration. No history is saved.
Step 3
Review findings by severity
Read configuration, duplicate identifier, consent signal and hygiene findings, with affected tags and recommendations.
Step 4
Re-run after you publish
Make and publish your changes in GTM, then press Refresh to check the new live version.
Common questions
When you open the page with a connected container or press Refresh. There is no daily GTM audit job and no saved audit history.
No. It reads the live GTM configuration. It does not inspect traffic, measure coverage or compare events with ad platforms or back-end orders.
Duplicate identifiers inside GTM, including GA4 measurement IDs, Google Ads conversion identifiers and Meta Pixel IDs in Custom HTML and the recognised Meta gallery template. It does not inspect theme apps or hard-coded site pixels.
No. The connection is read-only. Your team makes and publishes changes in GTM, then re-runs the audit.
Why teams use it
- Review configuration before relying on your container.
- Identify possible duplicates within GTM.
- Re-run the audit after publishing your fixes in GTM.
How we set this up with you
Your team reviews the findings, changes and publishes the container in GTM, then re-runs the audit. Hookology does not edit your container or monitor it daily.
Our onboarding processWorks alongside
See Tag & GTM Health running on your own data
We build the workspace around your accounts and walk you through it together. No self-serve setup, no trial to configure on your own.
Book a discovery call