mParticle Connector

This guide covers implementing Descope's mParticle connector. mParticle is a customer data platform (CDP) that helps companies collect, manage and activate customer data in real time.

Configure mParticle connector

Start by navigating to the Descope mParticle connector: Connectors then select mParticle

Now, complete the required fields:

• Connector name: Custom name for your connector. This will come in handy when creating multiple connectors from the same connector template.
• API Key: The mParticle Server to Server Key generated for the Descope service.
• API Secret: The mParticle Server to Server Secret generated for the Descope service.
• Custom base URL: The base URL of the mParticle API, when using a custom domain in mParticle.

You can also configure the optional fields:

• Connector description: Describe what your connector is used for.

You can test if your connector's configuration is working properly simply by hitting the Test button and viewing the Test Results panel.

Save your configuration by hitting Create.

Add your mParticle connector to a flow

Navigate to: Flows, choose your flow. Then, tap the create button (designated via the + icon), select Connector, and choose the mParticle option.

Click to set down the connector in your flow editor and fill out the fields:

• Step name: The unique name for the step.
• Connector: Name of the connector which was used to setup the connector.
• Event Type: mParticle event type. Can be custom_event, session_start,session_end etc.
• Environment: Default value is production. Must be either production or development.

For any extra information that needs to be tracked and analyzed later, event properties can be added.

Example:

• Key: event_name
• Type: Dynamic
• Value: project.name

Now, link your connector in your authentication flow, making sure it's placed after any required attributes you just chose are defined. Simply by adjusting the attributes and location of the connector, you can track anything from a user sign up/in to the method used for authentication.

That's it! Whenever a user goes through your authentication flow, the mParticle connector will be automatically triggered and the event will appear in your mParticle workspace.

The image above shows the Test Log along with event project name Demo as value which is in this scenario.