Customer.io

Export a person's data

Need to export the data associated with a single person? No problem!

Warning

Exports will include attribute and event data for the selected people. If this includes sensitive data, you must purge that data before passing it to customers.

Export data for a person

Head to the individual Person page for the end-user whose data you need to export, and select the ‘Export Profile Data’ option in the dropdown:

image.png

This will export the data that we have for a specific end-user. It may take a little while, but we’ll let you know when it’s done, and it will also appear on your Exports page like this:

There is a table titled Export. The first row shows the date of the export, that its a full customer export, the number of items exported, and the option to download the file.

Hover over the count of rows/items exported for more details.

That’s it!

Note

Note: You can also export the attributes for a user or group of users to CSV. This is available via the People page; here’s how!

What data we store

For each user, we store several types of data, all available for export:

  • All user attributes
  • User event data (for a person with a very large history, Customer.io may leave their oldest archived events out of the export)
  • All relationships to objects
  • User mobile device IDs, last_used timestamps, and platforms (if you’re sending us device data)
  • All deliveries for that customer, with their full content
  • Delivery metrics and metadata (delivery ID, the automation, message name, type, etc.)

What an export looks like

A single export will contain several different .json files for the above data types:

  • attributes.json contains all current attribute values for that end-user
  • details.json contains deliveries and their content for that customer, one per line
  • devices.json contains the device ID, platform, and when the device was last used— for up to 25 devices you associate with a given end-user (sorted by last_used)
  • events.json.gz and events2.json.gz contain the events (and their associated data) performed by the customer, from our event logs, one per line. If a person has a very large history of archived events, events2.json.gz holds that person’s most recent archived events, and the export adds a separate events2.truncated.json file (see below).
  • events2.truncated.json appears only when Customer.io leaves some of a person’s archived events out of the export, so you can use it to tell a truncated export from a complete one. The other files in the export aren’t affected.
  • metrics.json includes all individual delivery stats (timestamps for activities, and meta information), one delivery per line
  • relationships.json contains all relationships this person has to objects

Expiry

After 60 days, the export expires, and we delete it from your workspace. If you need the export again, you can always generate a new one!

Updated October 2, 2026