# Third-Party Scripts After Consent: The Tags That Reload Themselves

Source: https://bannerwarden.com/blog/2026-11-14-third-party-scripts-after-consent-reload.html

November 14, 2026

*A team denies all consent, loads the page, and watches the network tab. The Meta Pixel fires. A LinkedIn tag fires. A custom HTML tag fires, and the tag it loads fires another tag. The banner collected the refusal. The tags never got the message, because the banner is not the enforcement. The enforcement is per tag, and half the tags never got theirs.*

## The tags that reload themselves

Consent is a state, and tags are supposed to respect it. The failure is that tags do not only fire once. A tag that fires on page load can fire again when the user navigates, when the consent choice changes, when a single-page app swaps content, when a script reloads itself. Each firing is a new chance to ignore the consent state, and the tags that reload themselves are the ones that get missed, because the audit checked the first load and stopped. The [analytics and marketing split](2026-11-13-analytics-vs-marketing-consent.md) is the same problem in a different form: one toggle for two purposes, and a tag that fires under the wrong one. The audit has to watch the page over time, not just at load.

## Consent Mode v2 and the tags it does not govern

Google Consent Mode v2 governs Google's tags. It does not govern the Meta Pixel, TikTok, LinkedIn, or any custom HTML tag, which fire on their triggers whatever the signals say, unless each one gets its own consent check. Consent Mode is a Google mechanism, and the tags outside it need their own enforcement. A team that installs Consent Mode and assumes the problem is solved has governed a third of its tags and ignored the rest. The banner is the user interface. The tag manager is the enforcement point, and every tag in it needs a consent condition, not just the Google ones.

## The audit: deny, then watch the network tab

Deny all consent, load the page, and watch the network tab. Any request to a known tracker is a failure, and the failure is specific: it names the tag, the trigger, and the script that loaded it. Then change the consent choice and watch again, because tags that reload themselves after a change are a separate failure. Then navigate to a second page and watch again, because single-page apps re-fire tags on route changes. The audit is three watches, not one, and the tags that fail the second or third watch are the ones the first audit missed. The [withdrawal button nobody tests](2026-11-12-consent-withdrawal-button-nobody-tests.md) is the same gap: the choice exists, the mechanism to honor it does not, and nobody checked.

## The fix is per-tag, not per-banner

Every tag gets a consent condition in the tag manager, checked before it fires and re-checked when the consent state changes. Scripts loaded by other scripts get audited end to end, because the consent check on the first script does not reach the tracker the second script loads. The banner collects the choice. The tags enforce it. A platform that claims to enforce consent without per-tag checks is selling the banner, not the control, and the network tab is the test that proves it.

## Frequently asked questions

### Does Consent Mode v2 govern all my tags?

No. Consent Mode governs Google's tags. The Meta Pixel, TikTok, LinkedIn, and every custom HTML tag fire on their triggers whatever the signals say, unless each one gets its own consent check. Consent Mode is a Google mechanism, not a universal one.

### How do I audit which tags fire after consent is denied?

Deny all consent, load the page, and watch the network tab. Any request to a known tracker is a failure. Then change the consent choice and watch again: tags that reload themselves after a change are a separate failure, because the choice has to stick.

### Why does a tag fire even though the tag manager has a consent check?

Because the tag manager container loads a script, and that script loads another script, and the second script loads the tracker. The consent check was on the first script. The tracker never saw it. The chain has to be audited end to end, not just at the first link.

### Does my consent platform enforce consent, or just collect it?

A consent management platform collects the choice and stores it. It does not enforce it. Enforcement is per tag, in the tag manager or in the tag itself. A platform that claims to enforce consent without per-tag checks is selling the banner, not the control.