Using Google Additional Consent

Update

Date

Updated to reflect the change in adding Google ATP Vendors

October 6th, 2020

Introduction

This document is intended to describe how to set up your Sourcepoint instance to work with Google's Additional Consent string. As Google joins the TCF v2 Framework (TCF v2) they have describe a way to handle consent for their sub-vendors that currently do not participate in the TCF v2. For Google's description of Additional Consent please refer to the following documentation provided by Google:

Key Concepts

In order to successfully integrate your Sourcepoint CMP with Google's Additional consent, there are a few key concepts to understand. These concepts include:

  • Google's ATP Vendors

  • Additional Consent String

  • TCData and TCInAppData

Google's ATP Vendors

Google's Ad Tech Partners (ATP) are vendors that Google may share data with. To make full use of of these partners, Google asks that you collect consent information for these vendors.

Some of these vendors will already be part .of the TCF v2. For these vendors, you do not need to send additional signals to Google. The standard consent information will apply.

There are, however, some ATP vendors that are not part of the TCF v2 Framework. For these vendors, Google asks that you collect consent from your users to allow these vendors to process their data. You will then pass an Additional Consent signal Google indicating that you have successfully collected consent from the user.

Google will be supplying the list of non-TCF v2 vendors that are part of their ATP program.

When passing user consent information to Google for the ATP vendors that are not part of the TCF v2, the mechanism you will use is the Additional Consent String. This string will be created and added automatically by your Sourcepoint instance if you have configured the integration successfully. The Additional Consent String will be added to the TCData, and TCInAppData objects respectively.

TCData and TCInAppData

These objects are what is normally used to communicate consent to TCF v2 participants. TCData is used for web, and TCInAppData is used for mobile environments. Google's Additional Consent spec calls for non-TCF v2 ATP vendor consent to be added to each of these respective objects to transmit appropriate consent signals.

Setting up Your Sourcepoint Integration

When Google Additional Consent was in Beta, there were some extra steps to set up the integration. Once Google joins the TCF v2, these steps are now eliminated.

You will have to take the follow steps to configure your integration:

It is much easier to set up ATP vendors once you have added the Google Ad Products Vendor to your Vendor List. We highly recommend doing this first.

  • Add the Google Ad Products (755) Vendor as an IAB TCF v2 vendor to your Vendor List.

  • Add the Google ATP vendors to the Vendor List of the Properties where you want to use Additional Consent.

Identify the Vendor List for the Properties or Property Groups you wish to activate

Select an appropriate property on which to activate the feature. Find the Vendor List for that Property or set of Properties.

Once you have identified the Vendor List, add the Google Ad Products vendor, if it isn't already there. Next search for and add the Google ATP Vendors you wish to use to your Vendor List.

Adding Google as an IAB TCF v2 Vendor to your Vendor List

You will need to make sure that Google Advertising Products is added to your Vendor List as an IAB Vendor. They can be added using the normal procedure to add IAB Vendors. Make sure the purposes and legal bases you wish to use for Google Ad Products is set correctly as these setting will be used to configure your ATP vendors also.

Adding the Non-TCF v2 ATP Vendors to Your Vendor List

To add ATP vendors, go to the Add Vendors button at the bottom of the TCF v2 Vendor List Builder.

Next, switch to the Custom ATP Vendors tab.

You should now see a section similar to this (note the vendors may be different) on the left side of the screen :

You can now select and all ATP vendors to add to your vendor list.

Click on the Configure Google ATP Purposes and Legal Basis setting

Inspect the purposes and legal bases configured and make sure they match your expectations.

You can either choose to use the defaults (Recommended), or uncheck the Use Google ATP Vendors box, make adjustments, and click apply.

Now save your changes as normal.

Your Vendor List should now reflect the changes you have made with the ATP vendors denoted with the G logo.

ATP Vendors added to the Vendor List

Save your Vendor List changes.

Don't forget to save your Vendor List. Even if you have added Vendors, they will not become active until you save your changes.

Configure your designated Property to use this Vendor List

How to Verify it is Working

Once you have set everything up and launched your privacy campaign on the property, you validate your setup by visiting the Property from the browser of your choice.

Go to the URL of your property and take the Accept All action from the first layer message.

You can now enter the console mode of the browser and execute the following command:

__tcfapi('getTCData', 2, function (tcData, success) {
console.log("GETTCDATA: ", tcData);
});

After executing the command, scan for the following text "addtlConsent"

You should see something like the below:

addtlConsent: "1~.482.486.440.2382.2710.1329.2729.1171.228.780.2351.1248.338.1230.2923.303.162.1126.1911.2179.3033"

Please refer to Google's technical spec posted above to decode the string.

The first section is the version of Additional Consent being used followed by a ~/.

The next section is dot separated list of IDs that should correspond to the list of ATP vendor IDs included in your Vendor List for the property.

Final Thoughts

If you have any issues, please reach out to your Sourcepoint Account Manager for help.