Consent ModePrivacyGTM
Use case 05
Consent Mode v2 before any tag fires
All four consent signals are set before the container loads, including a cookieless ping when the visitor declines.
The situation
The banner recorded a choice after GA4 had already sent the first hit. Two of the four Consent Mode signals were never set. A reject stopped every Google tag, so Google received nothing it could model for the visits that declined.
What we implement
All four signals are set to denied before the container loads, with a default that follows the region. A rejected visit still sends a cookieless ping. The Meta pixel moves out of the theme and into the container, behind the same choice.
The result
The first hit carries a consent state. A visitor who declines is still visible to modeling, and marketing tags wait for the choice the banner records.