Customer.io helps you send targeted human messages to your users, by utilizing their unique interactions with your business. It facilitates segmentation of your users based on their historical actions, attributes, and email interactivity; and it automates the process of sending emails to specific user segments when trigger criteria are met.
Certain event properties are required in order to send an event to Customer.io. We map the properties of events collected by Replay so that they fit the expectations of Customer.io’s API. The following table shows you the properties collected by Replay and the names of the Customer.io properties to which they are mapped.
|Name of Property Collected By Replay||Customer.io Property Name||Required to track an event with Customer.io|
Any additional information Replay collects about an event is mapped to Customer.io’s
data dictionary and will still show up in the Customer.io interface.
Customer.io also requires certain trait properties in order to create a user profile. User properties collected by Replay are transformed so they fit the expectations of Customer.io’s API.
|Name of Property Collected By Replay||Customer.io Property Name||Required to store user profile with Customer.io?|
Other attributes collected by Replay are also passed to Customer.io and will show up in the Customer.io interface.
Note: When setting up the Outbound.io integration, use your Private Production API Key.