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

# Destinations overview

> Learn how to connect destinations in Hightouch so your models can be synced into the tools where teams run campaigns, measure results, and engage customers.

A **destination** is any system where teams consume activated data.

Common examples include:

* **CRMs** (Salesforce, HubSpot)
* **Marketing platforms** (Braze, Iterable, Marketo)
* **Ad platforms** (Meta Ads, Google Ads, LinkedIn)
* **Support tools** (Zendesk, Intercom)
* **Analytics platforms** (Amplitude, Mixpanel)
* **Custom APIs** (via Webhook/HTTP Request destinations)

![Reverse ETL flow: source → model → sync → destination](https://mintcdn.com/hightouch-3c037897/L_vQfA0JQEpeGUUo/images/get-started/reverse-etl-diagram.png?fit=max\&auto=format\&n=L_vQfA0JQEpeGUUo\&q=85\&s=1d150ddb9480d3ccb188c5977db55596)

Destinations are the endpoint of Hightouch’s [**Reverse ETL**](https://docs.hightouch.com/getting-started/concepts.md) pipeline. Once a [**model**](https://docs.hightouch.com/models/creating-models.md) is defined, you can configure one or more [**syncs**](https://docs.hightouch.com/syncs/overview.md) to deliver data into destinations.

> [!TIP]
>
> **For marketers**: a destination is the tool where you build campaigns,
> measure results, or engage with customers—like an ads platform, email tool, or
> CRM.

## Add a destination

To create a new destination:

1. Go to **Integrations → [Destinations](https://app.hightouch.com/destinations?from=docs)**.\\

   ![Add a destination](https://mintcdn.com/hightouch-3c037897/L_vQfA0JQEpeGUUo/images/destinations/add-destination.png?fit=max\&auto=format\&n=L_vQfA0JQEpeGUUo\&q=85\&s=8ad2696e1ab6afda2a7d957ba62e0134)
2. Click **Add destination**.\\

   ![Select a destination](https://mintcdn.com/hightouch-3c037897/L_vQfA0JQEpeGUUo/images/destinations/select-a-destination.png?fit=max\&auto=format\&n=L_vQfA0JQEpeGUUo\&q=85\&s=ccedf9e8d8b46626d8c5f5ebf12d039f)

You’ll be prompted to choose from supported destination types and configure:

* **Authentication** (OAuth, API key, service account, etc.)
* **Object type** (e.g. user, event, list, custom object)
* **Sync type** supported by that destination (upsert, insert, update, event streaming, etc.)

> [!NOTE]
>
> Each destination has unique configuration options. See catalog and refer to
> **integration-specific documentation** for setup details and supported sync
> types.

## Plan your sync

Before you configure a destination sync, you need a connected destination and a [model](https://docs.hightouch.com/models/creating-models.md) to pull data from. Then decide:

* **What to sync** — which objects, events, or records the destination needs, and therefore which [sync types](https://docs.hightouch.com/syncs/types-and-modes.md) to set up. Set up a separate sync for each object or data type.
* **Which fields to map** — the source columns that map to destination fields. See [field mapping](https://docs.hightouch.com/syncs/mapping-data.md).
* **How records change** — whether you're adding new records, updating existing ones, or both. This determines the [sync mode](https://docs.hightouch.com/syncs/types-and-modes.md#sync-modes) (insert, update, or upsert).
* **How often to sync** — how fresh the data must be, which sets the [sync schedule](https://docs.hightouch.com/syncs/schedule-sync-ui.md).

These decisions apply to every destination. Each destination's own page covers only what's specific to that platform — its required identifiers, field types, permissions, and limits — so check it before you build.

## Security and data handling

Hightouch writes data into destinations using secure APIs:

* All outbound traffic is encrypted via TLS 1.2+
* Data is batched and delivered according to the sync configuration (mode, type, mapping)
* Sensitive fields can be masked or excluded before syncing to destinations

See [Security and compliance overview](https://docs.hightouch.com/security/overview.md) for more details.

## Permissions

Access to individual destinations is controlled through custom roles. Admins can configure destination-specific grants in the **Destination** tab of the custom role builder, including per-destination read, write, and manage permissions. See [Roles](https://docs.hightouch.com/workspace-management/roles.md#destinations) for details.

## How destinations fit into data activation

* **Data teams**: configure destinations and map model columns to the correct destination fields.
* **Marketers**: access fresh, trusted data directly in the tools where they run campaigns or measure results.

**Example:**

* **Model**: SQL query for “users who abandoned checkout”
* **Destination**: Braze (Email + Push)
* **Sync**: upsert new/changed users nightly, send them into a “Cart Abandonment” campaign

## Next steps

* [Add your first destination](https://app.hightouch.com/destinations?from=docs)
* Learn about [Syncs](https://docs.hightouch.com/syncs/overview.md) and how they deliver data into destinations