Integrations
Iterable makes consumer growth marketing and user engagement simple. With Iterable, marketers send the right message, to the right device, at the right time.
The following types of data can be configured to be sent from Iterable to mParticle. See Iterable’s documentation for more info about these events. Additional events will be processed if added by Iterable.
Event | mParticle Event Name |
---|---|
Triggered Send / Blast Sent | emailSend |
Email Bounce | emailBounce |
Email Click | emailClick |
Email Complaint | emailComplaint |
Email Open | emailOpen |
Email Send Skip | emailSendSkip |
Email Subscribe | emailSubscribe |
Email UnSubscribe | emailUnSubscribe |
Hosted Unsubscribe Click | hostedUnsubscribeClick |
In-App Click | inAppClick |
In-App Open | inAppOpen |
In-App Send | inAppSend |
In-App Send Skip | inAppSendSkip |
Push Bounce | pushBounce |
Push Send | pushSend |
Push Send Skip | pushSendSkip |
Push Uninstall | pushUninstall |
SMS Bounce | smsBounce |
SMS Received | smsReceived |
SMS Send | smsSend |
SMS Send Skip | smsSendSkip |
Web Push Send | webPushSend |
Web Push Send Skip | webPushSendSkip |
‘Push Open’ events are not supported
Any events sent from Iterable to mParticle will be processed as follows:
eventName
fieldIterable events are mapped as follows:
Iterable Field | mParticle Mapping |
---|---|
eventName | Event Type = Custom Event, Custom Event Type = Other, Event Name = eventName |
Email User Identity | |
toPhoneNumber | Reserved User Attribute Mobile |
city | Reserved User Attribute City |
region | Reserved User Attribute State |
applicationName | Application Info - application name |
userAgent | Device Information - http_header_user_agent |
ip | Batch IP Address |
DataFields | All fields in the DataFields property are mapped to custom event attributes in in the form DataFields.XXX, where XXX is the name of the field provided by Iterable |
Configure the Iterable Input:
Select the Iterable input configuration group to specify the configuration parameters:
Was this page helpful?