Customer.io provides an email service that allows you to generate and execute against email lists based upon user mobile app activity.
In order to enable mParticle’s integration with Customer.io, you will need the Site ID and API Key of your Customer.io account. Both of these can be found on the “Integration” page of your Customer.io console.
mParticle will forward all events logged with the mParticle SDK
logScreen methods along with their attributes. When forwarding events, mParticle will include the timestamp of the events in JSON data format. When forwarding event names, mParticle trims the leading/trailing spaces and replace spaces with “_”.
mParticle will only forward event and user data to Customer.io for users that have an email address (
MPUserIdentityEmail) defined. When forwarding user data, mParticle uses
MPUserIdentityCustomerId as the Customer.io user_id. If CustomerId is not defined, mParticle uses the email address instead. mParticle always forwards users’ email, $FirstName, and $LastName, and will optionally forward all user attributes if the configuration parameter “Include ALL user attributes?” is enabled.
Please note that users who opt out of event tracking via mParticle’s
optOut (in iOS) or
setOptOut SDK methods will be unsubscribed from email communications in Customer.io, but their user profiles will remain in Customer.io.
|Setting Name||Data Type||Default Value||Description|
||The API Key of your Customer.io account. You can find it on the “Integration” page of your Customer.io console.|
||The Site ID of your Customer.io account. You can find this ID on the “Integration” page of your Customer.io console.|
|Setting Name||Data Type||Default Value||Platform||Description|
|Include user attributes||
||True||All||If enabled, mParticle will forward all user attributes to Customer.io. If disabled, mParticle will just send the users’ first and last names (so that they can be properly addressed in email campaigns).|
|Send User’s Created At||
||False||All||If enabled, mParticle will forward a value for user’s created_at field (the UNIX timestamp from when the user was created in the system). This value is first configured when a user opens up the application that contains mParticle’s SDK and it doesn’t change over time. It is device-specific, which means that the value will be constant among the same device type (eg. multiple Android devices) for the same user. Each device will have the same email and customer id, but the field will differ across different device types (Android, iOS, MobileWeb, AlexaOS, etc…). The created_at field will overwrite based on whatever device was last seen. Meaning that a user with multiple devices will take the created_at value of whatever the most recent device is.|
Was this page helpful?