Google tag not detected on website: why Tag Assistant can't find it

TofuAnswer by the Tofu team · checked

When Tag Assistant can't find your Google tag, Google says to check two things: that you're using the correct tag ID and that the code is live on the page. Beyond that, look for landing pages on another tool or subdomain without the code, a Tag Manager container that was saved or previewed but never published, the wrong ID, or a tag that loads but isn't connected to Google Ads. Ad blockers, consent banners and late-loading scripts can also stop Tag Assistant connecting. The example below works through each check in order.

Ask Tofu next

Pick a question and Tofu Ads Agent answers it in chat.

As of November 2026.

The example

Say you run marketing ops at a 60-person B2B software company. Your main site uses Google Tag Manager, your demo pages are HubSpot landing pages on a subdomain, and last week someone added the Google Ads conversion tag in Tag Manager. Now Google Ads says your Google tag isn't detected, and Tag Assistant won't connect to the demo page. These are example inputs, not benchmarks:

InputValue
Main sitewww.example.com on WordPress, with Tag Manager container GTM-AB12CD3 in the page code
Demo pagesgo.example.com, HubSpot landing pages
Google Ads tag IDAW-123456789
Tag ManagerGoogle Ads conversion tag and Conversion Linker added last week, tested in Preview, not published
Consent bannerBlocks Google tags until the visitor makes a choice (basic consent mode)
What you seeTag Assistant finds no tag on go.example.com/demo

Step by step

1. Check that the code is on the live page

One of Google's two checks is "Your code is live," and it says to use your browser's developer tools "to see what code has loaded." Open go.example.com/demo, open the developer tools, go to the Network tab and reload. Look for a request to googletagmanager.com: gtm.js with your GTM- ID for Tag Manager, or gtag/js with a G- or AW- ID for the Google tag.

In the example, www.example.com loads gtm.js?id=GTM-AB12CD3, but the demo page loads nothing. HubSpot's help explains why: its Tag Manager setting "runs on all HubSpot-hosted content," and "You'll need to connect external content to Google Tag Manager separately." It works the other way too: code on your main site doesn't reach your HubSpot pages.

The fix: in HubSpot, go to Settings, then Content, then Pages, open the Integrations tab, select Integrate with Google Tag Manager, enter GTM-AB12CD3 and click Save. HubSpot says this needs Super Admin or Website settings permission. Google's rule covers any page builder: "Remember to set up the Google tag on every website that should send data."

To see which pages have the tag, open the tag coverage summary from your Google tag settings (in Google Ads: Tools, Data manager, then Manage under Google tag). It marks each page Not tagged, No recent activity or Tagged.

2. Check the ID, and that the tag is connected to Google Ads

Google's other check is "You're adding the correct measurement ID." To find yours in Google Ads, go to Tools, Data manager, click Manage under Google tag, click the Google tag and copy the ID under Tag details.

The prefix matters. Google says a container ID starting with GTM- "allows all tag types," while one starting with G- or AW- "is limited to Google tags."

If Tag Assistant does find a tag but Google Ads gets nothing, Google says "your Google tag might not be connected to a destination." You'll see a notice when you open the Google tag page, and you can connect Google Ads there. This can happen when a site has only the GA4 tag (G-): Google says you can add the other product "as a destination" in the tag's settings.

One more case: a Tag Manager snippet sitting next to gtag('config') code is what Google calls "an unsupported implementation." What the Google tag's move into Tag Manager changes covers it. In the example, the page code and Google Ads use the right IDs, so move on.

3. Check that the Tag Manager container is published

Check this first when the tag is "in Tag Manager" but Google Ads shows it as inactive. Google says that after you add or edit tags, "you will need to publish those changes to make those changes operational on your website." Preview doesn't count: it lets you browse "as if the current container draft was deployed," and only in the browser where you turned it on (or for people you share the preview with).

To publish, click Submit, keep Publish and Create Version selected and click Publish. To see what's live, open Versions and look for a date in the Published column.

In the example, the Google Ads tags were previewed but never published, so the live site sent nothing. Once they're published, Google says containers with Google Ads tags "automatically load a Google tag first, before sending events." Also check that the conversion tag fires on the right trigger, such as the thank-you page load or a form submission, as Google's troubleshooting steps say.

4. Get Tag Assistant to connect

Start on a landing page or the home page, not the thank-you page. Google says: "It's best to use a landing page or home page instead of the conversion page URL directly." If you start Tag Assistant from Google Ads and use Tag Manager, "you may need to enable your Tag Manager container for debugging" by selecting Debug live version.

If it still won't connect, Google lists these causes, among others:

  • The URL you entered doesn't have the Google tag. Try another page where it should be.
  • The script "is loaded after the point when Tag Assistant tries to connect to the page." Click Retry.
  • "Ad blockers installed in your web browser may prevent the Google tag from running," and other browser extensions can block it too.
  • "Consent management tools may block Google tags." With basic consent mode, Google tags don't load "until a user interacts with a consent banner," so make a choice on the banner in the debug window.
  • The tag loads inside an iframe, which Tag Assistant can only debug with its Chrome extension installed. For forms in iframes, see tracking an embedded HubSpot or Calendly form.
  • Multiple redirects, an AMP page (not supported), a firewall or proxy server, or a content security policy that blocks the container.

In the example, the consent banner held the tags until a choice was made on it.

5. Give the status time to update

Don't keep changing things while you wait. Google gives these times:

  • Tag coverage "may not update status for up to 24 hours" when it relies on live traffic. Tag Assistant shows a page in real time.
  • Conversion actions you verify in a Tag Assistant session started from Google Ads update there "After approximately 30 minutes."
  • After you set up a new Google tag, "It may take up to 30 minutes for data collection to start."

What changes the answer

If…Then…
Your site uses the gtag.js snippet and no Tag ManagerSkip step 3. Google says to paste the snippet "immediately after the <head> element" on every page, and "Don't add more than one Google tag to each page"
Your pages have a Tag Manager snippet plus gtag('config') codeGoogle calls this unsupported; see the Google tag's move into Tag Manager
Tag Assistant finds the tag, but Google Ads gets no dataConnect Google Ads as a destination of the tag (step 2)
A campaign says "Eligible (Misconfigured): Your website is missing a Google tag"Google says this "often means your campaign hasn't recorded any biddable conversions in the last 28 days." See Google Ads campaign statuses
A conversion action shows "Unverified" or "Tag inactive"Google lets you launch Tag Assistant from that status with Troubleshoot. What each status means is in why Google Ads leads dropped
Your demo form is in an iframeInstall the Tag Assistant Chrome extension, and see embedded form tracking

Mistakes in this example to avoid

  • Calling it fixed after Preview. Preview shows the draft only in your browser; visitors get the published version.
  • Pasting a second Google tag "to be safe." Google says not to add more than one Google tag to a page.
  • Fixing the main site and forgetting the landing pages. The demo pages on go.example.com were the ones missing the code.
  • Changing settings again before the status could update. Allow the times in step 5 before you judge a fix.

Where Tofu fits

Tofu Ads Agent (our product) includes a conversion tracking audit for Google Search, can set up conversion events on Google for a page visit or a click, and its agent app connects to Google Tag Manager and GA4. It doesn't edit your website code or your landing page builder, and it doesn't change your consent banner, so steps 1 and 4 stay with whoever manages your site.

Sources (16)

Related resources