# Synchronize Audiences

### Overview

In this destination service, DinMo will update the contacts inside an audience, optionally insert new contacts and create a new list.

To do so, you will need to go through these three steps:

* Creating a Talon.One destination. Refer to the corresponding section for more info.
* Creating a user segment composed of all the users that will be updated or created in your Talon.One Audience. Refer to this [step-by-step tutorial](/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo/create-your-first-segment.md) to learn how to build segments without SQL in DinMo.
* Activating the segment to the Talon.One destination to start sending data.

Each time the activation will be running:

* Any new user entering your DinMo segment will be added to your Talon.One audience
* Any user leaving your DinMo segment will be removed from your Talon.One audience

Note that only users who have a valid identifier linked to a Talon.One account will be present in your audience.

### Destination setup

To start exporting audiences, you are first required to create a Talon.One destination with the corresponding destination service.

#### Optional: Setup default activation settings

At the end of the destination creation, you will be proposed to setup *Default Activation Settings*. This step is optional, but is highly recommended to facilitate the activation process.

By configuring default settings, synchronizing all your audiences to Talon.One will just take one click. Without default settings, you will be required to go through this configuration each time you activate a new audience.

Note that even if you setup default settings, you will still be able to adjust activation settings for each of your audiences if you wish to.

### Activation configuration

Once the destination has been setup, and your DinMo segment created, you can create an activation to start sending data to Talon.One right away. The segment will be exported as a new audience in Talon.One.

#### Activation Name and Description <a href="#activation-name-and-description" id="activation-name-and-description"></a>

In this section, the name you enter will be the name given to the audience created in Talon.One. You may also optionally enter a description, that will be attached to the audience in Talon.One.

By default, and if you activate your segment using the default activation settings, the name of the audience will be the DinMo segment name, and the description will be the DinMo segment description.

#### Fields mapping

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

#### Scheduling <a href="#scheduling" id="scheduling"></a>

In this section, specify how often the audience should be updated in Talon.One. Every time the audience is updated:

* Any user having left your DinMo segment since the last update will be removed from your Talon.One audience
* Any new user having entered your DinMo segment since the last update will be added to your Talon.One audience<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dinmo.io/integrations/destination-platforms/talon.one/synchronize-audiences.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
