Sending Insider Events to mParticle
- 21 Mar 2024
- 1 Minute to read
Sending Insider Events to mParticle
- Updated on 21 Mar 2024
- 1 Minute to read
Article Summary
Share feedback
Thanks for sharing your feedback!
You can establish Insider as a source in mParticle’s ecosystem, and send data from Insider to mParticle. With this integration, you can enable mParticle to collect channel Interaction and lead collection events.
This integration guide provides a complete frame of:
Use Cases
By integrating Insider as source on mParticle, you will be able to collect all messaging channel events such as Email Open or SMS Click so that you can store them in one place, create a segment, and forward them to your destinations.
You can easily forward collected leads by Insider lead collection templates and access data of your collected leads on mParticle dashboard.
Configuring Insider as a Source on mParticle
To configure Insider as a source on your mParticle account, follow these steps:
Your title goes here
You should create all your events and attributes with the exact naming before you set up the Insider. You can refer here on how to create events and event specifications.
1. Log into your mParticle account to find Custom Feed under Setup > Inputs and click it.
2. Name your Custom Feed name as Insider and click Save.
3. To finish the setup, contact Insider team to activate mParticle integration on Insider's end with the provided Server Key and Secret.
Data Synchronization
Identity
Insider can pass a selected identifier data to mParticle. This identifier can be any attribute including email, phone_number, uuid and any custom attribute.
Supported Events
The following events are forwarded to Segment:
- Mobile App Events
- Email Events
- Architect Events
- Web Push Events
- WhatsApp Events
- SMS Events
- Lead Collection User Event
- Custom events defined by user
| Event Name | Event Description |
|---|---|
| email_delivered | An email was successfully delivered to user. |
| email_open | User opened the email campaign. |
| email_click | User clicked a link in the email campaign. |
| email_bounced | User’s receiving mail server did not accept it. |
| email_unsubscribe | User no longer wants to receive marketing emails. |
| whatsapp_reply | User clicked any button in WhatsApp Message. |
| whatsapp_reply_first_button | User clicked the first quick reply button. |
| whatsapp_reply_second_button | User clicked the second quick reply button. |
| whatsapp_reply_third_button | User clicked the third quick reply button. |
| whatsapp_reply_auto_reply | User replied to WhatsApp message in a template that includes quick reply. |
| whatsapp_reply_other_reply | User replied to WhatsApp message in any template. |
| whatsapp_opt_out | User no longer wants to receive marketing WhatsApp marketing messages. |
| sms_click | User clicked a link in the SMS message. |
| sms_delivered | An SMS was successfully delivered to user. |
| sms_unsusbcribe | User no longer wants to receive marketing SMS marketing messages. |
| inapp_seen | User has seen the InApp campaign. |
| push_delivered | App Push message delivered to user. |
| push_session | User clicked an App Push. |
| session_start_from_push | App is opened by clicking an App Push. |
| session_start | Each time App is opened. |
| lead_collected | A new lead has been collected. |
Was this article helpful?