Google announced in September that there would be upcoming changes to support the Digital Markets Act (DMA). Google is releasing changes to the Google Ads API and the Display & Video 360 API as quickly as possible so that our developers have time to make application changes before DMA starts being enforced, expected March 6, 2024. Review the EU user consent policy for a reminder on our consent requirements for users in the European Economic Area.
What should I change for the Google Ads API?
The Google Ads API v15 release introduced the Consent object for uploading consent with your data. This Consent is used across all uploads for call conversions, click conversions , Customer Match, and Store Sales. Here is where to set the Consent for each feature.
| Feature | Code change |
|---|---|
| Call Conversions | Set Consent for each call conversion event at CallConversion.consent. See the guide for details.
|
| Click Conversions | Set Consent for each click conversion event at ClickConversion.consent. See the guide for details.
|
| Customer Match | Set Consent for each Customer Match job at CustomerMatchUserListMetadata.consent. See the guide for details.
|
| Store Sales | Set Consent for each Store Sales event at UserData.consent. See the guide for details.
|
What should I change for the Display & Video 360 API?
The Display & Video 360 API will be releasing similar changes in the following months announced via this blog. Check back in the release notes for updates to existing versions and the Customer Match feature guide for updated implementation instructions.
Where can I get support?
If you have questions, reach out to us [email protected] for the Google Ads API or the support form for the Display & Video 360 API.
Nadine Wang, on behalf of the Google Ads API and Display & Video 360 API Teams