Configure a Touchpoint or Process box

When you configure a Twitter connector from a Touchpoint in Journey or a Process box in Campaign, you will see the following properties:

Property name Description
Ad Account ID The Twitter Ad account ID.
Contact Action The actions to perform on the custom audience list of Twitter. The possible options in the dropdown are "Upload users to a new Audience" and "Upload users to an existing audience".
Audience The Twitter audience to populate. This field would be a dropdown field and it would be enabled if contact action is selected as "Upload users to an existing audience".
Audience Name The custom audience list name. It would be enabled if contact action is selected as "Upload users to a new Audience".
Audience Description The custom Audience description. It would be enabled if contact action is selected as "Upload users to a new Audience".

The following fields are available on the field mapping screen as per Twitter specifications as follows and for more details related to data normalization, see Data Normalization:

Field name Description
Email Address

The Email Address.

Use all lowercase and remove leading and trailing spaces.

Example: support@twitter.com
Twitter Username

The Twitter Username.

Use all lowercase, do not include @, and remove leading and trailing spaces.

Example: jack
Twitter UserID

The Twitter UserID.

Use standard integers (0-9) only.

Example: 143567
iOS Advertising ID (IDFA)

The IDFA ID.

Use all lower-case letters with dashes.

Example: 4b61639e-47cc-4056-a16a-c8217e029462
Google Advertising ID (AdID)

The Ad ID.

Original format on device is required, not capitalized with dashes.

Example: 2f5f5391-3e45-4d02-b645-4575a08f86e
Android ID

The Android ID.

Original format on device is required, not capitalized without dashes or spaces.

Example: af3802a465767e36
Partner UserID The User's ID in the partner's system.
Note:
  • The maximum request body size of the Custom Audiences' Users API is 5,000,000 bytes.
  • The data provided in the users field of the request, except Partner UserID, must be hashed using SHA256.
  • Additionally, the final output hash must be in lower case. For example: 49e0be2aeccfb51a8dee4c945c8a70a9ac500cf6f5cb08112575f74db9b1470d.