Sending mParticle Events to Insider
- 23 Aug 2023
- 1 Minute to read
Sending mParticle Events to Insider
- Updated on 23 Aug 2023
- 1 Minute to read
Article Summary
Share feedback
Thanks for sharing your feedback!
You can establish Insider as an output in mParticle’s ecosystem, and send data from mParticle to Insider. With this integration, you can enable Insider to collect any event or attribute that is collected by mParticle.
This integration guide provides a complete frame of:
Use Cases
Sending your website and app data from mParticle to Insider helps you leverage a variety of use cases:
- Triggering Journeys
You can track user behavior such as cart abandonment, purchase, etc. to trigger journeys with Insider’s Architect products, and target users across different channels such as website, web push, email, etc.
- Personalizing user experience
You can leverage the comprehensive user information such as name, age, city, country, etc. that is passed by leveraging native integration with mParticle, and deliver personalized user experiences and messaging across channels.
Configuring Insider as an output
To configure Insider as a output in your mParticle channel, 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. Navigate to Directory from the side menu and find Insider as your output connector in your mParticle marketplace.
2. Click the Output Integration Type and start configuring Insider.
3. Place your Insider account name, ID and upsert API key into the configuration settings.
4. After saving the configuration settings, connect your desired input to your Insider output.
5. Select your Insider configuration and activate your integration.
User Identification
By default, Insider gets email, phone number and uuid (mParticle customer_id) and mpID as identifiers. You can easily change it via your identity resolution settings from Identity Resolution Management page. Insider directly collects data as an identifier if the attribute sent by mParticle is selected as an identifier.
Event and Attribute Sync
Inisder can get all the events and attribute that are sent from mParticle over to Insider. By default, some of the events and attributes are mapped when syncing data from mParticle. All other events and attributes that are not in the below tables are collected as custom event or attributes from mParticle to Insider.
Mapped Events
| mParticle Event Name | Insider Event Name |
|---|---|
| add_to_cart | Item Added to Cart |
| remove_from_cart | Item Removed From Cart |
| checkout | Cart Page View |
| view_detail | Product Detail Page View |
| purchase | Purchase |
| session_start | Session Start |
Event Parameters Mapped
| mParticle Event Parameter Name | Insider Event Parameter Name |
|---|---|
| action | Event Name |
| id | Product ID |
| name | Name |
| category | Category |
| price | Unit Sale Price |
| quantity | Quantity |
| transaction_id | Event Group ID |
| session_id | Session ID |
| timestamp_unixtime_ms | Timestamp |
Attributes Mapped
| mParticle Attribute Name | Insider Attribute Name |
|---|---|
| Age | Age |
| Gender | Gender |
| Country | Country |
| City | City |
| Firstname | Name |
| Lastname | Surname |
Was this article helpful?