Optimize ad delivery with targeted in-sync audiences
The Google Ad Manager 360 destination allows you to batch upload identifiers to audience segments in bulk by sending your desired segments to Google Cloud (in an Ad Manager cloud storage bucket) as a CSV file, which can then be used in GAM 360.
To see an example of an exported file, scroll to the bottom of this page.
Before you can use Hightouch to batch upload your identifiers to GAM 360, ensure that the following steps have been completed, 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.
Once your account manager has completed your setup, you'll be ready to create the file of identifiers you want to upload.
To get started with our GAM 360 destination, select your Google Cloud credential (service account). If you need to create a cloud credential, consult our documentation.
Then, you will need to enter GCP Project ID and GCS Bucket Name. The "GCS Bucket Name" should just be the name of the bucket, not a URL.
Once you've done this, ensure you run the command to grant Hightouch's service account the correct permissions.
- All - All Mode creates a CSV file with all the rows in the query results, every time the sync is run.
- Insert - Insert mode creates a CSV file with the rows that were added since the last sync.
- Diff - Diff mode creates 3 CSV files with rows (1) added, (2) changed, and (3) removed since the last sync.
The GAM 360 destination as well as the batch upload process supports several different identifier types.
In the first mapping section, select the column corresponding to the list of identifiers you would like to batch upload (on the left), and on the right select the type of identifiers that are being uploaded to each segment.
The types supported are shown below.
In the next section, you will need to denote the audience segment ID(s) with which the identifiers from the previous section should be associated. Here, you can either specify a column from your model (to associate each identifier with a different segment) or a singular value (to associate all identifiers with the same segment). Use the toggle on the right of the field in sync configuration to flip between these two options.
The file name field will allow you to specify the prefix and the name of the file that you want to use for your results. In the screenshot below, we've specified that we want the file to be called results.csv, with a custom prefix.
If you've selected
Diff mode, you'll be prompted for 3 file names (for added, changed, and removed). If
any of these 3 are left blank, that subset of rows will be ignored.
You can also timestamp variables in the file name, surrounding each with
We currently support these timestamp variables: YYYY, MM, DD, HH, mm. All dates and times will be UTC.
You can also set a File Name Timestamp Offset. By default, the date/time used to generate the file name (above) is the date/time that the sync takes place; you can enter a number of seconds to offset this (offset can be positive or negative).
Ex. To set the date in the file name to 24 hours before the sync takes place, input
-86400. The default offset is
If a file at that path already exists at the time of a sync, Hightouch will overwrite it. To keep different versions of the same results file, you can enable versioning in your bucket, or your application can copy the data to another location.
This destination will not respect any sorting that you have in your model. It will export results file sorted by ID.
Example file content for encrypted cookie IDs:
cookie_encrypted,list_id ScpJKu-yV8je93qkd32MOA,3153490 w2gsrUcwxF-OiJTRmQswQA,3153490
Example file content for raw AdIDs:
cookie_adid,list_id 38400000-8cf0-11bd-b23e-10b96e40000d,3153490 38400001-8cf1-11be-b23f-10b96e40000e,3153490