Prompt

consent banner loads but tags still fire

Technology / Marketing Automation1 observationLast seen Oct 29, 2026

Latest observation

Oct 29, 2026OpenAI APIWeb search: off

If the consent banner loads but tags still fire, the usual cause is that the banner is only displaying UI and not actually blocking tag execution.

Here’s a quick checklist to debug it:

1) Verify tags are actually consent-gated

Make sure each tag is set to require consent before firing.

  • Google Tag Manager: check the tag’s Consent Settings
  • Ensure it’s not configured to fire on All Pages without consent checks
  • Confirm the default consent state is denied until the user opts in

2) Check the consent initialization happens before tags load

Consent must be set before any tags execute.

  • The consent banner / consent mode script should load before GTM / analytics / ad tags
  • If GTM loads first, tags may fire before consent is updated

3) Confirm the banner is updating consent correctly

The banner should send an explicit consent update on user action:

  • Accept → granted
  • Reject → denied
  • Partial consent should map each storage type correctly

If the banner only stores a preference in localStorage/cookie but doesn’t call the consent API, tags may still fire.

4) Test in browser devtools

Open DevTools and check:

  • Network tab: see whether analytics/ad requests are sent before consent
  • Console: confirm consent state
  • Cookies/localStorage: verify the banner preference is saved
  • Tag Assistant / GTM Preview: see whether consent is blocking tags

5) Watch for hardcoded scripts

Even if GTM is blocked, hardcoded scripts can still fire:

  • GA/gtag snippets in the site code
  • Facebook Pixel
  • Hotjar
  • Custom third-party scripts

Search your codebase for direct script embeds.

6) Check for CMP integration issues

If using a CMP like Cookiebot, OneTrust, Axeptio, etc.:

  • Verify GTM integration is enabled
  • Check consent categories are mapped correctly
  • Ensure the CMP is sending consent events, not just showing the banner

7) Look for race conditions

If the banner appears late, tags may already have fired.

Common symptoms:

  • Banner loads after page view tags
  • Consent updates happen after first page load
  • SPA route changes trigger tags before consent state is applied

Quick diagnostic question

What are you using?

  • Google Tag Manager + Consent Mode
  • gtag.js
  • A CMP like OneTrust/Cookiebot
  • Custom scripts

If you share:

  1. the CMP/banner tool,
  2. how tags are installed,
  3. one example tag that still fires,

I can tell you exactly where the issue is likely happening.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.