This article describes how to set up the Twitter Custom Audiences connector.

In this article:

API Information

This connector uses the following vendor API:

Batch Limits

This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met:

  • Max number of requests: 1000
  • Max time since oldest request: 60 minutes
  • Max size of requests: 2 MB

Connector Actions

Action Name AudienceStream EventStream
Add User To Custom Audience
Remove User From Custom 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:

  • Ad Account ID
    • Required.
    • Provide your Twitter Ad Account ID.
    • Your Account ID can be located in your account's URL when logged in.
    • Example: If the URL is https://ads.twitter.com/accounts/1234abcd/, the account ID is 1234abcd.

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 Custom Audience

Parameters

Parameter Description
Custom Audience
  • Required
  • Select audience from list.
  • For more information, see Custom Audiences.
Device ID
  • User Device ID.
Email
  • User Email.
Partner User ID
  • Partner User ID.
Phone Number
  • User phone number.
Twitter Handle
  • User Twitter handle.
Twitter ID
  • User Twitter ID.
User Identifier Hashing
  • All user identifiers except "Partner User ID" must be hashed using SHA256 hashing methods and normalized.
  • If the checkbox is unchecked, CDH will normalize and hash the mapped value.
Effective At
  • Membership option.
  • The UTC time at which the custom audience associations should take effect.
  • Expressed in ISO 8601.
  • Defaults to the current date and time.
  • A millisecond (MS) since epoch timestamp may be provided, and will be formatted correctly.
Expired At
  • Membership option.
  • The UTC time at which the custom audience associations should expire.
  • The specified time must be later than the value of "Effective At".
  • Expressed in ISO 8601.
  • Defaults to your configured default expiration period, which is typically 30 days or 720 hours from the value of "Effective At".

Action - Remove User From Custom Audience

Parameters

Parameter Description
Custom Audience
  • Required
  • Select audience from list.
  • For more information, see Custom Audiences.
Device ID
  • User Device ID.
Email
  • User Email.
Partner User ID
  • Partner User ID.
Phone Number
  • User phone number.
Twitter Handle
  • User Twitter handle.
Twitter ID
  • User Twitter ID.
User Identifier Hashing
  • All user identifiers except "Partner User ID" must be hashed using SHA256 hashing methods and normalized.
  • If the checkbox is unchecked, CDH will normalize and hash the mapped value.
Effective At
  • Membership option.
  • The UTC time at which the custom audience associations should take effect.
  • Expressed in ISO 8601.
  • Defaults to the current date and time.
  • A millisecond (ms) since epoch timestamp may be provided, and will be formatted correctly.
Expired At
  • Membership option.
  • The UTC time at which the custom audience associations should expire.
  • The specified time must be later than the value of "Effective At".
  • Expressed in ISO 8601.
  • Defaults to your configured default expiration period, which is typically 30 days or 720 hours from the value of "Effective At".
Public