# Integrate with mParticle

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

> For the complete documentation index, see [llms.txt](https://docs.talon.one/llms.txt).

<Button variant="primary" size="l" href="/third-party-api#tag/mParticle">
  See API docs
</Button>

## Integration features and types

The [Talon.One integration for mParticle](https://www.mparticle.com/integration/talonone/) supports the following mParticle data connection features:

|               Feature                |                                                                                                              Description                                                                                                              |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <NotificationCardTag tag="Input" />  | A stream of data captured using the Events API provided by mParticle. [Learn more](https://docs.mparticle.com/guides/get-started/create-an-input). |
| <NotificationCardTag tag="Output" /> | A stream of data forwarded from mParticle to other platforms like Talon.One.  [Learn more](https://docs.mparticle.com/guides/get-started/connect-an-event-output).                                                                |

For these features, the following integration types are available:

| Type                                          | Description                                                                                                                 |
| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| <NotificationCardTag tag="Feed Input" />      | Receive data from Talon.One. This is a custom feed. |
| <NotificationCardTag tag="Event Output" />    | Send raw event data from mParticle to Talon.One.                                                                            |
| <NotificationCardTag tag="Audience Output" /> | 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][API key].

## Set up a connection to Talon.One

In mParticle, a [connection][Connections] 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:

- [Set up a feed input](#set-up-a-feed-input)
- [Set up an event output](#set-up-an-event-output)
- [Set up an audience output](#set-up-an-audience-output)

:::important
For the following steps, we assume you are using mParticle's original UI. To enable it, sign in to mParticle and click **Settings** > **Go to Classic Experience**.
:::

### Set up a feed input

With a [feed input](https://docs.mparticle.com/guides/get-started/create-an-input/),
you can send data from Talon.One to mParticle using the [Events API][Events API] provided by mParticle.

To set up a feed input:

1. In mParticle, open **Setup** > **Inputs** and switch to the **Feeds** page.
1. If there's a **Talon.One** section with existing feeds, open it and click **+**. Otherwise, click **Add Feed Input** and select **Talon.One**.
1. 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][Input protection level].
1. Click **Save**.

To learn how to use the feed input, see the [mParticle documentation](https://docs.mparticle.com/integrations/talon-one/feed/).

### Set up an event output

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

For a sample scenario, see our [Use event data with mParticle](/docs/dev/technology-partners/mparticle/mparticle-use-event-data.md) tutorial.

To set up an event output:

1. In mParticle, open **Setup** > **Outputs**.
1. 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**.
1. 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](#prerequisites).
   - **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][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.
     :::
1. Click **Save**.

### Set up an audience output

With an [audience output][Connect 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.

For a sample scenario, see our [Run promotions for mParticle audiences](/docs/dev/technology-partners/mparticle/run-promotions-for-mparticle-audiences.md) tutorial.

To set up an audience output:

1. In mParticle, open **Setup** > **Outputs** and switch to the **Audience** page.
1. If there's a **Talon.One Default** section with existing outputs, open it and click **+**. Otherwise, click **Add Audience Output** and select **Talon.One**.
1. In the **Audience Configuration** window, configure the following parameters:
   - **Configuration Name**: Type a configuration name.
   - **API Key**: Paste the API key you [created](#prerequisites).
   - **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][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.
     :::
1. Click **Save**.

You can now [connect the output][Connect audience output] to the [audience you created][Create audience] in mParticle.

## Next steps

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

## Related pages

- [Run promotions for mParticle audiences][Running promotions]
- [Audience conditions][Audience conditions]
- [Update an audience][Update audience]

[Connections]: https://docs.mparticle.com/guides/platform-guide/connections/
[Input protection level]: https://docs.mparticle.com/guides/customer-360/profiles/overview/#input-protections
[API key]: /docs/product/applications/manage-third-party-api-keys.md
[Rule Engine]: /docs/dev/get-started/overview.md
[Events API]: https://docs.mparticle.com/developers/apis/http/
[Create event output]: https://docs.mparticle.com/guides/get-started/connect-an-event-output/
[Create audience]: https://docs.mparticle.com/guides/get-started/create-an-audience
[Connect audience output]: https://docs.mparticle.com/guides/get-started/connect-an-audience-output/
[Rules]: /docs/product/rules/overview.md
[Running Promotions]: /docs/dev/technology-partners/mparticle/run-promotions-for-mparticle-audiences.md
[Audience conditions]: /docs/product/rules/conditions/available-conditions.md#audience-conditions
[Update audience]: /docs/product/rules/effects/use-effects.md#update-an-audience