Privacy and Measurement

Google consent mode and banner controls

Understand how BlackShield asks for consent, what Google consent signals are sent, and how visitors can revisit privacy settings after the initial choice.

Region-scoped defaults before Google config

BlackShield initializes Google consent mode before the Google tag config command runs, so analytics and advertising-related storage start denied for EEA, UK, and Switzerland traffic while other regions keep the non-banner default.

Banner choice is persisted

The first-party banner stores the visitor choice in a site cookie and replays that choice on later page loads, which keeps consent handling consistent across public pages and signed-in routes.

Safe fallback for unknown geography

If the hosting edge does not provide a country header, BlackShield falls back to showing the banner instead of assuming a non-regulated region.

What visitors can expect

When consent is granted, BlackShield updates Google consent mode for analytics storage plus the ad_user_data and ad_personalization parameters required by consent mode v2.
When consent is denied, Google-related analytics and advertising storage remain disabled and the stored preference is respected on future visits, even if the visitor later loads the site from another region.
BlackShield uses edge-provided country headers only to decide whether a first-visit banner should appear. Google still receives region-specific default consent commands in the tag bootstrap itself.