What Is Pre-Consent Firing?

Pre-consent firing is when a tag or tracking pixel activates and transmits data in the moments before a consent banner has loaded or before a visitor has made a choice, a timing failure caused by a race condition between the CMP and other scripts loading on the page, rather than a deliberate configuration.

The failure here is almost never intentional: it’s a loading-order problem. If an analytics or advertising tag’s script loads faster than the CMP‘s banner script, it can execute and transmit data before the visitor has had any opportunity to consent. This happens in milliseconds during page load, so it’s invisible to someone watching the page render normally, and it won’t show up in an audit that only checks whether the banner displays correctly. It’s caused by a Race Condition (Tag Loading) and only shows up in network traffic captured through something like Consent Simulation.