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 a source in mParticle’s ecosystem and send data from Insider One 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 One as a source in mParticle, you can collect all messaging channel events, such as Email Open or SMS Click, store them in one place, create a segment, and forward them to your destinations.
You can easily forward collected leads using Insider One lead collection templates and access your collected lead data in the mParticle dashboard.
Configure Insider One as a Source on mParticle
To configure Insider One as a source on your mParticle account, follow these steps:
You should create all your events and attributes with the exact naming before you set up Insider One.
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 Destination as the integration type, and click the Save button.
4. Log in to your mParticle account, navigate to Directory from the side menu, and find Insider One as your output connector in your mParticle marketplace.
5. Click the Input Feed Integration Type and start configuring the Insider One.
6. Name your configuration, select the platform, and click the Save button.
7. Copy Server to Server Key and Server to Server Secret.
8. Paste the keys to the related input areas on the Insider One's InOne panel and select the mParticle identifier you will use.
9. After completing the Authentication step, continue with the Rules step. You can select one or more Events to send to mParticle.
10. Once you've chosen the initial event type to start data collection, you can view events categorized by type and choose which ones to include or exclude for collection. You can also introduce additional event types within the same section. You can also apply conditions to each event you want to send.
11. The Event Parameter section will be enabled after you select an event. You can select the parameters of your events through the dropdown that you want to send to your destination.
You can select the additional attributes to be included in the data sent to the endpoint. If you want to include additional attributes while sending the event data to your destination, you can add them here. For example, if you are sending an email open event, you can also select the email address to which it is to be sent. This way, you can understand which email address opened in which email campaign.
12. Thanks to Segmentation, you can also decide which users' data will be sent to the destination. For example, you can send an email open event only for users whose Total Purchase Amount was more than 100 USD in the last week. This way, you only get the data you need in the destination.
13. Once you have selected the data you want to send and determined when to trigger it under the Rules tab, move on to the Match tab. In this section, align the selected events, event parameters, and attributes with those in the destination to ensure that your data matches the schema defined in mParticle.
14. In the Launch step, you can activate your mParticle integration or save it as a draft. Select the Active status and click the Save button to activate your integration.
Data Synchronization
Identity
Insider One 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
All the default events are forwarded to mParticle.