Question 1

How was your GTM container originally set up?

Accepted Answer

GTM containers set up professionally with documented structure score highest. Containers that were copied from templates, inherited without documentation, or set up ad-hoc are more likely to have issues like duplicate tags, missing triggers, and bloated configurations.

Question 2

When should you audit your GTM container?

Accepted Answer

GTM containers should be audited at least every 3 months. Containers that haven't been audited in over a year typically have paused tags, broken triggers, and outdated conversion tracking that silently degrades data quality.

Question 3

How do you detect duplicate tags in GTM?

Accepted Answer

Duplicate tags fire the same tracking pixel multiple times per event, inflating conversion counts and page view data. Use GTM Preview mode or Tag Assistant to check if the same tag fires more than once on a single page load or event.

Question 4

What is a data layer and why does it matter for GTM?

Accepted Answer

A data layer is a structured JavaScript object that passes information from your website to GTM. Without a properly documented data layer, tracking breaks when developers ship code changes because GTM variables rely on DOM elements that may move or disappear.

Question 5

How do you check if GTM respects cookie consent settings?

Accepted Answer

Google Consent Mode v2 must be configured so GTM reads consent signals from your cookie banner. Many sites have a consent banner that changes nothing — tags fire regardless of user choice. Verify by checking if analytics and ad tags fire before consent is granted.

Question 6

What is PII leaking in GTM and why is it a compliance risk?

Accepted Answer

PII (personally identifiable information) like email addresses, phone numbers, or names can leak into GTM tags through form fields, URL parameters, or data layer pushes. This data gets sent to Google Analytics, ad platforms, and other third parties — potentially violating GDPR, CCPA, and platform terms of service.

Question 7

Who should have publish access to a GTM container?

Accepted Answer

GTM publish access should be limited to 1-2 people with a clear review process. Unrestricted publish access is a common source of tracking issues — someone publishes a change without testing, breaking conversion tracking or firing tags on the wrong pages.

Is your Google Tag Manager costing you money?

The problem nobody talks about

Marketing blames dev

Data you can't trust

Compliance risk

Container bloat

GTM Health Scorecard

1 How was your GTM container originally set up?

2 When did someone last audit your GTM container?

3 Do you have paused or unused tags sitting in your container?

4 How confident are you that tags aren't firing more than once per event?

5 Are your key conversion events tracked on every relevant page?

6 Is your GA4 data consistent with what your ad platforms report?

7 Do you use a data layer to pass information to GTM?

8 When your dev team ships changes, does tracking break?

9 Does your GTM container respect your cookie consent settings?

10 Have you checked whether PII is being passed into GTM tags?

11 Who has publish access to your GTM container?

12 When a tag goes live, how is it tested?

—

Your GTM setup needs immediate attention

You're close — a few fixes could make a big difference

Nice work — your GTM setup is in good shape

How I work

Free scorecard or Loom audit

Full audit report $297–$497

Done-for-you setup $800–$1,500

Monthly retainer $300–$500/mo

Why me