Using Google Additional Consent

Note:

For information on Google Consent Mode, see Cookie Consent Integration with Google Consent Mode.

Google has created a temporary technical specification called Additional Consent Mode in order to serve as a bridge for vendors that have not yet registered for the IAB Europe Global Vendor List (GVL) but are on Google's Ad Tech Providers (ATP) list. This specification enables Universal Consent & Preference Management Providers (CMP) to gather and propagate additional consent along with their IAB TCF 2.0 implementation.

To enable Google Additional Consent

Attention:

Google Additional Consent will only be available for New Preference Center Template Design.



  1. On the Cookie Consent menu, select Templates. The Templates screen appears.

  2. Select the IAB TCF 2.0 template for which you would like to enable Google Additional Consent. The Template Details screen appears.

  3. Go to the Preference Center tab.
  4. Expand the Content section.
  5. Click the Edit icon next to Vendor List. The Vendor List modal appears.

  6. Enable the Use Google's Additional Vendors setting.
    Note:

    You can also rename the labels displayed to the user for the Google Vendors and the IAB Vendors in the Preference Center. For more information, see Customizing the Preference Center Template.



  7. Click the Save button.
  8. Save the template.

To configure Google vendors in the Vendor List

  1. On the Cookie Consent menu, select Vendors. The Vendor List screen appears.

  2. Select an IAB TCF 2.0 Vendor List. The Vendor Details screen appears.


  3. Click the name of the Google ATP vendor you would like to configure. A details pane appears.
  4. Click the Edit button.
  5. Change the Status to Active or Inactive.


  6. Click Save.
Note:

All Google ATP Vendors will be Active by default.

Make sure to republish your script after any Template or Vendor List changes.

The Google ATP list of vendors is updated weekly in Cookie Consent from the Google Additional Consent Storage. Find a link to the storage here.

Additional Consent String Technical Details

The addtlConsent (AC) string is available within tcData or InAppTCData objects. The AC string is only available after the user has given an explicit action to consent.

The AC string contains the following three components:

  1. A specification version number, such as "1".

  2. A separator symbol: "~".

  3. A dot-separated list of user-consented Google Ad Tech Provider (ATP) IDs. Example: "1.35.41.101".

The AC string is stored in a cookie called OTAdditionalConsentString. The expiration of the cookie is the same as the OneTrust cookies and also depends on the reconsent frequency defined in the associated Geolocation Rule.

To pass the AC String through the digital advertising chain