Documentation Index

Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt

Use this file to discover all available pages before exploring further.

Send mParticle Events to Insider One

Prev Next

You cannot make any changes to External Platform Integrations without having either an Administrator or an Editor with PII access in InOne. Refer to User Roles for further information.

You can establish Insider One as an output in mParticle’s ecosystem and send data from mParticle to Insider One. With this integration, you can enable Insider One to collect any event or attribute that mParticle collects.

This integration guide provides a complete framework for:

Use Cases

Sending your website and app data from mParticle to Insider One 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 One’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. 

Configure Insider One as an output

To configure Insider One as an output in your mParticle channel, follow these steps:

  1. Navigate to Components > Integrations > External Integrations on the Insider One's InOne panel. 

  2. Select the mParticle platform.

  3. Give a name to your integration, select Source as the integration type, and click the Save button.

  4. Copy the mParticle Integration Key, Insider One Account Name, Insider One Account ID, and click the Save button.

  5. Navigate to the Directory from the side menu and find Insider as your output connector in your mParticle marketplace.

  6. Click the Output Integration Type and start configuring Insider One.

  7. Place your API Key, Insider Account Name, and Account ID into the configuration settings.

  8. After saving the configuration settings, connect your desired input to your Insider output.

  9. Select your Insider One configuration and activate your integration.

User Identification

By default, Insider One gets email, phone number, uuid (mParticle customer_id), and mpID as identifiers. You can easily change it via your identity resolution settings from the Identity Resolution Management page. Insider One directly collects data as an identifier if the attribute sent by mParticle is selected as an identifier.

Event and Attribute Sync

Insider One can get all the events and attributes that are sent from mParticle over to Insider One. 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 tables below are collected as custom events or attributes from mParticle to Insider One.

In Insider One, an attribute’s name can have up to 255 characters. If an attribute’s name exceeds 255 characters on the mParticle side, it will be rejected via Insider One.

Mapped Events

mParticle Event Name

Insider One 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 One 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 One Attribute Name

Age

Age

Gender

Gender

Country

Country

City

City

Firstname

Name

Lastname

Surname

email_optin

Email Optin

sms_optin

SMS Optin

If you want to send a custom event parameter or attribute, ensure it is created in Insider One's InOne panel with the same name used in mParticle. This allows Insider One to record those fields correctly.

Limitations and Validations

  • The phone number must be transmitted in E. 164 format from mParticle to Insider One.

  • Event, Event Parameter, and Attribute keys have a maximum length of 40 characters. If any key exceeds this limit, ensure it is shortened before sending it to Insider One.