Customer.io provides a marketing automation platform for email, SMS, push messaging, and more. Features include app-event based segmentation and targeting.
In order to activate audience forwarding to 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.
When forwarding audience data to Customer.io, mParticle will send Customer IDs, and if available Emails, First Names and Last Names.
mParticle’s Customer.io Audience integration works by setting attributes on a user which you can then use to create a data driven segment in Customer.io.
mParticle offers two ways to set segment membership attributes:
mParticle will always send the single attribute SegmentMembership, but it may also send one attribute per audience if the
Create One User Attribute Per Segment Configuration Setting is enabled.
This is the default behavior. mParticle creates a single attribute in Customer.io on each user, called
SegmentMembership. The value of this property is a list of mParticle audience IDs that match the user. Audience IDs can be found in the main Audience list view. For example, given these three audiences:
A user who is a member of both
Aspiring Athenians and
Ibiza Dreamers will show the attribute
SegmentMembership with a value of
'11036','11034' in Customer.io. To target members of
Ibiza Dreamers, you need to create a matching segment in Customer.io using the mParticle Audience ID,
with the filter
'11034'. It’s important to choose the
contains option, and not
equals, or users with membership in more than one audience will not be matched.
mParticle creates a user property in Customer.io for each audience that a user belongs to, based on the External Name of the audience. For example, a user who is a member of audience
Possible Parisians will show the attribute
In Possible Parisians is true in Customer.io. To target members of
Possible Parisians, you need to create a matching segment in Customer.io, with the filter
In Possible Parisians —
Since mParticle does not directly maintain segments in Customer.io, it will not delete segments when the corresponding mParticle audience connection is deleted or deactivated. When a deletion or deactivation occurs, mParticle will not update the Customer.io audience user attributes to remove the audience from each user.
|Setting Name||Data Type||Default Value||Description|
||The Site ID of your Customer.io account. You can find this ID on the “Integration” page of your Customer.io console.|
||The API Key of your Customer.io account. You can it on the “Integration” page of your Customer.io console.|
|Create One User Attribute per Segment||
||False||If enabled, mParticle will forward membership information for each audience as a separate user attribute. For example, if you’re forwarding an audience named “New Users,” mParticle will forward membership information for this audience in a user attribute called “In New Users” with a value of “true” or “false.”
Please note that mParticle will always forward a single user attribute called “SegmentMembership”. This attribute contains a comma-separated list of mParticle audience IDs that the user is a member of, wrapped in single quotes (e.g. “‘123’,‘456’,‘789’”).
Was this page helpful?