Why isn’t my Google Tag Manager tracking any events?

When Google Tag Manager tracks no events, the cause is almost always one of four things: the container is not loaded or not published, the trigger does not match what actually happens on the page, the expected dataLayer event is never pushed, or consent settings stop the tags from firing. Preview mode in Tag Manager shows within minutes which of these applies, because it lists every event and every tag that fired or did not fire.

One distinction helps from the start: a tag that does not fire is a Tag Manager problem. A tag that fires but whose data never shows up in GA4 or Google Ads is usually a problem with the tag configuration, the measurement ID or the receiving account.

Why does Tag Manager not track my events?

• Container missing or not published. The container snippet is not on every page, it sits on a different container ID, or your changes are only saved in the workspace and were never published. Preview mode then shows your new tags, but visitors still get the old version.
• Trigger does not match. A click trigger waits for a CSS selector or element ID that does not exist on the page, a form trigger listens for a submit that the form never sends because it uses JavaScript, or a condition compares against the wrong variable.
• dataLayer event never pushed or named differently. A custom event trigger only fires when the website runs dataLayer.push with exactly the same event name. Event names are case-sensitive, so addToCart and add_to_cart are two different events.
• Consent blocks the tags. With consent mode or a consent banner, tags can wait for consent or be blocked by additional consent checks. Without consent, an event may simply not be sent, which looks like “GTM does not track” in testing.
• Browser or blocker. Ad blockers and privacy settings can block Tag Manager or individual requests. Always test in a clean browser profile without extensions.

How do I find the cause in Preview mode?

1. Start Preview mode in Tag Manager and open your website in the connected Tag Assistant window. If the connection fails, check first whether the container snippet with the right ID is on the page.
2. Trigger the action you want to measure, for example the form submit or the click on the button.
3. Find the event in the left-hand list. If no event appears for your action, the trigger has nothing to react to. Then the website has to push a dataLayer event, or you need a different trigger type.
4. Open the tag under Tags Not Fired and check which trigger condition failed. Preview mode marks the condition that was not met.
5. Check the Data Layer and Variables tabs for that event. There you see the event name and the values that were really passed, for example item ID or price.
6. Check consent. Look at the consent state for the event and test once with consent accepted and once declined.

How should the data layer and triggers be set up?

• One event per action. The website pushes a clearly named event for each important action, for example generate_lead or add_to_cart, and a custom event trigger listens for exactly that name.
• Consistent names. Use the same spelling in the website code, in the trigger and, for GA4, ideally the recommended event names from Google’s documentation.
• Data Layer Variables with the exact path. If the value sits in ecommerce.items, the variable must read exactly that path. Otherwise the tag fires but sends empty values.
• Clear naming in the container. A fixed scheme for tags, triggers and variables makes later debugging much faster.

If the container stops working after a new consent banner was installed, the article Why does my GTM container stop working after the consent update? covers that case in detail.

Test every event in Preview mode before publishing, rely on dataLayer events instead of generic click triggers for important actions, and always test with and without consent.

Sources

• Tag Manager Help: Preview and debug containers
• Tag Manager Help: About triggers
• Google for Developers: The data layer
• Google for Developers: Set up consent mode on websites

Want every important action measured reliably, with consent? We check your container, data layer and triggers and test each event before it goes live. Book a free intro call or read more about our tracking services.