Last month we announced new changes launching in Google Ads API v15 to enable customers to pass end-user consent when uploading data. Today we are adding similar fields to Display & Video 360 API v2 and v3 that you can use when uploading Customer Match audience members.

You must start sending consent signals when uploading Customer Match audience members by March 2024 to adhere to the EU User Consent Policy and continue using European Economic Area (EEA) user data to populate Customer Match audiences.

What’s changing?

The Display & Video 360 API has added a Consent object for uploading consent with your Customer Match data. The Consent object specifies two distinct types of consent. For the EEA user data to be used in Customer Match user lists, both types of consent must be granted to indicate that you have received user consent.

What should I do?

Consent signals are set for all users added in a single firstAndThirdPartyAudiences.create or firstAndThirdPartyAudiences.editCustomerMatchMembers request. Use separate requests to upload users with different consent signals.

Make the following updates to requests creating and updating Customer Match audiences of the following audience types:

Audience Type	Relevant update
CUSTOMER_MATCH_CONTACT_INFO	Set the consent field of the included ContactInfoList.
CUSTOMER_MATCH_DEVICE_ID	Set the consent field of the included MobileDeviceIdList.

We have updated the existing Customer Match feature guide with information on passing consent signals. Read our release notes for an itemized list of the changes.

Before using these new features, make sure to update your client library to the latest version.

Where can I get support?

If you have questions regarding these changes or need help with these new fields, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team