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 IMS 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.
|PPID||Publisher provided ID||Select this target identity to send audiences to Google Ad Manager 360|
Refer to the table below for information about the destination export type and frequency.
|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.|
The allow list is mandatory before setting up your first Google Ad Manager destination in Platform. Please ensure the allow list process described below has been completed by Google before creating a destination.
Google has simplified the process to connect external audience management platforms to Google Ad Manager 360. You can now go through the process to link to Google Ad Manager 360 in a self-service manner. Read Segments from data management platforms in the Google documentation. You should have the IDs listed below at hand.
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.
DFP by Googlefor DoubleClick for Publishers
AdX buyerfor Google AdX
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 audience segments to this destination.
In the identity mapping step, you can see the following pre-populated mappings:
||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
||Maps Experience Platform segment names to segment IDs in the Google platform.|
||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.