Export audiences
Overview
In this destination service, DinMo will create audiences and keep them up to date in Google Ads.
To do so, you will need to go through these three steps:
Creating a Google Ads destination. Refer to the corresponding section for more info.
Creating a user segment composed of all the users that will populate your Google Ads audience. Refer to this step-by-step tutorial to learn how to build segments without SQL in DinMo.
Activating the segment to the Google Ads destination to start sending data. Refer to the corresponding section for more info.
Each time the activation will be running:
Any new user entering your DinMo segment will be added to your Google Ads audience
Any user leaving your DinMo segment will be removed from your Google Ads audience
Note that only users who have an identifier (phone number or email address) linked to a Google account will be present in your Google Ads audience.
Destination setup
To start exporting audiences, you are first required to create a Google Ads destination with the corresponding destination service.
You will need to specify the ad account in which your audience will be created, and the data type to be sent to Google Ads. contact_info is the most popular choice and is used for managing contacts identified by emails or phone numbers.
Note: If the ad account you seek is not listed, it means that the user who connected DinMo to Google Ads does not have the permissions for this account.
Optional: Setup default activation settings
At the end of the destination creation, you will be proposed to setup Default Activation Settings. This step is optional, but is highly recommended to facilitate the activation process.
By configuring default settings, synchronizing all your audiences to Google Ads will just take one click. Without default settings, you will be required to go through the configuration each time you activate a new audience.
Note that even if you setup default settings, you will still be able to adjust activation settings for each of your audiences if you wish to.
Refer to the Activation configuration section for more info about the default settings configuration process.
Activation configuration
Once the destination has been setup, and your DinMo segment created, you can create an activation to start sending data to Google Ads right away. The segment will be exported as a new audience in Google Ads.
Activation Name and Description
In this section, the name you enter will be the name given to the audience created in Google Ads. You may also optionally enter a description, that will be attached to the audience in Google Ads.
By default, and if you activate your segment using the default activation settings, the name of the audience will be the DinMo segment name, and the description will be the DinMo segment description.
User consent
Since early 2024, it is mandatory to send user consent modes to Google Ads for:
Ad user data
Ad Personalization
Failure to comply will result in Google stopping the processing of the data you send.
Google Ads only enable to apply consent modes to the entire customer list you send, and not at a user granularity. You must fill in the two consent fields. Make sure the segment you are synchronizing to Google Ads respect the user consent policy.
Fields mapping
In the Fields mapping section, you are asked to specify the meaning of the fields of your segment that you wish to send to Google Ads. Any non mapped fields in your segment will not be sent to Google Ads.
Google Ads will use the fields you send to recognize each user of your segment. The higher the number of fields you send, the most likely Google will be able to identify the users.
You can map the following fields:
Email (Required): The email addresses of the users. It can be in clear text, or hashed (SHA-256)
Phone: The phone numbers of the users. E164 format is preferred ('+49xxxxxxxx'). It can be in clear text, or hashed (SHA-256)
First Name: It can be in clear text, or hashed (SHA-256)
Last Name: It can be in clear text, or hashed (SHA-256)
Postal Code: It can be in clear text, or hashed (SHA-256)
Country Code: 2-letter country code in ISO-3166-1 alpha-2 of the user’s address. It can be in clear text, or hashed (SHA-256)
State: It can be in clear text, or hashed (SHA-256)
City: It can be in clear text, or hashed (SHA-256)
Tips to improve matching:
If your user list contains an invalid email, Google Ads will require additional attributes to identify the user, otherwise this record will be rejected.
In this instance, you have two options for giving Google Ads the minimum required information, by adding one of the following:
Phone
A combination of first name, last name, and address (minimum postcode/zip code and country code)
Of course, the more attributes you add the better the matching. However, adding one of these two gives Google Ads sufficient information to identify these users, and means the records will not be rejected during the activation.
Scheduling
In this section, specify how often the audience should be updated in Google Ads. Every time the audience is updated:
Any new user having entered your DinMo segment since the last update will be added to your Google Ads audience
Any user having left your DinMo segment since the last update will be removed from your Google Ads audience
Last updated