Integrating with mParticle

This tutorial shows you the basic steps to integrate Talon.One with mParticle.

See API Docs

Integration summary

mParticle integrations rely on the following mParticle data connection features:

Feature	Description
Input	A stream of data captured using the Events API provided by mParticle. Learn more.
Output	A stream of data forwarded from mParticle to other platforms like Talon.One. Learn more.

Integration types

mParticle supports the following integration types for Talon.One:

Integration type		Description
Input	Feed	Receive data from Talon.One. This is a custom feed.
Output	Event	Send raw event data from mParticle to Talon.One.
Output	Audience	Send audience membership information from mParticle to Talon.One.

Prerequisites

• You are an Admin user in Talon.One and mParticle.
• In Talon.One, you created an mParticle-specific API key.
• You know which mParticle user identity matches your Talon.One User ID.

Setting up a connection to Talon.One

In mParticle, a connection is a combination of an input, an output, and the configuration information required to make the connection work. A connection is a basic requirement for any integration use case.

For Talon.One, you can configure and use the following integration types:

• Setting up a feed input
• Setting up an event output
• Setting up an audience output

Setting up a feed input

With a feed input, you can send data from Talon.One to mParticle using the Events API provided by mParticle.

To set up a feed input:

1. In mParticle, open Setup > Inputs and switch to the Feeds page.
2. If there's a Talon.One section with existing feeds, open it and click +. Otherwise, click Add Feed Input and select Talon.One.
3. In the Input: Feed Configuration window, configure the following parameters:
   • Configuration Name: Type a configuration name.
   • Feed Status: Select whether you want the feed to be active.
   • Input Protection Level: Select the input protection level.
4. Click Save.

To learn how to use the feed input, see the mParticle documentation.

Setting up an event output

With an event output, you can send data from mParticle to Talon.One in close to real time.

To set up an event output:

1. In mParticle, open Setup > Outputs.
2. If there's a Talon.One Default Group section with existing outputs, open it and click +. Otherwise, click Add Event Output and select Talon.One.
3. In the Output: Event Configuration window, configure the following parameters:
   • Configuration Name: Type a configuration name.
   • Use same settings for Development & Production: Select your desired environment settings.
   • API Key: Paste the API key you created.
   • Deployment URL: Type the base URL of your Talon.One deployment, for example, mycompany.europe-west1.talon.one.
   • User ID: Select the user identity to map with Talon.One as the customer's user ID.
   • Run Rule Engine: Select whether to leverage the Rule Engine every time an event processing request is sent to Talon.One.
     tip

     To limit the triggering of effects for some events, you can set up and use a second configuration with Run Rule Engine disabled.

4. Click Save.

Setting up an audience output

With an audience output, you can send a series of messages about audience membership, with each message containing:

• An audience name.
• An identity for targeting, like email address.
• Information about whether the identity is being added to or removed from the audience.

note

Before you set up an audience output, ensure that:

• You created an audience.
• You started capturing some data points.

To set up an audience output:

1. In mParticle, open Setup > Outputs and switch to the Audience page.
2. If there's a Talon.One Default section with existing outputs, open it and click +. Otherwise, click Add Audience Output and select Talon.One.
3. In the Audience Configuration window, configure the following parameters:
   • Configuration Name: Type a configuration name.
   • API Key: Paste the API key you created.
   • Deployment URL: Type the base URL of your Talon.One deployment, for example, mycompany.europe-west1.talon.one.
   • User ID: Select the user identity to map with Talon.One as the customer's user ID.
   • Run Rule Engine: Select whether to leverage the Rule Engine after each membership change.
     tip

     To limit the triggering of effects for some audiences, you can set up and use a second configuration with Run Rule Engine disabled.

4. Click Save.

Next steps

You can build the rules and conditions for when a user joins or leaves an audience.

Related pages

• Running promotions for mParticle audiences
• Audience conditions
• Updating an audience