Once you’ve had a chance to see Customer.io work, the next thing you might want to do is back-fill your historical data. Here are a couple of options.
If you’re a developer, you may want to write a quick script to loop through all of the people in your database and add them to Customer.io. While this creates a lot of API requests, it’s fine to do and won’t overload our system if you follow the API guidelines.
Note, that your API calls may not be processed in the order you send them. If you will be sending multiple identify() calls per user and chronology of the attribute updates is important to you, you will need to send a
_timestamp value as discussed in our documentation on User Attributes.
Customer.io shines best when we have access to a stream of real-time data about your users so we’d like to see if there’s anything we can do to help you get this type of data flowing directly into your account.
However, in cases where you need to backfill historical data into your new account or you want to complete one-time imports, you are able to upload a CSV file of users.
For more information, check out: Uploading People via CSV
You can optionally add historical event data by adding a timestamp.
If you want to also use the event timestamp to customize your emails, you can add an additional attribute to the data hash like this:
If you need help on any of these issues, please get in touch.