How do I know if it's consent mode and not a broken tag?

Test both paths: accept the banner in one browser session and decline it in another (or clear cookies between tests). If the pixel fires when you accept but not when you decline, that's consent working as configured, not a bug. If it's missing in both cases, you have a separate firing problem.

Why does this affect Meta more than GA4?

Google's consent mode has a "basic" fallback that keeps sending pinged, cookieless data even without consent, so GA4 often still shows partial signal. Meta Pixel typically has no such fallback: without consent it sends nothing at all, which makes the drop-off look larger on the Meta side even when both platforms are behaving correctly.

Can a consent banner block tracking for users who haven't interacted with it yet?

Yes, and this is the version worth checking first. Some CMPs default to "denied" until a visitor makes a choice, others default to "granted" until they explicitly decline. If your CMP defaults to denied, every visitor who bounces before interacting with the banner is being counted as declined, even though they never said no.

Does this explain a mismatch between GA4 and Meta specifically?

Often, yes. If GA4 keeps a cookieless fallback and Meta doesn't, a legitimate consent configuration can produce exactly the pattern that looks like a cross-platform mismatch: GA4 shows a purchase, Meta shows nothing. Worth ruling out before assuming something broke.

Should I rule out consent before reporting a tracking bug?

Yes, always check this first. It takes a few minutes (see the test above) and it's one of the most common reasons a "broken" pixel turns out to be working exactly as configured.

Is your consent banner blocking GA4 or Meta Pixel?

A cookie consent banner working exactly as configured can look identical to a broken tag: events go missing, numbers drop, and nobody notices until someone asks why conversions are down. Here's how to tell the two apart.

6 min read

Why this is easy to misdiagnose

A missing pixel event and a suppressed pixel event look exactly the same from the outside: no request in the network tab, no event in your dashboard. The difference matters because the fix is completely different. A broken tag needs debugging. A working consent banner doing its job needs a decision about defaults, not a bug fix.

Teams that skip this check often spend hours debugging a tag that was never broken, or worse, loosen consent defaults to make the numbers look better without realizing that's what they just did.

Three ways a consent banner suppresses tracking

Each produces a different pattern in your data. Knowing which one you have tells you whether to fix your tag or fix your consent configuration.

Default-to-denied before any interaction

Some consent management platforms (CMPs) set every category to "denied" until a visitor explicitly accepts. Anyone who bounces before interacting with the banner, closes the tab, gets distracted, or is simply browsing quickly, is counted as declined even though they made no choice at all.

Fix: Check your CMP's default state in its own settings, not just your tag manager. If it defaults to denied, decide whether that matches your actual compliance requirement or is more conservative than necessary.

GA4 has a fallback, Meta doesn't

Google's consent mode can send a reduced, cookieless "ping" even when consent is denied (consent mode's basic behavior). Meta Pixel has no equivalent: when consent is denied, it typically sends nothing. The result is GA4 showing partial signal while Meta shows none, for the exact same visitors.

Fix: Don't treat a GA4-vs-Meta gap as a mismatch incident without checking consent state first. If the gap tracks closely with your decline rate, that's consent doing what it's configured to do.

A CMP misconfiguration suppresses more than intended

It's common for a CMP integration to accidentally gate an unrelated category, for example, blocking "analytics" consent from also blocking a pixel that should only depend on "marketing" consent. This looks identical to a real block rate problem, but the actual issue is a mapping error in the CMP setup.

Fix: Check your CMP's category mapping against what each pixel is actually configured to check. A pixel gated on the wrong consent category will show the same symptom as legitimate suppression, but the fix is a five-minute config change, not a debugging session.

A quick test to tell consent and broken tracking apart

Step 1: Test both consent states

In one browser profile (or after clearing cookies), accept the banner and complete a test conversion. In another, decline it and repeat. If the pixel fires on accept but not on decline, that's consent behaving as configured.

Step 2: Check whether the gap tracks your decline rate

If your CMP reports a 30% decline rate and your GA4-vs-Meta gap is roughly 30%, that correlation is a strong signal the "mismatch" is consent, not a broken tag. A gap far larger or smaller than your decline rate points to something else.

Step 3: Confirm your CMP's default state

Open your CMP's own configuration (not your tag manager) and check what happens before a visitor interacts with the banner: granted, denied, or unset. This single setting explains a lot of "missing" events that were never really missing, just correctly withheld.

Step 4: Check category mapping per pixel

Confirm each pixel is gated on the consent category it should actually depend on. A pixel accidentally tied to the wrong category will look broken when it's really a mapping error.

Rule out consent before you chase a phantom bug

The steps above take a few minutes and save hours of debugging a tag that was never broken. Once you've confirmed the gap isn't consent-driven, Kickin monitors your GA4 and Meta events continuously so you know within minutes when something that was firing reliably actually stops, instead of finding out weeks later.

FAQ

Frequently Asked Questions

Stop guessing whether it's consent or a broken tag

Once you've ruled out consent, Kickin monitors your GA4 and Meta events continuously and alerts you the moment something actually breaks.