> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hightouch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Talon.One

> Sync customer data to Talon.One audiences

## Supported syncing

| Sync Type | Description | Supported Sync Modes | API documentation |
| - | - | - | - |
| **Customer Profile** | Sync data from any source to a Talon.One audience as customer profiles | Upsert | [Customer Profile Audiences](https://docs.talon.one/integration-api#tag/Audiences) |
| **Events** | Sync data from any source to a Talon.One events | Insert | [Events](https://docs.talon.one/integration-api#tag/Events/operation/trackEventV2) |

For more information about sync modes, refer to the [sync modes](https://docs.hightouch.com/syncs/types-and-modes.md#sync-modes) docs.

## Connect to Talon.One

Go to the [**Destinations** overview page](https://app.hightouch.com/destinations?from=docs) and click the **Add destination** button. Select **Talon.One** and click **Continue**.

Enter your Talon.One base URL. To find your base URL, simply navigate to your Talon.One Campaign Manager home page and enter the URL.

This should be in the format `https://<your domain>.talon.one/`.

You will need an Integration API key and a Management API key to successfully sync data from Hightouch.

If you do not have an Integration API key, follow the instructions [here](https://docs.talon.one/integration-api#section/Authentication/api_key_v1) to create one. If you have multiple Integration API keys, choose one to serve as your default.

If you do not have a Management API key, follow the instructions [here](https://docs.talon.one/management-api#section/Authentication/management_key) to create one. Enable access to the `v1/audiences`, `/v1/customer_search`, and `/v1/attributes`endpoint when creating your Management API key for the optimal experience. If you are connecting multiple applications, ensure this key has access to all of the applications.

Enter both of these API keys into Hightouch, and test that your connection is successful for both APIs.

You can connect multiple Talon.One applications in one Hightouch destination by entering multiple Integration API keys in the **Multiple application configuration** section. Enter an application name and corresponding Integration API key. When configuring your sync configuration, you can choose which application you'd like to sync to.

## Sync configuration

Once you've set up your Talon.One destination and have a [model](https://docs.hightouch.com/getting-started/concepts.md#models) to pull data from, you can set up your sync configuration to begin syncing data. Go to the [**Syncs** overview page](https://app.hightouch.com/syncs?from=docs) and click the **Add sync** button to begin. Then, select the relevant model and the Talon.One destination you want to sync to.

### Syncing audiences

#### Audience selection

Select whether you'd like to create a new audience or sync to an existing audience. If you would like to create a new audience, enter the name of the audience in the sync configuration form.

#### Record matching

Talon.One uses `Profile Integration ID` to identify each customer profile. Choose which column in your model contains the Profile Integration ID.

#### Rule Engine

By default, adding customer profiles to Talon.One audiences does not trigger the Rule Engine. If you have defined [rules](https://docs.talon.one/docs/product/rules/overview) in Talon.One that dynamically apply effects to customers, enable this option.
This option is **less performant** than the default option, so you may observe slower sync speeds.

#### Custom attributes mapping

If you have created customer profile custom attributes, you can map to those attribute values in Hightouch. Choose which column in your model should be mapped to each attribute.
Customer profile custom attributes cannot be created in Hightouch. To create new custom attributes, follow the [instructions on Talon.One](https://docs.talon.one/docs/product/account/dev-tools/managing-attributes#creating-a-custom-attribute).

#### Delete behavior

When records leave your query result, they are removed from your audience by default. If you would not like to delete any records from your audience, you can choose to do nothing when records leave your query result.

### Syncing events

Sync data from any source to events in Talon.One.

> [!WARNING]
>
> To ensure syncs send each event, your event model must use a truly unique [primary key](https://docs.hightouch.com/getting-started/concepts.md#unique-primary-key-requirement). See the [events syncs](https://docs.hightouch.com/syncs/types-and-modes.md#event-syncs) documentation for more information.

#### Record matching

You can match rows from your model to events in Talon.One on any column in your model and the **Profile ID** field in Talone.One.
The Talon.One events API requires the **Profile ID** field, so you must map it to complete your configuration.

#### Attributes mapping

Hightouch lets you sync Talon.One event attributes that have already been created in your Talon.One account via field mapping.

## Tips and troubleshooting

To see the exact API requests and responses from each sync run, use the [live debugger](https://docs.hightouch.com/syncs/debugger.md). To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up [sync alerts](https://docs.hightouch.com/syncs/alerting.md). If you run into an issue this page doesn't cover, [contact support](#pylon-chat).