# Google Tag Manager preview mode: fix a tag that does not fire on Mac

> Google Tag Manager preview mode shows which tags fire and which stay silent. Use these steps on Mac in Chrome to find the cause.

URL: https://www.lazur.app/for/marketers/problems/gtm-preview-mode-tag-not-firing
Updated: 2026-11-08

Google Tag Manager preview mode runs your workspace draft on your site, so you can see which tags fire and which stay silent. If a tag does not fire, check its trigger, the published version, and your browser before you change the tag again. The steps below use Google's free tools, Chrome, and built-in Mac shortcuts.

## Quick answer

- Open the Workspace tab, click Preview, enter your URL, click Connect, then click Continue in the Tag Assistant tab.
- Preview shows the draft. Visitors get the last published version, so a tag can work in Preview and still fail live.
- Ad blockers, privacy extensions, and consent settings can each stop a tag from firing for you or your visitors.
- Confirm the event in GA4 DebugView. In Chrome on Mac, press ⌘⌥J and read the Network tab to see whether the request leaves the browser.
- Lazur can point at the Preview button, explain a message on screen, and draft your bug note. It does not click for you.

## What a tag that does not fire in google tag manager costs you

- **Salary time spent guessing.** BLS puts the median hourly wage for advertising, promotions and marketing managers at $79.70 in May 2025. That is a salary rate, not a bill. Use it to price your own hours. An afternoon lost to a silent tag is paid time that does not go to campaign work. BLS also says this work may be stressful, particularly near deadlines.
- **Data that drifts without a warning.** A 2019 Forrester study, commissioned by Marketing Evolution, found 21 cents of every media dollar was wasted from poor data quality. It also found 26% of campaigns were hurt by poor data quality. These are vendor-commissioned numbers from 2019, so read them as a direction, not a forecast. A tag that fires on some pages and not others is a data quality problem.
- **Conversions the models cannot see.** When consent holds back the Google tag, Google says modeled conversions become less accurate. A silent conversion tag can make a campaign look weaker than it is. That shifts bids and budget decisions, and the cost lands there, not in the tag settings.
- **Visitors your tags never reach.** GWI data, as cited by Backlinko, shows 29.5% of internet users use ad blockers at least sometimes as of Q2 2025. Tags do not run for those visitors. Your reports will show a gap that looks like a tag bug but may be the browser.

## Why it happens

1. **The trigger never matches the event.** The tag waits for a trigger, and the trigger waits for an event. If the event name, the page filter, or the trigger type is off, the tag never runs. Blocking triggers add a trap of their own. Analytics Mania says a blocking trigger can only block a firing trigger of the same event type, so an exception on a different trigger type can fail without any warning.
2. **Tag settings hold it back.** A tag can be set to fire once per page, which stops repeat firing on the same page. A firing schedule can block a tag outside the hours you set. A paused tag never fires until someone unpauses it and publishes the container. Check all three before you suspect anything bigger.
3. **The container was never published.** Preview runs your workspace draft. Visitors get the last published version. If you changed a tag and did not publish, the live site runs the old setup. Analytics Mania also lists a setting called Only fire in published containers, which stops tags from firing in Preview at all.
4. **The dataLayer snippet sits in the wrong place.** The dataLayer snippet must load before the GTM container snippet. If it sits below the container, it can overwrite the layer, so no new events fire after the first one. A developer can check the snippet order in the page source in a few minutes.
5. **Ad blockers, privacy tools, and extensions.** Ad blockers and privacy extensions can stop a tag from loading or sending. Analytics Mania also names Brave Shields and Cloudflare Rocket Loader as sources of trouble. The GA Debugger extension can make GA4 look wrong without stopping the tag, which hides the real picture.
6. **Consent settings hold the tag back.** If the Google tag only loads after a visitor agrees, the tag waits. Google says that makes modeled conversions less accurate. A Could not connect message in Tag Assistant can also mean your container is blocked from loading, so check that message before you blame a single tag.
7. **The page code blocks the script.** A Content Security Policy, a firewall, or a proxy can block the tag script before it runs. Google's troubleshooting guide lists these checks. Google also says to turn off the debug signal in the URL if it breaks the page. Confirm that the Google tag is on the page at all, because a missing tag cannot fire.

## How to fix it

- **Run Preview the right way.** Open the Workspace tab, click Preview, enter the full URL including https://, and click Connect. Wait for the Tag Assistant tab, then click Continue in that tab. Browse the page in a second tab. Use the exact URL of the page where the tag should fire, not a shortcut to it.
- **Read the trigger and the tag settings.** Open the silent tag and read every trigger attached to it. Compare the event name with what the page actually sends. Check the paused status, the once per page setting, and any firing schedule. Change one setting, save, and retest in Preview so you know what worked.
- **Confirm the Google tag is on the page.** Open the Tag Assistant side panel in Chrome and check the list of Google tags on the page. If the Google tag is missing, the container cannot load, and no tag will fire. Google's troubleshooting steps say to confirm this first.
- **Clean up the browser for the test.** Disable ad blockers and privacy extensions for the test. Allow the Tag Assistant extension to read and change site data. Analytics Mania also suggests disabling Brave Shields and Cloudflare Rocket Loader, then fully quitting and relaunching the browser. Remove the Tag Assistant extension only if it conflicts with the test.
- **Check GA4 in DebugView, then clean up.** Turn on debug mode for your own device through Tag Assistant or GTM Preview. Trigger the event once. Open DebugView and find the event in the Seconds stream. When you finish, remove the debug_mode parameter from the tag, because setting it to false does not turn debug mode off.
- **Check the request in DevTools.** In Chrome, press ⌘⌥J, open the Network tab, and reload the page. Filter for the request your tag sends. For blocked requests, press ⌘⇧P, type block, and choose Show Request Blocking. Blocked requests show in red, which means the browser stopped the call before it could finish.
- **Publish, then test the live page.** Publish the container, then load the live page in a clean profile. Check Tag Assistant or DebugView again. Google says a tag that works in Preview can still fail live, so this step is not optional. Log the result with the date and the tag name.

A tag that does not fire is one of the most common problems in Google Tag Manager. You set up a button click or a purchase event, publish, and nothing shows up in your reports. Preview mode is the fastest way to find out why. It shows what GTM sees on a page before the change goes live.

![A marketer at a laptop checking a tracking setup before a Google Tag Manager preview mode test](https://images.lazur.app/content-images/problem/gtm-preview-mode-tag-not-firing/google-tag-manager-preview-mode-1-c892f0.jpg)

## What Preview mode shows, and what it does not

Google Tag Manager, often called GTM, lets you add tags to a website without editing the site code each time. A tag sends data somewhere, such as a Google Analytics event or an ad conversion. A trigger decides when the tag runs. Preview mode lets you watch that chain on a live page before you publish.

Google says Preview runs the current workspace draft as if it were deployed. Visitors still get the last published version. A tag that works in Preview can still fail for real visitors. Test again after you publish.

## How to open GTM Preview mode on Mac, step by step

1. Open your container in Google Tag Manager in Chrome. Sign in with an account that has edit access.
2. Click the Workspace tab.
3. Click Preview.
4. Enter the full URL of the page you want to test, including https://, then click Connect.
5. Wait for the Tag Assistant tab to open. Click Continue in that tab.
6. Open a second tab with your site and browse the pages. Watch the Tag Assistant summary fill in.

Older versions work a little differently. Open Versions, pick the version you want, then choose More Actions > Preview. Use this when you need to see how a past version behaved, or to compare it with your current draft.

> **Test the right URL:** Enter the exact page where the tag should fire. A Page View tag on your homepage tells you nothing about a checkout page. Use a real product or checkout URL, with the same path your visitors use.

## Read the Tag Assistant panel without guessing

Preview opens Tag Assistant in its own tab. Tag Assistant is Google's debugging view. It shows the tags that fired, the tags that did not, and the events on the page. Read the summary from top to bottom before you change anything.

The Tag Assistant Chrome extension adds a side panel. It lists the Google tags on the current page. Its Troubleshoot tag option turns on debug mode through tagassistant.google.com. Google merged the older Legacy and Companion extensions into one Tag Assistant extension. If you have Legacy installed, you need not uninstall anything. Companion still works, but Google says it will be deprecated in the coming months.

If Tag Assistant says Could not connect, treat that as a loading problem first. Google's consent guide says your container may be blocked from loading in that case. Check your browser and consent setup before you dig into individual tags.

## Check the trigger before you change the tag

Most silent tags have a trigger problem. Open the tag, look at its Triggering section, and read every trigger attached to it. Check the event name, the page filter, and the trigger type. A Click trigger does not run on a page load, and a Page View trigger does not run on a button press.

Blocking triggers, also called exceptions, have a quirk. Analytics Mania says a blocking trigger can only block a firing trigger of the same event type. An exception built on a different trigger type can fail to block, or fail to fire, when you expect it to. Test the exception on its own before you trust it.

| What you see | Likely cause | First check |
| --- | --- | --- |
| Tag never appears in the summary | The trigger never matched | Event name and page filter on the trigger |
| Tag fired on the first page, not after | Once per page setting | Tag advanced settings |
| Tag works in Preview, not live | Container not published | Publish, then test the live page |
| No new events after the first one | dataLayer snippet placed below the GTM container | Order of the two snippets in the page source |
| Tag is listed but does not run | Tag is paused or on a firing schedule | Paused status and schedule in tag settings |

_Symptoms and first checks, based on Analytics Mania's list of common causes._

Start with the cheapest check. Paused tags and firing schedules take seconds to read. A dataLayer order problem takes a developer to fix, so bring them the page source order with the problem marked.

## When Preview works but GA4 shows nothing

Preview and GA4 answer different questions. Preview proves GTM ran the tag. It does not prove Google Analytics received the event. For that check, use GA4 DebugView.

Google says you can turn on debug mode with Tag Assistant or GTM Preview for your own device. You can also set debug_mode to true in the gtag config or GA4 Event tag, which affects all users. Setting debug_mode to false does not turn it off. Remove the parameter entirely.

DebugView has two streams. The Seconds stream covers the last 60 seconds. The Minutes stream covers the last 30 minutes. Events can be hidden if client-side privacy controls are in use, or if consent mode is on and the visitor has not consented to Analytics cookies. A quiet DebugView can mean a consent setting, not a broken tag.

> **Turn off GA Debugger:** The GA Debugger extension only hides GA4 requests from the Preview GA4 section. The tags still fire and still send hits. Disable it while you debug GA4, or you will chase a problem that exists only in the view.

- Turn on debug mode for your own device through Tag Assistant or GTM Preview.
- Load the page and trigger the event once.
- Open DebugView and find the event in the Seconds stream.
- If nothing appears, check the consent setting for Analytics cookies.
- When you finish, remove debug_mode from the tag and publish the change.

![Person typing on a Mac at a desk while testing a website in Google Tag Manager preview mode](https://images.lazur.app/content-images/problem/gtm-preview-mode-tag-not-firing/google-tag-manager-preview-mode-2-a4698f.jpg)

## Find out if the browser blocks the request

When Preview and GA4 disagree, look at the network. Open Chrome, load the page, then press ⌘⌥J to open DevTools on the Console. Click the Network tab. A working tag sends a request. If no request appears, the tag did not run, or something stopped it.

To check for blocked requests, press ⌘⇧P, type block, then choose Show Request Blocking. Blocked requests show in red in the Network log. That tells you an ad blocker, a privacy extension, or a firewall stopped the call. GTM did not.

On Safari, turn on Web Inspector first. Go to Safari > Settings > Advanced, then check Show features for web developers. After that, press ⌥⌘I, or choose Develop > Show Web Inspector. The Tag Assistant extension installs from the Chrome Web Store, so run the Preview checks in Chrome.

> **Use a separate Chrome profile:** Debug in a Chrome profile with no ad blocker installed. Your everyday browser stays clean. Your test profile shows what a visitor with no blockers sees.

## Ad blockers, privacy tools, and consent settings

Sometimes the tag is fine and your browser is the problem. Google's troubleshooting steps say to disable ad blockers and extensions, and to allow the Tag Assistant extension to read and change site data. Analytics Mania adds Brave Shields and Cloudflare Rocket Loader to that list.

Consent is the other silent blocker. Google's consent guide checks default and updated consent values for ad_storage, ad_personalization, ad_user_data and analytics_storage. It also checks whether each tag behaved according to consent. If the Google tag only loads after a visitor agrees, modeled conversions become less accurate.

Ad blockers reach real visitors too. Backlinko, citing GWI data, says 29.5% of internet users use ad blockers at least sometimes as of Q2 2025. For that share of people, some tags will not run. Read your reports with that gap in mind.

- **21 cents** of every media dollar wasted from poor data quality, per a 2019 Forrester study commissioned by Marketing Evolution ([source](https://customerthink.com/new-study-finds-marketers-waste-21-cents-of-every-media-dollar-from-poor-data-quality/))
- **32%** of marketing team time can go to managing data quality, as much as, per the same 2019 study ([source](https://customerthink.com/new-study-finds-marketers-waste-21-cents-of-every-media-dollar-from-poor-data-quality/))
- **29.5%** of internet users use ad blockers at least sometimes, as of Q2 2025 (GWI data) ([source](https://backlinko.com/ad-blockers-users))
- **$79.70** median hourly wage for advertising, promotions and marketing managers, May 2025 ([source](https://www.bls.gov/ooh/management/advertising-promotions-and-marketing-managers.htm))

These numbers are general. None of them measure how long a silent tag takes to fix. Treat them as context for why blockers and consent deserve a check on every test, not as a forecast for your site.

## Server-side tagging is a bigger change, not a quick fix

Server-side tagging moves some tag work to a server you control. Google lists three benefits: improved page performance, more detailed privacy controls, and improved data quality. Google's page does not say it gets around ad blockers. Do not promise that to your team.

If your silent tag is a one-off, fix the trigger, the consent setting, or the browser test first. Server-side work needs a server and a developer. Plan it as a project, not as a debugging step.

## Hand the bug to your developer in a useful form

Some causes sit outside GTM. A Content Security Policy, a firewall, or a proxy can block the tag script. Google's troubleshooting guide lists firewalls, proxies, and CSP as checks. Confirm the Google tag is on the page before you blame the container.

Write the bug so a developer can act on it in one read. Include the tag name, the trigger name, the exact URL, the browser version, and what the Tag Assistant panel showed. Attach a screenshot of the panel with any customer data cropped out.

> **Customer data on screen:** If the screen shows customer emails, account numbers, or health information, follow your employer's rules before you share a screenshot or paste text into an AI tool. Lazur listens and looks only while you hold the shortcut.

## A worked example: a purchase tag that stays silent

Say a purchase tag fires on your test store but not on the live checkout. You open Preview on the checkout URL. The Tag Assistant summary shows the page loaded, and the purchase tag is listed as not fired. The trigger waits for an event named purchase.

Your developer's code pushes the event as checkout_complete a moment after the page changes. The trigger never matches, so the tag never runs. You did not need to touch the tag. The fix is to match the event name in the trigger to the event in the code.

Publish the container, then open the live checkout in a clean profile. Check DebugView for the event, then the Network tab for the request. If both show it, write the fix in your log and close the bug.

## Keep a test log so you do not repeat yourself

A short log saves the most time on a long bug. A Google Sheet works well. Use one row per test with the date, page URL, tag name, trigger, what Preview showed, what DebugView showed, and the fix you tried. Read the basics in [Google Sheets for marketers](https://www.lazur.app/for/marketers/google-sheets).

### Mistakes people make

- Testing the draft, then assuming the live site matches it.
- Setting debug_mode to false and believing debug mode is off.
- Trusting a fix before you publish and check the live page.
- Changing three triggers at once, so nobody knows which change worked.
- Blaming GTM when an ad blocker or a consent setting stops the request.

If you are stuck after the checks above, write down what you tried and send it to your developer. A clear log turns a vague bug into a short task.

## Where Lazur helps, and where it stops

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥⌘ to ask about anything on screen, and Lazur answers out loud. It can point at things, so you can find the Preview button or the Troubleshoot tag option without hunting.

Lazur can also guide you through the steps one click at a time. It waits for each click, and you do the clicking. Lazur does not press buttons, edit tags, or work inside Tag Manager for you. Lazur is not a plugin or add-in for Google Tag Manager or any other app.

Hold fn to dictate clean text at the cursor in any app. That helps when you write the bug note. Dictation is unlimited on both paid plans.

Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. Content is never used to train AI models.

Lazur runs on macOS, on Apple silicon and Intel Macs. Windows is planned, not available. The 3-day Pro trial starts when you first open the app, with no credit card. Check the [pricing page](https://www.lazur.app/pricing) for paid plans, or [download Lazur](https://www.lazur.app/download) to try it on your Mac.

## What to do after the tag fires

Once the tag fires in Preview and shows up in DebugView, publish the container. Load the live page in your clean profile and check again. Write the fix in your log, and tell your team what changed and when. The next report then starts from facts, not memory.

![Office team reviewing an analytics dashboard after a tag fix in Google Tag Manager preview mode](https://images.lazur.app/content-images/problem/gtm-preview-mode-tag-not-firing/google-tag-manager-preview-mode-3-9e8c68.jpg)

## With Lazur

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ and ask; it sees your screen, answers out loud, points at buttons and walks you through apps. Hold fn to dictate. Free for 3 days, then $18/month: https://www.lazur.app/download

- “Where is the Preview button in this container?”: Lazur circles the Preview button and labels it. You click it yourself, then continue in the Tag Assistant tab. (Points at it)
- “What does this Tag Assistant message mean?”: Lazur reads the panel on screen and explains the message out loud in plain words. It does not change anything in the panel.
- “Where is the Troubleshoot tag option?”: Lazur draws a circle and a label around the option. You click it yourself.
- “Walk me through the GTM Preview steps.”: Lazur guides you one click at a time and waits for each click before it moves on. It does not click for you.
- “Type this bug note into my Google Doc.”: Hold fn and speak. Clean text appears at the cursor in any app, so the bug note goes into your doc without retyping.
- “Draft a bug report for my developer.”: Lazur drafts the message from what you tell it. You check the tag name, the URL, and the trigger before you send anything.
- “Remind me to recheck the live page tomorrow morning.”: Lazur adds an item to Apple Reminders. Use it to schedule the live check after you publish.

## A plan you can start this week

- **Day 1: Reproduce the bug in Preview.** Open the Workspace tab, click Preview, enter the exact URL, and click Connect. Click Continue in the Tag Assistant tab. Note which tags fired and which did not, with the trigger names beside them.
- **Day 1: Check triggers and tag settings.** Read each trigger on the silent tag. Check the event name, the page filter, the paused status, the once per page setting, and any firing schedule. Fix one thing at a time and retest in Preview after each change.
- **Day 2: Test in a clean browser.** Open a Chrome profile with no ad blocker. Run the same URL again. Press ⌘⌥J, open the Network tab, and look for the tag request. Note any red blocked requests and the name of the blocker or extension you suspect.
- **Day 2: Check GA4 in DebugView.** Turn on debug mode for your own device, trigger the event once, and open DebugView. Check the Seconds stream first. When you finish, remove debug_mode from the tag, because setting it to false does not turn it off.
- **Day 3: Publish and test the live page.** Publish the container, then load the live page in your clean profile. Confirm the request in the Network tab and the event in GA4. Write the fix and the date in your test log, then tell your developer what changed.

## FAQ

### Why does my tag work in Preview but not on the live site?

Preview runs the workspace draft. Visitors get the last published version. If you did not publish after your change, the live site runs the old setup. Publish the container, then test the live page in a clean browser profile.

### Does Preview mode show whether Google Analytics received the event?

No. Preview shows that GTM ran the tag. To see what GA4 received, open DebugView, turn on debug mode for your device, trigger the event, and check the Seconds stream. Privacy controls and consent settings can hide events there.

### How do I turn off GA4 debug mode after testing?

Remove the debug_mode parameter from the gtag config or GA4 Event tag. Setting debug_mode to false does not turn it off. Remove the parameter, then publish the change.

### Is Tag Assistant Companion still needed?

Not for new work. Google merged Tag Assistant Legacy and Companion into one Tag Assistant extension. Companion still works, but Google says it will be deprecated in the coming months. Legacy users need not uninstall anything.

### Does server-side tagging get around ad blockers?

Google lists three benefits for server-side tagging: improved page performance, more detailed privacy controls, and improved data quality. Its page does not say server-side tagging defeats ad blockers. Treat it as a larger project, not a quick recovery for blocked tags.

### Can I run Preview mode in Safari?

Use Chrome for the Preview and Tag Assistant steps, since the Tag Assistant extension installs from the Chrome Web Store. Safari's Web Inspector still helps with network checks. Turn it on under Safari > Settings > Advanced, then press ⌥⌘I.

### Does Lazur click the buttons in Tag Manager for me?

No. Lazur does not click buttons, edit tags, or operate other apps for you. It can point at the Preview button, guide you one click at a time, explain a message on screen, and dictate or draft text. You do the clicking and the editing.

### Is there a free trial of Lazur?

Yes. Lazur has a 3-day Pro trial with no credit card. The trial starts the first time you open the app. Paid plans are listed on the pricing page.

## Sources

1. [Google Tag Manager Help: Preview and debug](https://support.google.com/tagmanager/answer/6107056), Google, checked 2026-11-08
2. [Troubleshoot with Tag Assistant](https://support.google.com/tagassistant/answer/10039345?hl=en), Google, checked 2026-11-08
3. [Tag Assistant Chrome extension](https://support.google.com/tagmanager/answer/16463290?hl=en), Google, checked 2026-11-08
4. [Monitor events in DebugView](https://support.google.com/analytics/answer/7201382?hl=en), Google, checked 2026-11-08
5. [Troubleshoot consent mode with Tag Assistant](https://developers.google.com/tag-platform/security/guides/consent-debugging), Google for Developers, checked 2026-11-08
6. [Server-side tagging](https://developers.google.com/tag-platform/tag-manager/server-side), Google for Developers, checked 2026-11-08
7. [Network panel (Chrome DevTools)](https://developer.chrome.com/docs/devtools/network/), Chrome for Developers, checked 2026-11-08
8. [Enabling Web Inspector](https://webkit.org/web-inspector/enabling-web-inspector/), WebKit, checked 2026-11-08
9. [Advertising, Promotions, and Marketing Managers](https://www.bls.gov/ooh/management/advertising-promotions-and-marketing-managers.htm), U.S. Bureau of Labor Statistics, checked 2026-11-08
10. [12 Reasons Why a Tag in Google Tag Manager is Not Firing](https://www.analyticsmania.com/post/tag-in-google-tag-manager-is-not-firing/), Analytics Mania, checked 2026-11-08
11. [Preview Mode Not Working? 26 ways to fix it](https://www.analyticsmania.com/post/google-tag-manager-preview-mode-not-working/), Analytics Mania, checked 2026-11-08
12. [Ad Blocker Usage and Demographic Statistics in 2026](https://backlinko.com/ad-blockers-users), Backlinko, checked 2026-11-08
13. [New Study Finds Marketers Waste 21 Cents of Every Media Dollar From Poor Data Quality](https://customerthink.com/new-study-finds-marketers-waste-21-cents-of-every-media-dollar-from-poor-data-quality/), CustomerThink, checked 2026-11-08