You can now use the new Google Ads API v15 via the Ad Audiences node in Bloomreach Engagement. However, before using it, make sure you have the two necessary consents, as introduced by Google for the Customer Match integration when adding customers to the audience.

The two consents on the Google Ads API side are:

• ‘ad_user_data’ - The ad_user_data setting determines whether personal data is sent to Google based on user consent. “Google” in this context refers to services like Google Ads, YouTube Ads...
• ‘ad_personalization’ - The ad_personalization setting controls whether personal data can be used for purposes such as retargeting.

In order for Customer Match (and the Bloomreach Engagement Ad Audiences node) to add a customer to an audience, both consents need to be set to Granted.

How it works

When a customer reaches the Ad Audience node, and it's necessary to add them to the audience (Action to perform), Engagement uses the consent specified in the Consent category section of the node to filter the customer. The process continues only if the customer has granted this consent. Then, a Customer Match with both consents granted is called for the customers.

🚧

This doesn't result in the automatic creation or tracking of two consent events on the Bloomreach Engagement side. Rather, it signifies to Google that both consents are granted when making the API call. You are responsible for ensuring that this node gets called only for customers with the correct consents.

Bear in mind that it's your responsibility to ensure that the language and consent in your banners align with Google's policies.

If you capture consents in more detail - for instance, gathering retargeting consent for individual customers as well as specific platforms (like Google) - you should use a Scenario. Implement a Condition Node to filter out customers before reaching the Ad Audience node.