GA4 GTM Tags Not Firing: Trigger, Consent and Configuration Problems
When GA4 GTM tags are not firing, the tag never runs so no event reaches GA4. The cause is in the trigger, the consent configuration or the tag setup. Map the flow from the user action to the GA4 request to find where it stops, because a tag that does not fire has nothing to send.
Table of Contents
- 01.The GTM firing flow
- 02.What to check first
- 03.Container and published version
- 04.Triggers and exceptions
- 05.Consent and variables
- 06.Measurement configuration and the GA4 request
- 07.How to test it
The GTM firing flow
A GA4 tag in GTM follows a short path. A user action happens, a trigger evaluates whether to fire, the tag fires and sends a GA4 request, and GA4 receives it. If the tag is not firing, the break is at the trigger, the consent condition or the tag configuration. Each has a different fix, so find which one stops the flow.
| Cause | What happens | How to check |
|---|---|---|
| Trigger condition not met | Trigger never evaluates true | GTM preview, trigger conditions |
| Consent not given | Tag waits for consent | Consent state in preview |
| Tag paused or unpublished | Tag not in live container | Published version |
| Exception blocks it | Trigger exception active | Exceptions in preview |
| Variable resolves wrong | Condition uses bad value | Variable values in preview |
What to check first
- Open GTM preview and perform the action.
- Check whether the tag appears as fired, not fired or skipped.
- If not fired, check the trigger conditions.
- If skipped, check for exceptions or consent conditions.
- Confirm the published container version includes the tag.
Container and published version
The simplest cause is that the tag is not in the published container. Preview uses the draft, so a tag that works in preview may not be live. Confirm the published container version includes the tag and that no recent publish removed it. A tag that exists only in the draft never fires for real visitors.
Triggers and exceptions
A trigger decides when the tag fires. If the trigger condition is not met for the action, the tag does not fire. Check the trigger in preview and confirm the condition evaluates true for your action. Exceptions can also block a tag that would otherwise fire. Review any exceptions attached to the tag and confirm none apply to the action you are testing.
Consent and variables
Consent conditions can hold a tag back. If the tag waits for consent and consent is not given, it does not fire. Check the consent state in preview and whether the tag has a consent condition. Variables feed trigger conditions and tag configuration. A variable that resolves to an unexpected value can make a condition fail. Inspect the variable values in preview to confirm they resolve as expected.
Measurement configuration and the GA4 request
If the tag fires, confirm it sends the correct GA4 request. Check the measurement ID in the tag and the event name. A tag that fires with the wrong measurement ID sends to the wrong property. A tag that fires but sends a request that fails to reach GA4 is a different problem, covered in the guide on GA4 events not showing. Confirm the tag fires first, then confirm the request reaches GA4.
How to test it
- 1.Open GTM preview and perform the action.
- 2.Check whether the tag is fired, not fired or skipped.
- 3.If not fired, inspect the trigger conditions and exceptions.
- 4.If skipped, check the consent state and consent conditions.
- 5.Confirm the published container version includes the tag.
Frequently Asked Questions
Why does my GA4 tag show as not fired in GTM preview?
The trigger condition was not met for the action. Check the trigger conditions in preview and confirm they evaluate true for the action you performed. Also check for exceptions that block the tag.
Could consent stop my GA4 tag from firing?
Yes. If the tag has a consent condition and consent is not given, the tag is skipped. Check the consent state in preview and whether the tag waits for consent.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
GA4 Events Not Showing: What to Check Before Rebuilding Your Tracking
A missing GA4 event usually has a specific cause in the flow from user action to reporting. Diagnose the flow before you rebuild anything, because most missing events come from a single point of failure.
GA4 Tracking Works on Some Pages but Not Others: How to Find Coverage Gaps
Coverage gaps come from page templates, landing pages, subdomains and single-page routes that the tag setup does not cover. Audit every page type and confirm the pageview tag fires on each.
GA4 Sessions Dropped After a Tracking Change: What to Check
Separate actual traffic decline from measurement decline before you fix anything. A real decline is a marketing problem. A measurement decline is a tracking problem. Check other data sources to tell them apart.