How to upload segment data into Google Ad Manager (GAM) 360 using Dataflow?
Optimize ad delivery with targeted in-sync audiences
The Google Ad Manager 360 (GAM 360) destination allows you to batch upload identifiers to audience segments in bulk by sending your desired segments to an Ad Manager cloud storage bucket. The segments appear as a CSV file, which you can then use in GAM 360.
Prerequisites
Before you can use Antsomi to batch upload your identifiers to GAM 360, ensure you've completed these steps, taken from Google Ad Manager Help:
Locate and submit your network code. Find your network code in Ad Manager under Admin -> Global settings -> Network code.
Ensure that you've created an active first-party audience segment with which you want to associate the identifiers. If you don't want this segment to collect users using your own inventory, select "Publisher Managed" as the Population method.
Expect to wait up for 24 hours from the time of segment creation to the time when you can perform batch upload.
Create a Google Group that contains all Google Accounts that will have access to upload and view files.
Inject your Antsomi Website SDK to your website source code.
If you haven't injected the Antsomi SDK, please follow these instructions.
In your website source code, include the following code snippets in the GAM360 function (in the function
googletag.cmd.push()
and before the statementgoogletag.enableServices();
).
The _cdpEventFunction
is a utility object from the Antsomi Website SDK, please kindly wait for the SDK script to be fully loaded and check for its existence before using it.
Once your account manager has completed your setup, you can create the file of identifiers you want to upload.
Connect to Google Cloud Storage (GCS)
Log into the CDP system. After logging in, click the menu in the left corner of the screen
Go to menu: DATAFLOWS -> Data Destinations
You can then authenticate Antsomi to Google Ad Manager 360 by entering your GCP Credentials.
If you need to create a cloud credential, consult the guide from Google documentation.
After validated successfully, input the Destination name and click the Connect button.
Prepare your Visitor Segments
Skip this step if you have your segment(s) already.
Please follow the steps in this document.
Prepare your Segment Data Source
Skip this step if you have your Segment Data Source already.
Please follow the steps in this document.
Create the upload file
Once you've set up your Google Ad Manager 360 Destination and have a Segment(s) Data Source to pull data from, you can set up your dataflow to begin syncing data.
Select the relevant Segment data source where you want to pull data from, then click Create dataflow.
1. Add Data
Select your desired segment(s) and the field "User ID".
2. Add Columns
In the next step, you need to denote the audience segment IDs with which the identifiers from the previous step should be associated. You need to specify a static value to associate all identifiers with the same segment.
List of identifiers
We only supports this identifier type of the GAM 360:
Identifier | Description | Source | Upload as |
---|---|---|---|
PPID | Publisher provided identifiers | Raw (external source) | ppid |
Input the column names, following this setup:
Column Name | Data Type | Formula |
---|---|---|
ppid | Text | Select the field "User ID" |
list_id | Text | Static value |
process_consent | Text | Static empty string: '' |
3. Select Columns
To ensure the uploading file is in the correct format that GAM360 can read and process, you need to specify only the required columns.
From the list of available columns, select 3 columns: "ppid", "list_id", and "process_consent".
4. Export data to GCS
The GCS destination lets you specify the bucket name, the parent directory, and the name of the file you want to use for your results.
You can include timestamp variables in the filename, surrounding each with {}
. Antsomi supports these timestamp variables:
timestamp
: Unix timestamp in milliseconds.year
: Represents the full year in four digits.month
: Two-digit month format (01-12).day
: Two-digit day format (01-31).hour
: Two-digit hour format in the 24-hour clock (00-23).minute
: Two-digit minute format (00-59).
All dates and times are GMT +8 (Singapore timezone).
If a file already exists at the path you entered at the time of a sync, Antsomi will overwrite it.
Example exported file
Example file content:
Last updated