# Google Tag Not Detected? Why Tag Assistant Misses It {#post-title}

[All Pixel Helper](/blog/#blog-all-pixel-helper)

By [B2B Gold](/about/#how-we-write) Published 25 September 2026

## Why does Google say my tag isn’t detected? {#why-does-google-say-my-tag-isnt-detected}

Google’s Tag Diagnostics flags a tag it detected before but not in the last 48 hours; Tag Assistant finds none on the page you entered. Usually the tag isn’t on that page, runs in an iframe or Shopify custom pixel Tag Assistant may not read, waits for consent, or is blocked by an ad blocker or Content Security Policy.

Tell the two apart before you change anything. Google’s warning is about what reached Google over days; Tag Assistant’s is about one page in one browser session. Google’s pages cited below were checked on 25 September 2026.

| What you see | Start with |
| --- | --- |
| Tag Diagnostics shows **Urgent** or **No recent data** | [Is it the tag or the tool?](#is-it-the-tag-or-the-tool) |
| Tag Assistant finds no tag | [Confirm the tag is on the page](#how-do-you-confirm-the-google-tag-is-on-the-page) |
| It fails only on Shopify, or only at checkout | [Shopify](#why-cant-tag-assistant-see-it-on-shopify) |
| Tag Assistant or Preview won’t connect | [Connection problems](#why-wont-tag-assistant-or-preview-connect) |
| The tag loads, but GA4 or Google Ads gets nothing | [Loads but sends nothing](#why-does-the-tag-load-but-send-nothing) |

## Is it the tag or the tool? {#is-it-the-tag-or-the-tool}

Check what Google itself has received first. Tag Diagnostics reports on the tag across your site over time, while Tag Assistant tests one address in one session and can miss a tag that works.

- **Tag Diagnostics.** Open your Google tag’s settings and click **View diagnostics** under **Tag quality**. An **Urgent** status marks a critical issue, and Google’s example is a tag detected before but not in the last 48 hours, so data drops to zero; **No recent data** means Google has never detected it on your site. Other notices include **Some of your pages are not tagged**, **Some pages missing consent for EEA users**, **Consent mode installation out of order** and **Content Security Policy blocks some resources** ([Google: Tag Diagnostics](https://support.google.com/tagmanager/answer/14681508)).
- **Tag Assistant.** At [tagassistant.google.com](https://tagassistant.google.com/) you click **Add domain**, enter an address and click **Connect**, and the page opens in a debug session that your regular visitors don’t see. It can only find a tag that’s on the page you entered, it needs Google’s Tag Assistant Chrome extension to debug a tag inside an iframe, and a Content Security Policy can block it ([Google: Tag Assistant](https://support.google.com/tagassistant/answer/10039345)).

If Tag Diagnostics is healthy and only Tag Assistant complains, the tool is the problem: skip to [connection problems](#why-wont-tag-assistant-or-preview-connect). If it shows **Urgent** because the tag stopped being detected, the tag has been missing or blocked for at least two days: look for a theme change, a new consent banner or a new security header from before then.

## How do you confirm the Google tag is on the page? {#how-do-you-confirm-the-google-tag-is-on-the-page}

Look at the requests the page sends, not at its source code. Google’s own advice for a tag it can’t find is to check the measurement ID and confirm your code is live with the browser’s developer tools ([Google: fix issues with your Google tag](https://support.google.com/google-ads/answer/15756500)).

1. Open the page in Chrome, open DevTools and select **Network**.
2. Tick **Preserve log**, so requests survive page changes ([Chrome: Network reference](https://developer.chrome.com/docs/devtools/network/reference)).
3. Reload, then type `googletagmanager` in the filter box. The Google tag (`gtag/js`) or the Tag Manager container (`gtm.js`) should load with your ID in its address: `G-` followed by letters and digits, or `AW-` followed by digits, for a Google tag; `GTM-` followed by letters and digits for a container.
4. Change the filter to `collect` and do something the tag should measure. A GA4 hit goes to an address ending in `/g/collect` and carries your measurement ID.
5. If nothing appears, choose **More filters** → **Blocked requests**. Chrome highlights blocked requests in red.

Viewing the page source finds only tags typed into your theme or HTML. A tag that Tag Manager or an app adds appears only once it runs, which is why the Network panel is the better test.

## Why can’t Tag Assistant see it on Shopify? {#why-cant-tag-assistant-see-it-on-shopify}

Because on Shopify the tag often runs inside one of Shopify’s pixel sandboxes, and Google says its tools may not work from a custom pixel’s. Google calls Google tags inside a Shopify custom pixel “not a supported implementation”, lists Tag Assistant and even Tag Diagnostics among the features that may not work correctly from that sandbox, and recommends its Google & YouTube app instead ([Google: custom pixel limitations](https://support.google.com/google-ads/answer/16000892)). Shopify says the same from its side: Tag Assistant isn’t compatible with custom pixels ([Shopify: replacing Google Tag Manager scripts](https://help.shopify.com/en/manual/checkout-settings/customize-checkout-configurations/upgrade-thank-you-order-status/replace-google-tag)).

- **Theme code doesn’t reach checkout.** A tag in your theme runs on storefront pages only. Checkout and the Thank you page need a pixel or the Google & YouTube app: see [moving Google tags off the Thank you page](/blog/shopify-additional-scripts-tracking/#google-ads-and-ga4).
- **Tag Manager in a custom pixel.** It runs, within the sandbox’s limits, but Tag Assistant can’t test it. Test with Shopify’s Pixel Helper and Google’s own reports instead: see [Google Tag Manager in a custom pixel](/blog/shopify-app-pixels-vs-custom-pixels/#can-you-use-google-tag-manager-in-a-custom-pixel).
- **A warning isn’t proof either way.** In a Shopify Community thread that ran from January to August 2024, merchants using the Google & YouTube app saw Tag Assistant warn that the Google tag should have loaded before an event command was called, and asked whether tracking still worked; the only fix offered came from a merchant, not Shopify or Google. In a 2022 thread, Tag Assistant found no tags on a store whose theme code combined a Tag Manager snippet with Google tag config commands; the accepted answer was to keep only the snippet and add the Google tags inside the container.

When Tag Assistant can’t test a set-up, check what Google received in GA4’s own reports and in the status of each conversion action in Google Ads.

## Why won’t Tag Assistant or Preview connect? {#why-wont-tag-assistant-or-preview-connect}

Usually because something in the browser stops the debug session or the tag, or the address you entered isn’t where the tag runs. Every cause below is in Google’s help.

| Cause | Fix |
| --- | --- |
| The tag isn’t on the address you entered | Enter a page where the tag should load, and check the address is exact |
| The debug parameter breaks your site | Deselect **Include debug signal in the URL** |
| Several redirects stop the debug window loading | Enter the final address the browser lands on |
| The tag loads after Tag Assistant tries to connect | Click **Retry** |
| An ad blocker or other extension stops the Google tag running | Pause it for the site, or test in a clean Chrome profile |
| A consent management tool holds Google tags | Set it to allow interaction with Google’s consent API, or accept on the banner and retry |
| The tag runs in an iframe | Install Google’s Tag Assistant Chrome extension and let it read and change site data |
| Your Content Security Policy blocks tag resources | Tag Assistant lists what your policy blocked; allow those origins, or use Google’s nonce method |
| An AMP page | Tag Assistant doesn’t support AMP pages |

Sources: [Google: Tag Assistant](https://support.google.com/tagassistant/answer/10039345) and [Google: Tag Manager and CSP](https://developers.google.com/tag-platform/security/guides/csp) (updated 18 September 2026).

Preview mode asks for your site’s address and connects the same way, so the same causes apply; it also needs you to open the container in Tag Manager ([Google: Preview and debug containers](https://support.google.com/tagmanager/answer/6107056)). With Google’s Tag Assistant Chrome extension installed, your site opens in a new tab rather than a new window, which is easy to miss. That extension now combines the old Tag Assistant Companion and Tag Assistant Legacy ([Google: Tag Assistant Chrome extension](https://support.google.com/tagmanager/answer/16463290)).

## Why does the tag load but send nothing? {#why-does-the-tag-load-but-send-nothing}

Usually consent, a blocked request, a missing destination, or a hit sent to an address you aren’t watching. A tag can load and still send no measurement request.

- **Basic consent mode.** Google’s tags stay blocked until the visitor interacts with the consent banner, and nothing is sent before they consent, not even the default consent state ([Google: consent mode overview](https://developers.google.com/tag-platform/security/concepts/consent-mode), updated 30 July 2026). Accept on the banner and the requests should start: [check that Google Consent Mode is working](/blog/check-google-consent-mode/).
- **DebugView is empty.** GA4 doesn’t show events in debug mode when consent mode is in place and the visitor hasn’t granted consent for analytics cookies ([Google: DebugView](https://support.google.com/analytics/answer/7201382)).
- **The request was blocked.** A red request in the Network panel was stopped before it finished. To find out what stopped it, [tell whether an ad blocker or CSP is blocking a tag](/blog/pixels-blocked-ad-blocker-csp/).
- **No destination.** When Tag Assistant finds the tag but no events, Google’s reading is that the tag may not be connected to a destination, so check the tag’s settings ([Google: verify your Google tag](https://support.google.com/tagmanager/answer/15756111)).
- **A server-side tagging address.** With server-side tagging, the page sends its measurement requests to a tagging server the site runs, often on its own domain, and that server routes the data on ([Google: server-side tagging](https://developers.google.com/tag-platform/tag-manager/server-side/intro), [custom domains](https://developers.google.com/tag-platform/tag-manager/server-side/custom-domain)). Filter the Network panel on the path, not on Google’s hostname, or you’ll miss those hits. What the server forwards to Google goes server to server and never appears in the browser.

## How do you check without Tag Assistant? {#how-do-you-check-without-tag-assistant}

With the Network panel steps above, which need nothing installed, or with an extension that decodes Google’s requests for you. [All Pixel Helper](/chrome/all-pixel-helper/), which we build, shows whether the Tag Manager container (as `container_loaded`), GA4 and Google Ads requests left the tab, with their IDs and each request’s outcome, without connecting a Google account. It doesn’t show triggers or why a tag didn’t fire, which is what Tag Manager’s Preview mode is for. It matches only Google’s usual addresses for these (`www.googletagmanager.com`, Google Analytics’ collection hosts and `www.googleadservices.com`), so hits sent to a server-side or first-party tagging address don’t appear. And an outcome of delivered means the browser got a response, not that Google recorded the hit. It doesn’t block or change requests, but it does add an empty `dataLayer` to pages that have none, so with it installed an empty `dataLayer` in the console doesn’t prove Tag Manager is on the page; the extension itself sends nothing anywhere.

It reads requests from every frame in the tab, so requests from a tag in an iframe, including a Shopify custom pixel’s, should be listed with the page’s own. Shopify’s app pixels run in a web worker instead, and we haven’t yet confirmed that their requests appear.

If Tag Manager is involved, [check the dataLayer in Chrome](/blog/check-datalayer-in-chrome/) next. For platforms beyond Google, [check every pixel on the page](/blog/check-if-pixel-is-working/); if Meta Ads Data Advisor (formerly Meta Pixel Helper) is silent too, see [why Meta Pixel Helper finds no pixel](/blog/meta-pixel-helper-not-working/).

## Frequently asked questions {#frequently-asked-questions}

### Does the Google and YouTube app use Google Tag Manager? {#does-the-google-and-youtube-app-use-google-tag-manager}

It sets up your Google tag, not a Tag Manager container. Shopify points you to Google’s instructions for setting up your Google tag with the app ([Shopify: Google Analytics setup](https://help.shopify.com/en/manual/reports-and-analytics/google-analytics/google-analytics-setup)), and recommends the app over a Tag Manager script on the Thank you page because Google maintains it. A Tag Manager custom pixel is a route Google doesn’t recommend or support ([Shopify: replacing Google Tag Manager scripts](https://help.shopify.com/en/manual/checkout-settings/customize-checkout-configurations/upgrade-thank-you-order-status/replace-google-tag)). The move is covered in [the 26 August Thank-you-page change](/blog/shopify-additional-scripts-tracking/).

### What does “Some of your pages are not tagged” mean? {#what-does-some-of-your-pages-are-not-tagged-mean}

It’s a Tag Diagnostics notice: some pages on your site don’t carry the Google tag, which can weaken your measurement. Google’s fix starts in the **Tag coverage summary**, which shows the untagged pages; look for templates or parts of the site that load without the tag, such as pages from a landing-page builder or a separate domain.

### Why does it work in Preview but not for visitors? {#why-does-it-work-in-preview-but-not-for-visitors}

Preview runs your workspace’s unpublished changes as if they were live, so a fix that works there does nothing for visitors until you publish the container. Beyond that, testers usually accept the consent banner and switch off their blockers, and many visitors don’t. A cached page can also serve old code for a while after you publish.

[All Pixel Helper - Tag, dataLayer & Consent Debugger](/chrome/all-pixel-helper/)

All Pixel Helper is a free Chrome extension that lists and decodes the requests a web page sends to 40 ad and analytics platforms, including Meta, TikTok, GA4, Google Tag Manager and Shopify, and marks each one delivered, failed or blocked. It also shows every dataLayer push, with paths you can copy into Tag Manager, and the consent signals on Google, Meta, Microsoft and TikTok requests.

[Add to Chrome](https://chromewebstore.google.com/detail/all-pixel-helper-tag-data/bdedmcfjebcoemocjajpohkbnohbfeld?utm_source=b2bgold.app&utm_medium=referral&utm_campaign=blog&utm_content=blog/google-tag-not-detected&utm_term=post-cta) [Plans and pricing](/chrome/all-pixel-helper/#pricing)

Need help with All Pixel Helper? Email [chrome@afixer.app](mailto:chrome@afixer.app).

## More on All Pixel Helper {#related-heading}

- 25 September 2026 **[Pixels Blocked by an Ad Blocker or CSP? How to Tell](/blog/pixels-blocked-ad-blocker-csp/)** Tell an ad blocker from a Content Security Policy or a consent tool when tags go missing: ERR_BLOCKED_BY_CLIENT, CSP errors in the Console, and what to fix.
- 25 September 2026 **[How to Check If Your Tracking Pixels Are Working](/blog/check-if-pixel-is-working/)** Check any tracking pixel with the platform's own tool or Chrome's Network panel: did it load, fire, reach the platform and carry the right event and values?
- 25 September 2026 **[Meta Pixel Helper Not Working? Why It Finds No Pixel](/blog/meta-pixel-helper-not-working/)** Meta Pixel Helper, now Meta Ads Data Advisor, shows no pixel? Ad blockers, consent banners, iframes, Shopify's sandbox and server-only events: what to check.