# Mutiny Destination

## Destination Info

* Accepts [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Mutiny** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

[Mutiny](https://mutinyhq.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) allows you to personalize your website content based on customer's activity and 3rd party data. By integrating with [Segment](https://segment.com), you can easily and accurately track conversions and integrate 1st party data for personalization with Mutiny.

This destination is maintained by Mutiny. For any issues with the destination, [contact the Mutiny Support team](mailto:mutinylovesyou@mutinyhq.com).

## Getting Started

To set up Mutiny to receive Segment data:

1. From your Segment Project's Destinations page click on "Add Destination".
2. Search for "Mutiny" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. In the destination settings, enter your personal "API Key" into Segment's Mutiny integration settings panel UI, which you can find from your [Mutiny dashboard](https://app.mutinyhq.com/integrations/segment).

## Identify

If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/segment/connections/spec/identify/) does. An example call would look like:

```js
analytics.identify('userId123', {
  email: 'john.doe@example.com'
});
```

Identify calls will be sent to Mutiny as an `identify` event. Segment uses this in order to associate traits with an individual, which can be targeted for personalization in outbound email campaigns.

## Track

If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/segment/connections/spec/track/) does. An example call would look like:

```js
analytics.track('Clicked Login Button')
```

Track calls are sent to Mutiny as a `track` event. Within the Mutiny dashboard, you can select which events signal a conversion for your website visitors. When a `track` event is processed for these events, a visitor will be marked as converted and that information will be displayed in the experiment results for a given experience.

Mutiny's integration with Segment enables customers to use Segment events to track conversions in Mutiny. Mutiny also sends events *to* Segment to help track attribution for Mutiny experiences. Mutiny sends the `Mutiny Experience Viewed` with the `audienceSegment`, `experience`, and `personalized` properties. For example:

```js
analytics.track('Mutiny Experience Viewed', {
  experience: 'Corporate Website Experiment',
  audienceSegment: 'Small company',
  personalized: true,
});
```

The `personalized` property is `true` for personalized experiences and `false` for a control views. For more information, contact [Mutiny Support](mailto:mutinylovesyou@mutinyhq.com).

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to Mutiny  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field   | Description                                                        | Required | Type   |
| ------- | ------------------------------------------------------------------ | -------- | ------ |
| API Key | You can find your API key under "Segment" in the Integrations tab. | Yes      | string |