mParticle is a customer data platform (CDP) that helps B2C companies unify existing customer data and allows for them to connect it anywhere in order to improve marketing performance, enhance analytics, and transform the customer experience.
mParticle will forward data server to server if they detect that the UserLeap kit is not included in your product. In this case, UserLeap will not be able to deliver studies.
With a server-to-server connection, UserLeap may still deliver Email Studies.
Choose from one of the supported inputs in mParticle.
To send data from your web app to your mParticle workspace input, navigate to Setup > Inputs and select the Web platform. The web SDK only needs the API Key (not the API secret), which you’ll replace in the snippet below. Reference the guide section for information on creating inputs.
The following snippet should be included on every page of your web app. Ideally, it should be placed within the
<head> tag or otherwise be loaded as soon as possible on each page
When you add an input, you should be provided with a Key and Secret from mParticle:
If done correctly you should see the input listed here.
UserLeap supports iOS as an input for passing events and attributes from mParticle. For full documentation, read their iOS guide
Here's a direct link to UserLeap.
Let’s start by configuring events to send to UserLeap
Both your Environment ID and API Key can be found on the UserLeap Connect page. If you would like to keep the same settings for development and production, you can choose to do so.
Give the configuration a name - the idea is to have two setups one for your UserLeap production environment and the other for the UserLeap development environment.
See above on how to find your API keys for mParticle.
Now we'll configure an audience
Give the configuration a name and then enter your API Key. Click Save when finished.
You may need to create an audience in mParticle if you have not done so already. Go to the Audience page in mParticle to create a new audience.
Yes! Events sent from the mParticle SDK can in fact be used to trigger a Sprig study. For full details on events, please read more here (or see table below).
mParticle events sent using server-to-server (mParticle firehose) cannot be used to trigger a study. These events can however be used as a study filter.
For study filters you can use events that are sent through the mParticle SDK or events that are sent network to network from mParticle to Sprig.
Attributes sent from mParticle (also known as audiences in mParticle) can be used as a study filter. To learn more about attributes, read here (or see table below).
Updated about 1 month ago