Google Ads API v15 Update

Google Ads API v15 is now available through the Ad Audiences node. To use it, you must collect the two consents Google requires for Customer Match integrations.

The two required consents are:

• ad_user_data: Controls whether personal data is sent to Google services, such as Google Ads and YouTube Ads, based on user consent.
• ad_personalization: Controls whether personal data can be used for purposes such as retargeting.

Both consents must be set to Granted for Customer Match to add a customer to an audience.

How it works

When a customer reaches the Ad Audience node, the node checks the consent categories you've specified in the Consent category section. The process continues only if the customer has granted the required consent. A Customer Match with both consents granted is then called for those customers.

Consent categories don't need specific names — Google doesn't manage them. You're responsible for filtering out customers without the correct consent before they reach the node. Customers sent to Google without the required consents will be inaccurately targeted.

Most customers don't need to make any changes — existing consent settings already cover both required categories. If you use more granular consent settings, manually filter customers to meet Google's requirements.

Filter customers with granular consent settings

If you collect consent at a more detailed level — for example, per customer and per platform — use a Scenario with a Condition node to filter out customers before they reach the Ad Audience node.

The language and consent options in your banners must align with Google's policies. This is your responsibility to maintain.