Segment export: Google Ad Manager
Prerequisite for implementation of Google Ad Manager (contact Meiro team to discuss details):
Locate and submit your network code. Find your network code in Ad Manager under Admin and then Global settings and then 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, mark the Audience pixel segment option. Expect to wait up for 24 hours from the time of segment creation
Create a Google Group that contains all Google Accounts that will have access to upload and view files. (link to link to Google documentation).
How to export your segmented customers to Google Ad Manager.
Prerequisites
Before you can upload the identifiers, work with your account manager to:
- Locate and submit your network code. Find your network code in Ad Manager under Admin and then Global settings and then Network code. The name of the Google Storage bucket where the segments will be uploaded `gdfp_cookieupload_[Ad Manager network code]`
- Ensure that you've created an active first-party audience segment with which you want to associate the identifiers.
Learn more: About prerequisites here.
How it works
After export in Meiro Business Explorer segments are loaded to the Google Cloud Storage bucket connected to the Google Ad Manager account. After the segment was loaded to the Google Cloud Storage bucket successfully Google loads the identifiers to the Audience and generates a log file in a separate Google Cloud Storage bucket in the next 24 hours.
The full process is explained in more details below.
Set up destination parameters
Google Ad Manager export destination has two parameters: Audience ID and Segment Name.
|
Audience ID (required) |
Refers to the ID of the Audience (or list_id) in Google Ad Manager to which segment should be loaded. |
|
Segments Name (required) |
The required parameter for organizing export files in the Google Cloud Storage bucket. Used for constructing prefixes for the files which contain identifiers from the exported segment. It is possible to modify the rules of constructing the prefix, the example of the full path can be: |
Segment export
After parameters are set and you export the segment, the CSV file with exported attributes is sent to Meiro Integration for further processing.
The format of exported segment:customer_entity_id, exported attribute_1, exported attribute_2,... , where exported_attribute_X is an attribute calculated for the identifier sent to Google Ad Manager. Google Ad Manager supported identifiers:
In the Meiro Integrations segment file is cleaned and prepared for the format required by Google Ad Manager: separate files for each identifier with 2 columns: `identifier, list_id`.
Find more about file format and requirements here in Google Ad Manager help article.
After processing files are exported to Google Cloud Storage bucket with the name gdfp_cookieupload_[Ad Manager network code]
What happens next?
After the segments were exported to Google Cloud Storage bucket in the next 24 hours Google Ads Manager will send the identifiers to the chosen Audience and generate the logs. The logs are being saved into gdfp_cookieupload_result_[Ad Manager network code]/ bucket with the same prefix and name as file with the identifiers and the suffix .fail or `.success`.
Important: most of the files will have `.fail` suffix, as files are named as `.success` only if all identifiers were uploaded successfully.
Important: each time Google Ads Manager makes a full load to the audience and resets the expiration settings for all identifiers.