Exporting Data for Many People

There are a few ways for you to export people data from the People page in Customer.io. You can…

  • Export all your users and all their data
  • Export all your users, but only with specific attributes
  • Export a set of users who meet certain conditions — with all of their attributes, or a specific set
Be aware that these exports will include all attribute and event data you have sent to Customer.io for the selected profiles. If this includes sensitive data, you must purge that before passing it to customers.

How-to

First, head to the People section of your account. There, you’ll see the Export to CSV dropdown:

Export as CSV dropdown

When you click this, you’ll see three options:

  • All attributes: Clicking this will export all users and all their attributes
  • Displayed attributes: If you’ve displayed specific attributes in the UI via the Edit Displayed Attributes dialog, this option will export those
  • Choose attributes…: Quickly choose exactly which attributes you want to export from everything you’re sending to Customer.io.

For each option, the id attribute will always be included in your export.

Exporting everyone

In the Export to CSV dropdown, select “All attributes” and you’re done! It’s that simple; you’ll get a CSV with all your users and all their attributes.

Export all

Exporting displayed attributes

The “Displayed attributes” option will export all of the displayed users, with the attributes that are currently visible in the table. For example, if we use the ‘Edit Displayed Attributes…’ modal to display the following attributes (id, city and state):

Displaying attributes

In this image, selecting Export to CSV > Displayed attributes will result in an export of all users in Customer.io, and the attributes id, city and state in addition to created_at.

Exporting specific attributes

If you want to just export a set of specific attributes immediately without viewing them first, select Choose attributes… in the export dropdown, and then specify which attributes you’d like to export:

Choosing attributes to export

You can also combine this with…

Exporting users who meet certain conditions

By clicking the “adding filters” toggle switch, you can specify segment and/or attribute conditions to refine the users to be exported. Then, in the dropdown, you can choose to export those people with all their attributes, or choose exactly which ones you’d like, as above.

So we can refine by segment or attribute conditions:

Export filtered by segment

…and then use the ‘Choose attributes…’ dialog to specify exactly which attributes to export for those users.

What segment-filtered exports look like

In the above example, if we export everyone in the “Looney Tunes Characters” segment, and then choose to export their id and species attributes, the resulting exported CSV looks like this:

Sample segment-filtered CSV output

There are two users meeting those conditions, with ids of 4 and 5, and species values of coyote and bunny respectively.

The 7 in _segment:7 is the id of the segment used. This is found on the individual segment page, as well as in the overview:

Segment ID Segment ID

The values underneath it (in this case, 1519326058 and 1519326081) are the timestamps for when this user matched that particular segment. You can convert them to dates using the Epoch Converter.

Helpful notes

No exporting based on email address

As mentioned above, you can add filters and export those users, but we don’t support exporting based on the “filter by email address” field.

Bonus attributes

In addition to all the attributes that you’re sending to Customer.io, you can also export a couple of internal ones that we track. These are:

  • _created_in_customerio_at: this is when a user was first created in Customer.io. This is different from created_at because it’s specific to when this user was created in Customer.io, not in your system or application.
  • _last_visited: the most recent timestamp of a pageview event for that particular user
  • _last_emailed: the most recent time that you successfully sent a delivery to that particular user

Why the id attribute is always included

We do this in order to make it easier for you (and our support team, if necessary) to troubleshoot your exports, by ensuring that there is always a reference to the unique identifier of your end-user in Customer.io.