If any of the contacts you store in Emarsys and synchronized with a Google Audience are in the EEA and Switzerland, you need to collect consent statuses to show them the personalized ads.

If all of your contacts are outside the EEA and Switzerland, simply create two fields as described in the documentation and leave them empty. These will be synchronized with the "UNSPECIFIED" consent status, which will have no effect on non-EU users.

If all of your contacts are outside the EEA and Switzerland, simply create two fields as described in the documentation and leave them empty. These will be synchronized with the "UNSPECIFIED" consent status, which will have no effect on non-EU users.

All customers with active Google Connections get the notification, as we do not know whether an audience contains EEA and Switzerland contacts, or not.

For websites and apps, you can implement a consent banner or other custom consent solution, or use a Consent Management Platform (CMP). Learn more.

Yes. For data Emarsys uploads to Google using Customer Match (Audience sync), we need explicit user consent, even if it is set at another source.

For the data Emarsys uploads, Google will not rely on any external signals. So, if the Tag Manager on the customer's website sends a "DENIED" status, but we set it to "GRANTED", it will be considered as a grant for the EU and Switzerland user.

You need to update the Contact Fields with the corresponding value (similar to opt-in) in either of the following ways:

• You can use the API endpoint for this. See, Update Contacts: Emarsys Core API Reference.
• Or, if you are using other methods for updating Contact Data (Data imports or the Set Value node etc.) you can use these as well.

You must set the fields for each Google connection. You may set different fields or reuse the same fields, depending on your data strategy for consent handling.

This is also possible and long term would also reduce the customers' Digital Ads usage (billing).