Google Consent Mode v2, set by the banner your visitors answer.
Sadang sends Google tags a denied default before the visitor chooses, then an update with their choice. Here is exactly what it sends, and what we are still building.
Seven signals, three choices.
Sadang's banner asks for three things: analytics, personalisation and marketing. Six of Google's seven consent types follow one of them; security_storage is always granted. Choose an example on the right to see what Google tags receive.
The three advertising signals follow the single marketing choice: a visitor who allows marketing allows all three.
What Sadang sends, in order.
- A default, before any choice.
gtag('consent', 'default', …)withad_storage,analytics_storage,ad_user_data,ad_personalization,functionality_storageandpersonalization_storagedenied, andsecurity_storagegranted. It includeswait_for_update: 500(configurable) andads_data_redaction: true. - Region defaults, if you set them. One extra default per region list, so a site can, for example, treat visitors from different countries differently.
- Data layer markers.
IsConsentManagementPlatform: trueand aconsent_default_setevent, so Tag Manager can tell a consent platform is present. If the data layer has nogtm.domevent yet, Sadang also adds one. - An update, when the visitor chooses.
gtag('consent', 'update', …)with each type granted or denied to match their choice. Reject all sends every type denied exceptsecurity_storage.
Optional settings: url_passthrough (off unless you turn it on), ads_data_redaction (on unless you turn it off) and a Google developer_id.
Where we are.
We publish this list so you can see exactly what works today and what we are finishing before we apply to Google's CMP Partner Program.
| Capability | Status | Notes |
|---|---|---|
| Denied default before a choice | Live | All seven types; security_storage granted |
| Update when the visitor chooses | Live | Accept all, Reject all and custom choices in the banner |
| Update when consent is withdrawn | In development | Withdrawing does not yet send an update to Google tags |
| Reject all next to Accept all | Live | Same style, first layer of the banner |
| Region defaults (ISO 3166-2) | Live | Set in site configuration; dashboard setting in development |
| wait_for_update, ads_data_redaction, url_passthrough | Live | Configurable per site |
| Default sent before the banner's own set-up finishes | In development | Moving the default to the very start of the script |
| Stored choice re-sent on every page | In development | Returning visitors and visitors with Global Privacy Control currently get no signal from Sadang |
| Signals when another consent platform or a regional rule decides | In development | Visitors outside your configured regions, or with another consent platform's cookie, get no signal from Sadang today |
| Google Tag Manager Community Template | In development | See Google Tag Manager |
| Google CMP Partner Program | Not yet applied | We will apply when the items above are live |