DinMo Documentation
  • πŸ“™Core Concepts
  • Guides
    • ⚑Get started with DinMo
      • Initial Configuration of DinMo
        • Connect a Source
        • Create your Models
        • Create a Destination
      • Create and Activate Segments on DinMo
        • Create your first Segment
        • Activate your first Segment
    • 🌐Workspaces & Organizations
    • πŸ’­Need Help?
  • Integrations
    • Data Sources
      • AWS Redshift
      • Databricks
      • Google BigQuery
      • PostgreSQL
      • Snowflake
    • Destination Platforms
      • Actito
        • Synchronize users attributes
        • Export contact lists
      • All My SMS
      • Attentive
        • Synchronize Users
      • Batch
        • Synchronize contacts (MEP)
        • Synchronize profiles (CEP)
        • Send events (CEP)
      • Braze
        • Synchronize users attributes
        • Send track events
        • Synchronize subscription statuses
        • Export user lists
      • Brevo
        • Synchronize contacts
        • Export contact lists
      • Criteo
        • Export contact lists
      • Dialog Insight
        • Synchronise Contacts
      • Dotdigital
        • Synchronize contacts
      • Emarsys
        • Export contact lists
        • Synchronize contacts data
        • Synchronize custom table's data (RDS)
      • Firestore
        • Create and update Collection Documents
        • Export Audiences
      • Google Ads
        • Export audiences
        • Enhanced Conversions for Web
        • Upload click or offline conversions
          • Prerequisites and walkthrough
        • Adjust conversion events
        • Retract conversion events
      • Google Display & Video 360
        • Export audiences
      • Google Search Ads 360
      • Hubspot
        • Synchronize objects
      • Intercom
        • Export segments
        • Synchronize contacts
        • Synchronize companies
      • Iterable
        • Synchronize user attributes
        • Export contact lists
      • June Email Marketing
        • Export Contact Lists
      • Klaviyo
        • Export contact lists
        • Synchronise contacts
        • Create subscription list
      • LinkedIn Ads
        • Export user audiences
        • Export company audiences
      • Mailchimp
        • Export segments
      • Meta Ads
        • Export audiences
        • Send conversion events
      • Microsoft Ads (Bing)
        • Export audiences
      • Pinterest Ads
        • Export audiences
        • Send conversions
      • Reddit Ads
        • Export Audiences
      • Salesforce Marketing Cloud
        • Synchronize data extensions
      • SendGrid
        • Synchronize contacts
        • Export contact lists
      • Selligent
      • SFTP
        • Export your data models and segments
      • Snapchat Ads
        • Export Audiences
      • Splio
        • Synchronize contacts
      • TikTok Ads
        • Export Audiences
        • Send Offline Conversions
        • Send Web Conversions
      • X (Twitter)
        • Export audiences
      • Zendesk
        • Synchronize users
        • Synchronize custom objects' data
  • Models
    • Overview
    • Primary Keys
      • Detect duplicate primary keys
    • Calculated Fields
  • Identity resolution
    • Overview
  • Segments
    • Visual Builder
    • Breakdowns
    • Overlap Analysis
  • Activations
    • Overview
    • Sync Scheduling
    • Troubleshooting Syncs
      • Automatic pause or resume Activations
      • Sync warnings
  • AI PREDICTIONS
    • Overview
    • LTV and Churn
    • Product Recommendations
  • WORKSPACE MANAGEMENT
    • Set Up
    • Managing Users & Roles
    • Audit Logs
    • Enterprise Single Sign-On (SSO)
  • Security & Privacy
    • Overview
    • Networking
    • Privacy
    • Data Processing
Powered by GitBook
On this page
  • Overview
  • Destination setup
  • Optional: Setup default activation settings
  • Activation configuration
  • Activation Name and Description
  • User consent
  • Fields mapping
  • Scheduling
  1. Integrations
  2. Destination Platforms
  3. Google Ads

Export audiences

PreviousGoogle AdsNextEnhanced Conversions for Web

Last updated 2 months ago

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 for more info.

  • Creating a user segment composed of all the users that will populate your Google Ads audience. Refer to this 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 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

Learn how to create such a destination in our

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.

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.

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

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 each time you activate a new audience.

Refer to the for more info about the default settings configuration process.

Learn how to activate a segment in our

step-by-step tutorial
step-by-step tutorial
step-by-step tutorial
corresponding section
corresponding section
configuration
Activation configuration section