DSDillon
Analytics / Questions / Tagging and Pixels
Tagging and Pixels

GTM preview not working

A direct answer to GTM preview not working, including the measurements to check, the setup required, common mistakes and the next action to take.

TroubleshootingUpdated 24 September 2026
Direct answer

Check container identity, published or workspace state, browser restrictions, consent tools, CSP and whether the site loads the intended GTM container before editing triggers. Check tag firing status, trigger conditions, event parameters. Keep traffic, leads and revenue separate so one number does not hide a weak customer journey.

What matters

What you need to know

Use one known journey and find the exact point where expected evidence disappears, duplicates or changes. Repair that layer, retest it, then move outward only if the problem remains.

For this issue, check tag firing status, trigger conditions, event parameters.

Google Tag ManagerGTMMeta PixelFacebook PixelGoogle tagserver side taggingConsent Mode
Evidence

What to measure

Use the smallest group of metrics that can answer the question. A larger report is not automatically a better report.

01 Tag firing status

Check this against the same date range, traffic segment and business definition used elsewhere in the analysis.

02 Trigger conditions

Check this against the same date range, traffic segment and business definition used elsewhere in the analysis.

03 Event parameters

Check this against the same date range, traffic segment and business definition used elsewhere in the analysis.

04 Duplicate requests

Check this against the same date range, traffic segment and business definition used elsewhere in the analysis.

05 Consent state

Check this against the same date range, traffic segment and business definition used elsewhere in the analysis.

06 Destination receipt

Check this against the same date range, traffic segment and business definition used elsewhere in the analysis.

Implementation

How to build or diagnose it

Follow the evidence in order. Changing several tracking layers at the same time makes it harder to prove which change fixed the problem.

  1. Inventory every existing tag before adding another
  2. Use one controlled deployment path
  3. Name triggers and variables so another person can audit them
  4. Test consent states, mobile behaviour and duplicate firing before publication
Failure patterns

What commonly goes wrong

These are recurring causes of misleading analytics, broken attribution and wasted implementation work.

Publishing duplicate tags

Verify the underlying evidence before changing the reporting layer or drawing a commercial conclusion.

Using broad click triggers that fire on unrelated elements

Verify the underlying evidence before changing the reporting layer or drawing a commercial conclusion.

Sending personal data in URLs or event parameters

Verify the underlying evidence before changing the reporting layer or drawing a commercial conclusion.

Making consent dependent tags fire before the consent state is known

Verify the underlying evidence before changing the reporting layer or drawing a commercial conclusion.

Decision sequence

How to read the result

Keep observation, interpretation and commercial action separate. That reduces false certainty and makes the next decision easier to defend.

Observed

A tag firing in the browser does not prove the destination accepted the event

Interpret

Debugging needs browser evidence and destination evidence

Act

Clean naming and version control reduce future tracking failures

Questions

Frequently asked questions

Short answers to the next questions that usually follow this search.

What should I collect before changing anything?

Keep one affected journey, timestamps, event or network evidence, account and property identifiers, and the expected business result. That usually narrows the failure faster than changing several settings at once.

Which measurements matter for GTM preview not working?

Tag firing status, Trigger conditions, Event parameters, Duplicate requests. Choose the smallest set that answers the business question.

Can analytics prove every customer action?

No. Browser restrictions, consent choices, cross device behaviour, offline conversations and missing identifiers create gaps. A reliable report shows what is observed, what is inferred and what remains unknown.

When is specialist help useful?

Bring in help when the numbers cannot be reconciled with known business outcomes, several platforms report different results, advertising depends on the data, or the setup has become difficult to audit safely.

Platform guides

Check the platform settings

Use the vendor guides below when checking the settings discussed on this page.

Need the measurement fixed, built or verified?

DSDillon can audit the current setup, repair conversion evidence and connect website activity to leads and commercial outcomes.

Related DSDillon resources

Keep working through the issue

Related guides and services that can help you continue the diagnosis.

Marketing Attribution CompanyMarketing Source DefinitionMarketing Attribution ConsultingHow Do You Know Where A Lead Came FromMarketing Attribution ConsultantMarketing Attribution Agency
Related guidance

Explore more about Gtm Preview Not Working

Conversion evidence, lead tracking and commercially useful reporting.

DSDillon brandmark
KEEP DSDILLON CLOSE

DSDillon, one tap away.

Add DSDillon to your home screen for direct access to services, properties and your client workspace.

YOUR DSDILLON APP

Add DSDillon to your device.

On your computer

In Chrome or Edge, use the install icon near the address bar or the browser menu to install DSDillon. On a supported Mac, Safari offers File → Add to Dock.

On your phone, open this site in Chrome on Android or use Safari's Share menu on iPhone.

Live information, forms, payments and account access require an internet connection. Your existing login and permissions still apply.

About the DSDillon app
Business Intelligence
Find the next useful answer or diagnostic.