Skip to main content
All CollectionsBringing Data InConnectionsAdvertising Connections
Syncing Segments with Custom Audiences in Advertising Connections: Deep Dive
Syncing Segments with Custom Audiences in Advertising Connections: Deep Dive
Updated over a week ago

BlueConic has many advertising connections that allow synchronizing BlueConic segments to custom audiences in the ad platform. This enables users to run advertising campaigns that are powered and orchestrated by the BlueConic platform. Using one platform, such as BlueConic, as the source of truth for advertising campaigns ensures that the correct profiles are always targeted, drives higher conversion rates, and increases return on ad spend (ROAS). Some of the most common advertising connections in BlueConic include Facebook Advertising, Google Ads, Twitter Ads, and The Trade Desk, but a complete list can be found below.

Depending on the advertising platform, some connections have different methods to connect. For example, Facebook Advertising has the additional option to export to the conversion API or to use a client-side pixel integration.

How to set up and configure Advertising Connections in BlueConic

For instructions on setting up the advertising connections in BlueConic, see the Advertising Connections section.

Mapping fields in advertising connections

When mapping a BlueConic segment to a custom audience, the process is similar for each advertising platform (depending on whether you want to create new custom audiences or add information to existing custom audience profiles) and involves linking unique identifiers and segment mapping like pictured below.

The matching step is typically sent hashed to the advertising platform and is used to find corresponding users. Fields that can be used for matching depend on the API of the advertising platform. For example, Facebook has the option to match profiles based on email, phone number, first name, last name, city, state/province, country, zip/postal code, date of birth, gender, and mobile advertiser ID. The number of matched profiles is typically lower than the number sent to the platform as not every profile will have a Facebook account, Facebook may have different identifiers on file, or profiles don’t have the required identifiers.

The mapping flow of all advertising connections is the same and can described as follows:

  • Export: For each configured segment…

    • Get profiles of the segment that have not been sent yet or have a last modified date more recent than the last connection run date. When the matching settings are changed, all profiles are sent.

    • Convert the profile to the data the advertising platform expects, including any hashing of values.

    • Send the data to the advertising platform in batches.

  • Cleanup: For each configured segment…

    • Get all profiles that have been sent to the advertising platform and specific audience, and are not currently part of the segment.

    • Convert profiles to expected data and send them to the advertising platform to remove them from the audience.

Available mapping fields by connection

Connection

Matching fields

Encryption

API

  • email

  • phone number

  • first name

  • last name

  • city

  • state

  • country

  • zip code

  • first initial

  • gender

  • birth date

  • mobile advertiser ID

SHA-256

/{audience_id}/users

  • email

  • phone number

SHA-256

offlineDataJobOperations.generateCreateUserOperations

  • email

SHA-256

GetBulkUploadUrl

  • mobile advertiser ID

  • external user ID

  • cookie

none

/v2/dp/audience

  • email

  • phone number

  • mobile advertiser ID

SHA-256

segments/{audienceId}/users

  • email

  • device ID

  • handle

  • partner user ID

  • Twitter ID

SHA-256

custom_audiences/{audienceId}/users

  • email

SHA-256

dmpSegments/{audienceId}/users

  • email

  • phone number

  • GAID

  • IDFA

SHA-256

/dmp/custom_audience/update/

  • email

  • mobile advertiser ID

  • identity link

MD-5

audiences/{audienceId}/contactlist

  • The Trade Desk ID

  • device ID

  • UID 2.0

  • LiveRamp ID

none

/data/advertiser

Did this answer your question?