Question
What do I need to take into account when uploading a CSV file to update user traits?
Product
Twilio Segment
Environment
Segment Console
Answer
Keep the following guidelines in mind as you upload CSV files to Twilio Segment Engage:
- You can only upload
.csvfiles. - Files can’t be empty and must have at least one header and one row.
- You can’t have multiple columns with the same header.
- CSV files cannot exceed 1 million rows (plus one header row), 299 columns, or 100 MB in file size.
- You can only upload one file at a time.
- Add an identifier column or
anonymous_idin your identity resolution configuration. - Leave any unknown values blank to avoid bad data. Engage can create a user profile from a single identifier in your CSV.
- The template won’t include duplicate custom traits, traits with trailing, leading, or multiple consecutive spaces between characters, or unallowed characters.
- Custom traits column headers are case-sensitive. For example,
first Name,FIRST Name, andFirst Namewould all be different traits in the template. - Trailing, leading, or multiple consecutive spaces between characters are not allowed.
- The CSV uploader shares Unify product limits.
When saving the CSV file, make sure that it does not contain an invisible Unicode Byte Order Mark (BOM, \uFEFF) character at the beginning of the keys as some text editors or applications automatically add a BOM when saving a CSV file in UTF-8 to ensure compatibility with Unicode-aware programs.
Additional Information
For more information, refer to the CSV Uploader documentation.