The consent banner that wasn't blocking anything

US state privacy laws keep arriving, and the standard response is a consent platform. The banner appears, the visitor chooses, everyone moves on. A store we look after had exactly that, a proper consent app configured for the states that require one, banner rendering, choices being recorded.

What we found

We counted how many scripts the page was actually holding back before consent. The rendered page is checkable from the outside, so this is not a matter of opinion. The count was zero. Every marketing and analytics tag loaded the moment the page did, whatever the visitor chose. The banner was collecting choices that nothing was listening to.

This is more common than you’d hope. Consent platforms automatically block the scripts they recognise, but tags added through the theme, custom pixels and app embeds keep loading unless each one is explicitly gated. Installing the app is the visible step. Gating the scripts is the step that makes it real.

We gated each tag so it waits for the visitor’s answer, tested the lot on a development theme first, then shipped it and re-checked the live page the same way we checked it at the start. Four tags now hold until consent is given, including the email platform’s tracking.

What to take from it

A consent banner is the visible part of compliance, not the working part. The question worth asking is how many scripts your storefront blocks before consent, and it has a hard number as an answer. If nobody has ever measured it, it is worth measuring, because a banner over an ungated page is doing very little beyond looking responsible.