This article describes how to set up the Criteo Audience Match (Deprecated Marketing API v1) connector in your Customer Data Hub account.

In this article:

Connector Actions

Action Name AudienceStream EventStream
Add User to Audience
Remove User from Audience

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

  • Advertiser ID
    • Required.
    • Your Advertiser ID associated with an integration in your Criteo account. 
    • To use the Criteo Audiences Connector. Send an email to "asintegrations@tealium.com." and we will email back a consent link that authorizes us to manage audiences on behalf of advertisers. Learn about sending an authorization request to users.

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Add User to Audience

Parameters

Parameter Description
Audience
  • Select an audience to add user to or provide an Audience ID directly.
Email
  • Send email value as-is without applying built-in hashing.
  • Select this option if value requires no hashing or is already hashed.
Email (apply MD5 hash)
  • Hash email value with MD5 before sending.
Email (apply MD5 SHA256 hash)
  • Hash email value with MD5 and then SHA256 before sending.
Mobile ID
  • IDFA mobile ID for Apple.
  • ADID mobile ID for Android.
Identity Link
  • Identity Link
Gum ID
  • Identifier obtained from cookie matching.
  • A corresponding Gum Caller ID is automatically added to the request.

Action - Remove User from Audience

Parameters

Parameter Description
Audience
  • Select an audience to remove a user from or provide an Audience ID directly.
Email
  • Send email value as-is without applying built-in hashing.
  • Select this option if value requires no hashing or is already hashed.
Email (apply MD5 hash)
  • Hash email value with MD5 before sending.
Email (apply MD5 SHA256 hash)
  • Hash email value with MD5 and then SHA256 before sending.
Mobile ID
  • IDFA mobile ID for Apple.
  • ADID mobile ID for Android.
Identity Link
  • Identity Link
Gum ID
  • Identifier obtained from cookie matching.
  • A corresponding Gum Caller ID is automatically added to the request.
Version history
Last update:
5 hours ago
Updated by: