Google Additional Consent
Google Additional Consent (AC) covers Google ad partners that are not on the IAB Global Vendor List. The TCF can only signal consent for GVL vendors. Google created the AC string to fill the gap. OptSens encodes an AC string alongside the TC string.
What OptSens does on the wire
OptSens builds an AC string in the version 2 format:
2~{consented_ids}~dv.{disclosed_ids}
The disclosed IDs are every Google AC vendor you select. The consented IDs depend on the visitor's action:
| Action | Consented vendors |
|---|---|
| Accept all | All selected AC vendors |
| Reject all | None |
| Save choices | Per-vendor toggles from the banner |
The AC string is carried in the addtlConsent field of the
IAB TCF getTCData response. An AC string is only
valid next to a TC string. Google discards an AC string sent without one. AC runs together with TCF, not on its own.
How to enable it
Google Additional Consent requires a Pro plan or higher, and it depends on Google Consent Mode.
- Open the dashboard and select your domain.
- Go to Frameworks.
- Make sure Google Consent Mode v2 is on. The AC toggle is locked until it is.
- Toggle Google Additional Consent.
- Save, then open Vendors to select your Google AC vendors.
The list of Google AC providers refreshes daily. If a vendor is removed from Google's list, OptSens drops it from your selection and notifies you. See vendors.
How to verify it
Open your site from a region your geo rules serve in IAB TCF mode, then run this in the browser console:
window.__tcfapi('getTCData', 2, function (data, ok) {
console.log(ok, data.addtlConsent);
});
addtlConsent should hold a string starting with 2~. The IDs before ~dv.
are the vendors the visitor consented to. The IDs after dv. are all vendors
disclosed to them.