Client Defined Segments

CrowdTwist has the ability to create segments based on a predefined list of CrowdTwist member IDs via an upload process that utilizes a client-specific directory on the CrowdTwist SFTP. Speak with your dedicated support team to discuss specific use-cases that are relevant to your program.

Documentation

CrowdTwist requires the file of members to be formatted with the following criteria:

  • A column named CTUserID (case insensitive). Any additional columns will be ignored.

  • A list of one or more CrowdTwist User IDs in the CTUserID column.

  • File should be saved as a CSV with UFT-8 encoding and without field enclosures.

Example: 

CTUserID
54602377
54600375
54600597
54602359
58249083
54615470
58813384
CTUserID
54602377
54600375
54600597
54602359
58249083
54615470
58813384

The file naming convention is as follows:

[CUSTOM_SEGMENT_NAME]_YYYYMMDD_[SEGMENT_VERSION].csv

Ex: SPECIAL_PROMOTION_20180914_0001.csv

Notes on the file naming convention:

  • [SEGMENT_VERSION] represents the iteration of the segment, is recommended to start with 0001 if it is the first version of the segment, but not required as long as the next segment on the same day has a higher version number. For instance, the first version could be 1205 and the second could be 1643.
  • [SEGMENT_VERSION] should always be 4 numerical characters.
  • If the client would like to update a previously processed segment on the same date as the first upload, the [SEGMENT_VERSION] should be incremented and re-uploaded to the SFTP (i.e., 0002, 0003, 0004, etc.). If the second iteration of the same segment is updated on a different day, the YYYYMMDD date should be changed to the date that the segment is uploaded, but the SEGMENT_VERSION can reset back to 0001 (or any other number with the need for the next version be higher).
  • [CUSTOM_SEGMENT_NAME] should have underscores (_) where whitespace should appear in the segment name on Control Center (i.e., SPECIAL_PROMOTION = SPECIAL PROMOTION in Control Center)

  • Any subsequent file, which updates the segment will replace entries in the initial file. Therefore, to append new set of users in a segment, it is necessary to include the initial set of users from the first file. Any users not in the subsequent file will be considered not in the segment in the current iteration of the segment.

File Validations: 

  • Maximum supported file size is 128Mb

  • Duplicate entries in the file will be automatically removed.

  • If there are non-numeric entries in the CTUserID column, we do not process the file and the file is marked as failed.

  • In case a CTUserID value does not exist in the platform, the User ID is accepted and stored, Since the user is not on CT platform no action happens on the User ID if the segment is linked to a feature.

Uploading the segment to the SFTP: 

Segments should be uploaded to the segment directory on your defined SFTP directory. Before uploading files to this directory, confirm with your support team that client defined segments are enabled for your program’s instance. If you have any questions, please reach out to your dedicated support team.