> ## 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.

# Cadent

> Activate your data as Conversion events in Cadent

## Supported syncing

| Type | Description | Supported Sync Modes |
| - | - | - |
| **Conversions** | Sync conversion event data to Cadent | Insert |

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 Cadent

Go to the [**Destinations** overview page](https://app.hightouch.com/destinations?from=docs) and click the **Add destination** button. Select **Cadent** and click **Continue**. You can then authenticate Hightouch to **Cadent** by entering your API key.

If you do not have an API key, contact Cadent support to set one up.

## Sync configuration

Once you've set up your Cadent 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 Cadent destination you want to sync to.

### Syncing conversions

Sync event conversions data to Cadent.

#### Dataset selection

Enter the dataset ID you would like to sync events to. This ID can be found on the Dataset Details page in Cadent.

#### Field mapping

Each Cadent dataset is set up with a match key. Include this match key in your mappings to successfully sync events to Cadent.

Provide the event name, and optionally provide the event timestamp. If no timestamp is provided, Cadent will use the time the event was received.

Hightouch lets you sync event properties and user properties via field mappings. Select the column in your model you'd like to map to each field in Cadent you'd like to sync.

The following are valid values for the event conversion type in Cadent:

* `email_clickthrough`
* `site_clickthrough`
* `online_purchase`
* `app_install`
* `in_app_purchase`
* `physical_store_visit`
* `offline_purchase`
* `phone_call`
* `chat_event`
* `system_generated`

#### Field hashing

The following fields are required to be hashed, and hashed by default:

* Email (`em`)
* First name (`fn`)
* Last name (`ln`)
* Date of birth (`db`)
* Gender (`ge`)
* City (`ct`)
* State (`st`)
* Zip code (`zp`)
* Country (`country`)
* External ID (`external-id`)

If the data in your model is already hashed, you can disable field hashing in your sync.

## 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).