SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

What Are the Best Practices and Design Considerations for CSV Profile Uploads?

Question

What are the best practices and important considerations when using the Upload Profiles and Custom Traits feature for CSV uploads in Segment?

 

Product

Segment

 

Environment

Segment Console

 

Answer

When uploading profiles via CSV, follow these best practices:

  • Include an identifier column, such as email or anonymous_id, to ensure proper identity resolution.
  • Leave unknown values blank to avoid introducing bad data.
  • Use case-sensitive headers for custom trait columns.
  • Avoid trailing, leading, or multiple consecutive spaces in data fields.
  • Ensure column keys do not contain invisible Unicode Byte Order Mark (BOM) characters, which some text editors may add.
  • Consent preferences cannot be updated via CSV uploads; use a Segment Consent Preference Updated event for those changes.

 

Additional Information 

For more details and up-to-date guidance, refer to the official documentation on CSV uploads in Segment Engage

Have more questions? Submit a request
Powered by Zendesk