Google tag manager errors mistakes solutions

In this guide

The six usual suspects Data layer mistakes Consent mistakes Server container mistakes A debugging routine A worked example Terms you will see Habits that prevent most errors Frequently asked questions

Check these first

Start in Preview: did the event arrive, did the trigger match, did the tag fire?
Most problems are a trigger that does not match, a data layer value that is missing or a container that was not published.
Change one thing at a time and test again.

Tag Manager errors are rarely mysterious. The container has a fixed order of work, and each step either happens or does not. This page lists the common failures, the symptom each one shows in Preview, and the fix. It covers web containers first and server containers at the end. If you only use a server container, jump to clients, tags, triggers and variables.

The six usual suspects

SymptomThe tag does not fire

Likely causeThe trigger conditions do not match, or the trigger is attached to the wrong tag.

FixIn Preview, click the event and read the "Tags Not Fired" list and the trigger conditions. Fix the condition or the attachment.

SymptomThe tag fires twice

Likely causeTwo triggers, or the same tag in two containers, or the page loads the container twice.

FixSearch the page source for the container ID. Remove the duplicate.

SymptomA variable is undefined

Likely causeThe data layer value is pushed after the tag runs, or its name is wrong.

FixCheck the data layer tab in Preview. Push the value before the event that needs it.

SymptomChanges are not live

Likely causeYou edited the workspace but did not publish.

FixPress Submit and Publish. Check the live version number.

SymptomPreview shows nothing

Likely causePreview mode blocked by an ad blocker, a cookie banner, or the container is not on the page.

FixOpen the page without blockers and confirm the container snippet is in the source.

SymptomTags fire on the wrong pages

Likely causeA trigger has no page condition and fires on "All Pages".

FixAdd a page URL or event condition.

Set up in minutes

Connected in minutes

Add your domain, install the pixel, connect your ad platforms and watch the first events land.

Data layer mistakes

Pushing an event name with different case than the trigger (Purchase vs purchase).
Pushing a value as text where the tag expects a number.
Overwriting the data layer array instead of pushing to it.
Pushing ecommerce data without clearing the previous object, so old items appear.

Tags fire before the banner has stored a choice.
Consent Mode default is set after the container loads.
A tag has no consent setting, so it ignores the visitor's choice. See Consent Mode v2.

Try it

Works with your stack

Grab a logo and throw it. These are the tools Open Tracked already talks to.

Grab one. Throw it.

Server container mistakes

SymptomNo requests arrive

Likely causeThe web tag does not send to the server container URL.

FixSet the server container URL in the GA4 configuration. See server container not receiving requests.

SymptomTag status failed

Likely causeThe vendor rejected the request.

FixOpen the tag in Preview and read the response. See tag status failed.

SymptomTag status still running

Likely causeThe request is waiting for a response.

FixSee tag status still running.

A debugging routine

Start Preview and reproduce the problem.
Pick the event in the left list.
Read Tags Fired and Tags Not Fired.
Open the tag and the trigger to see the conditions and values.
Check the data layer tab for the values.
Fix one thing, refresh Preview and test again.

0 of 6 done

The container ID appears once on the pageTriggers have clear conditionsData layer values arrive before the tag needs themConsent settings are on each tagI published after the last changeI tested in a private window

For a full review of an existing container, see Google Tag Manager audit and GTM best practices.

A worked example

A GA4 purchase tag does not fire on the thank-you page. Preview shows the event purchase in the left list, but the tag is under Tags Not Fired. Opening the trigger shows it waits for the event Purchase with a capital P, while the data layer pushes purchase. Matching the case fixes it in one minute. Most debugging stories look like this: the answer is in the list of conditions, not in the code.

Terms you will see

Data layer: A list of values your site pushes for the container to read.
Trigger: The rule that says when a tag may fire.
Preview: Tag Manager's debug mode that shows what happened on a page.
Workspace: Your draft changes before you publish.
Version: A published snapshot of the container.

Habits that prevent most errors

Name tags, triggers and variables in a consistent way, such as GA4 - purchase.
Write a short note on every version you publish.
Test in Preview before every publish.
Keep one container per site and delete old ones. See deleting a container.
Review the container twice a year. See Google Tag Manager audit.

Works worldwide

Runs on your domain, anywhere

Your tracking runs on your own domain, so a visit from any country is handled the same way.

Frequently asked questions

Why is my Google Tag Manager tag not firing?

The trigger does not match, the tag is not attached to the trigger, or the container is not published. Use Preview and read Tags Not Fired.

Why do I see duplicate events?

Two containers, two triggers, or a tag that fires on every history change. Search the page for duplicates.

How do I know if a change is live?

The container version on the Admin page and in Preview shows the published version.

Why do variables show undefined?

The data layer value does not exist yet or has a different name. Check it in the data layer tab.

Can I debug a server container the same way?

Yes. Server Preview shows the incoming request, the client that claimed it, the event data and each tag's outgoing request.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start free More in Troubleshooting →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...