Google is releasing changes to the Google Ads API, Customer Match, and the Display & Video 360 API in order to support the compliance and consent-related requirements defined under the Digital Markets Act (DMA) in the European Union (EU User Consent Policy). Enforcement of these changes to consent requirements is live as of March 6, 2024.
To adhere to the EU user consent policy and continue creating audience lists for users in the European Economic Area (EEA), advertisers and partners must ensure they are passing end-user consent when uploading audience data. As a Google Partner, Adobe provides you with the necessary tools to comply with these consent requirements under the DMA in the European Union.
Customers who have purchased Adobe Privacy & Security Shield and have configured a consent policy to filter out non-consented profiles do not need to take any action.
Customers who have not purchased Adobe Privacy & Security Shield must use the segment definition capabilities within Segment Builder to filter out non-consented profiles, in order to continue using the existing Real-Time CDP Google Destinations without interruption.
The Google Ad Manager 360 connection enables batch upload for publisher provided identifiers (PPID) into Google Ad Manager 360, via Google Cloud Storage.
For more details on how publisher provided identifiers work in Google Ad Manager 360, see the official Google documentation.
This destination is currently in Beta and is only available to a limited number of customers. To request access to the Google Ad Manager 360 connection, contact your Adobe representative and provide your organization ID.
The Google Ad Manager 360 destination exports CSV files to your Google Cloud Storage bucket. Once you’ve exported the CSV files, you must import them into your Google Ad Manager 360 account.
Note the following details that are specific to Google Ad Manager 360 destinations.
This integration supports the activation of identities described in the table below.
Target Identity | Description | Considerations |
---|---|---|
PPID | Publisher provided ID | Select this target identity to send audiences to Google Ad Manager 360 |
This section describes which types of audiences you can export to this destination.
Audience origin | Supported | Description |
---|---|---|
Segmentation Service | ✓ | Audiences generated through the Experience Platform Segmentation Service. |
Custom uploads | ✓ | Audiences imported into Experience Platform from CSV files. |
Refer to the table below for information about the destination export type and frequency.
Item | Type | Notes |
---|---|---|
Export type | Profile-based | You are exporting all members of a segment, together with the applicable schema fields (for example your PPID), as chosen in the select profile attributes screen of the destination activation workflow. |
Export frequency | Batch | Batch destinations export files to downstream platforms in increments of three, six, eight, twelve, or twenty-four hours. Read more about batch file-based destinations. |
Allow-listing is mandatory before setting up your first Google Ad Manager 360 destination in Platform. Make sure to complete the allow-listing process described below, before creating your destination.
The exception to this rule is for existing Audience Manager customers. If you have already created a connection to this Google destination in Audience Manager, then it is not necessary to go through the allow-listing process again and you can proceed to the next steps.
To connect to the destination, you need the View Destinations and Manage Destinations access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
To connect to this destination, follow the steps described in the destination configuration tutorial. In the destination configuration workflow, fill in the fields listed in the two sections below.
To authenticate to the destination, fill in the required fields and select Connect to destination.
For more information about these values, see the Google Cloud Storage HMAC keys guide. For steps on how to generate your own access key ID and secret access key, refer to the Google Cloud Storage source overview.
To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
AdX buyer
for Google AdXDFP by Google
for DoubleClick for PublishersAudience Name (Audience ID)
.You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.
When you are finished providing details for your destination connection, select Next.
See Activate audience data to batch profile export destinations for instructions on activating audiences to this destination.
In the identity mapping step, you can see the following pre-populated mappings:
Pre-populated mapping | Description |
---|---|
ECID -> ppid |
This is the only user-editable pre-populated mapping. You can select any of your attributes or identity namespaces from Platform and map them to ppid . |
metadata.segment.alias -> list_id |
Maps Experience Platform audience names to audience IDs in the Google platform. |
iif(${segmentMembership.ups.seg_id.status}=="exited", "1","0") -> delete |
Tells the Google platform when to remove disqualified users from segments. |
These mappings are required by Google Ad Manager 360 and are automatically created by Adobe Experience Platform for all Google Ad Manager 360 connections.
To verify if data has been exported successfully, check your Google Cloud Storage bucket and make sure the exported files contain the expected profile populations.
In case you encounter any errors while using this destination and need to reach out to either Adobe or Google, keep the following IDs at hand.
These are Adobe’s Google Account IDs: