---
title: Syncs
description: Send user and event data to downstream tools.
product: data
lang: en
last_updated: 2026-11-20
token_estimate: 3428
---
# Syncs

Amplitude supports three sync cadences for cohorts, properties, computations, and predictions: on-demand, recurring, and real-time. A sync pushes Amplitude data to third-party [destinations](https://amplitude.com/docs/data/destination-catalog) such as ad networks, attribution providers, and marketing automation platforms.

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

As cohort audience membership or user predicted probabilities change, Amplitude automatically adjusts cohort membership in connected destinations on recurring and real-time syncs.

You don't need CSV downloads or manual syncs. When users take an action in your app, Amplitude automatically syncs them to the relevant ad, email, or testing platform.

## Plan availability

Scheduled Syncs and AMPL to AMPL real-time cohort sync vary by plan. Some features need a higher plan or an add-on. Go to [Amplitude pricing](https://amplitude.com/pricing) for plan details.

| Plan | Scheduled Syncs | AMPL to AMPL real-time cohort sync |
| --- | --- | --- |
| Free | Not included | Not included |
| Plus | Not included | Not included |
| Growth | Limited 2 syncs (add-on: Unlimited) | Not included |
| Enterprise | Limited 2 syncs (add-on: Unlimited) | 50 |

AMPL to 3rd Party Real-Time Cohort Syncs and AMPL to AMPL real-time cohort sync are available as an add-on on the Growth and Enterprise plans.

One-Time Syncs is available on all plans.

_Availability reflects the latest Amplitude plans. If your organization is on an older plan, your access may differ. Check your plan under [Plans & Billing in your organization settings](/docs/admin/account-management/account-settings#organizational-settings), or contact your Amplitude account representative._

## Feature availability

- Users on Free, Plus, Growth, and Enterprise plans can use on-demand syncs.
- Users on Growth, Enterprise, and Plus plans can use recurring syncs.
- Users on Growth and Enterprise plans can use real-time syncs.

## Choose a sync cadence

The cadence you pick determines how often the destination receives updates, and which destinations accept the sync at all.

### On-demand syncs

Use an on-demand sync to send a cohort to your destination once. Choose this option when you need to export a cohort and don't require continuous updates. On-demand syncs suit audience testing and one-off campaigns.

### Recurring syncs

Use a recurring sync to send updates on an hourly or daily basis. Amplitude queues sync jobs throughout the hour or day, depending on your selection. You can't choose the time of day that a sync runs.

> **Note:** Recurring sync timing
>
> Amplitude schedules a time to sync the cohort as soon as you create a new cohort or update the sync details.
>
> The first sync occurs right after Amplitude schedules it. The first two syncs may occur more frequently than every 24 hours.
>
> If you don't update the sync, future sync jobs run around the same time within the time period.

### Real-time syncs

With real-time syncs, Amplitude sends updates to a partner destination almost as soon as a user enters or exits a cohort. This unlocks additional uses for cohort sync, such as timely and contextual messaging to end users.

When you create a real-time sync, Amplitude first sends the initial population to the destination. This can take several hours if the sync is large. After this initial sync, Amplitude sends updates every minute as users enter and exit the cohort. When partners fail or reject API requests, or when network delays and errors occur, Amplitude sends any changes once the issue clears.

Amplitude recommends real-time syncs for cohorts that need minute-by-minute precision and that don't change by a large number of users from minute to minute. If you choose real-time syncing and notice in the sync history that most syncs update `0` users, an hourly recurring sync may work better.

Real-time sync sends cohort membership to destinations, but not computations, properties, or predictions.

> **Warning:** Real-time sync limitations
>
> Real-time sync supports cohorts of 1,000,000 users or fewer by default. If you need real-time sync on a larger cohort, contact your Amplitude account team. Computationally complex cohorts fall back to a recurring cadence because of the computation cost.
>
> Real-time sync supports all cohort types except:
>
> - Funnel
> - Retention
> - Stickiness
> - Nth time event
> - Event within
> - Distinct interval
>
> Real-time sync supports all cohort destinations except those that aren't designed for frequent updates, or that enforce integration limits preventing frequent syncing:
>
> - [Facebook Ads](https://amplitude.com/docs/data/destination-catalog/facebook-ads)
> - [Google Ads](https://amplitude.com/docs/data/destination-catalog/google-ads-cohort-syncing)
> - [Twitter (X) Ads](https://amplitude.com/docs/data/destination-catalog/twitter-ads-cohort)
> - [Hubspot](https://amplitude.com/docs/data/destination-catalog/hubspot-cohort-sync)
> - [Qualtrics](https://amplitude.com/docs/data/destination-catalog/qualtrics)
> - [S3 cohort sync](https://amplitude.com/docs/data/destination-catalog/amazon-s3-cohort)
> - [TikTok Ads](https://amplitude.com/docs/data/destination-catalog/tiktok-ads)
> - [Enterpret](https://amplitude.com/docs/data/destination-catalog/enterpret)
> - [SFMC](https://amplitude.com/docs/data/destination-catalog/salesforce-marketing-cloud-v2)
> - [The Trade Desk](https://amplitude.com/docs/data/destination-catalog/thetradedesk)

## Create a new sync

To create a new sync, follow these steps:

1. Click **+ New** and click the **Sync** tile. The _Create New Sync_ modal appears.
2. Select the sync type to create: cohort, recommendation, user property, or computation sync. Then click **Next**.
3. From the drop-down list, select the specific item you want to sync. Then click **Next**.
4. Choose the destination to sync to. If the destination doesn't appear, click **+ Add** or **Manage Destinations** and configure the destination there. Then click **Next**.
5. Choose whether to create an on-demand sync, recurring sync, or real-time sync. Recurring syncs run on an hourly or daily schedule, while real-time syncs update each minute.

   Depending on your choice in step 4, you may also need to specify a customer account or API target to sync to.
6. Click **Sync**. Your sync is active.

## Email notifications

Amplitude automatically sends email alerts for cohort sync jobs:

- **Success notifications**: Receive confirmation when your cohort sync completes successfully.
- **Failure notifications**: Receive an alert when a sync job fails, so you can address issues quickly.

These notifications help you monitor cohort sync status without manually checking the platform.

## View sync details

After you create a sync, click the sync name in the _Syncs_ panel to view its details.

The _Details_ tab provides basic information about the sync. The example above is a cohort sync, so the _Details_ tab provides a definition of the cohort, as well as a chart detailing its population over time. The _Syncs_ tab shows each destination that receives this sync.

On the _Comparisons_ tab, you can view a head-to-head comparison between this synced cohort and another cohort of your choosing. You can break down the results of the User Composition chart by user property using the _Composition by_ drop-down.

To view a list of your synced cohorts from within Amplitude Analytics, click **Cohorts** and open the **Synced Cohorts** tab.

## Understanding cohort sync discrepancies

When syncing cohorts from Amplitude to a third-party destination, you may notice differences between the user numbers in Amplitude and on the partner's platform. Understanding why these differences occur and how to check which users transferred successfully can help you fix these issues.

Amplitude lets you choose any user properties to sync. This aids in customization, but it also requires careful planning to minimize discrepancies during a cohort sync.

Common reasons for differences in cohort syncs include:

- **Unresolved mapping**: If a user property isn't set, or is `NULL`, Amplitude can't sync the user attached to the property. For example, if you're syncing a cohort of 100 users to a platform using email as the `User_ID`, but only 50 users provided an email, only those 50 users sync. Check and fix your data at the source, update it in Amplitude, and then run another sync.
- **Invalid mapped properties**: Properties that don't conform to the expected format in third-party destinations can cause partial or failed syncs. For example, the downstream destination may not accept a particular identifier format, such as email or phone number.

> **Note:**
>
> If a sync is partially successful, Amplitude still marks the entire cohort sync as successful, regardless of whether individual users are valid.

## Warning when updating cohort mapping

Amplitude issues a warning if you attempt to modify the Amplitude user property mapping, because modifying the mapping can affect active cohort syncs. Click **View Syncs** to view the syncs that the change could affect. From there, decide if you want to turn off the sync.

Even if you don't receive a warning, be careful when modifying mapping properties. Mapping changes can cause unexpected changes in the number of users tracked.

For example, if you stop mapping by email addresses and switch to phone numbers, users previously synced with their emails don't receive updates. Your change only affects new users. Amplitude syncs new users based on phone numbers, while previously existing users still sync based on email addresses. Over time, this can lead to data discrepancies.

If your cohort sync process has been in place for some time and you're considering changing the mapping, create a new sync destination first. Then proceed with the sync using this new target.

## View sync history

The cohort sync history page provides a detailed breakdown of cohort syncs over the last 14 days. Each cohort sync provides a list of skipped, added, or removed users. To access the page, follow these steps:

1. Click the **Cohorts** tab.
2. Choose the specific cohort of interest.
3. Click the **Syncs** tab.
4. If the cohort sync includes multiple destinations, select the appropriate cohort destination.
5. Click the **History** tab.

> **Note:**
>
> The detailed cohort sync history page supports all cohort sync destinations except for [Amazon S3](https://amplitude.com/docs/data/destination-catalog/amazon-s3) and [TradeDesk](https://amplitude.com/docs/data/destination-catalog/thetradedesk). These destinations continuously perform a full sync of users, not just an initial sync followed by incremental changes. This sync behavior makes CSV exports impractical.

## Inspect exported cohorts using CSV export

To find out which users and how many users Amplitude exported from your cohort to your third-party destination, export a CSV containing all exported users.

The CSV export includes the following columns:

- **Amplitude\_id**: Displays the unique Amplitude ID associated with each user.
- **Operation**: Indicates whether Amplitude added or removed a user from cohort membership.
- **Mapped properties**: This column shows the mapped user identifier for the cohort sync.
- **Skip\_detected**: Shows if Amplitude skipped a user during the cohort sync process.
- **Skip\_reason**: High-level categorization of why Amplitude skipped a user.

  - **Unresolved mapping**: Amplitude skipped this user during the cohort sync because the mapped property used to identify the user is missing or has no value.
  - **Rejected by partner**: The third-party destination rejected this user because the mapped property doesn't adhere to the required format. For example, if data fields aren't in the correct numeric or email format, the destination excludes the user from the cohort sync.

Some user properties may be incomplete or out of compliance with the target platform's criteria. A cohort sync success rate over 80% is often acceptable for advertising campaigns. For email campaigns or A/B testing, use a rate above 95%.

If there are many skipped entries, there may be a data quality issue at the source. To resolve this issue, review the CSV file to pinpoint discrepancies. Then make appropriate corrections to the user data when you're importing it into Amplitude. After you make corrections, launch the cohort sync process again to confirm the accuracy and consistency of your data.

## Additional considerations

- **Real-time cohort sync**: With Amplitude's Real-Time Sync (RTS) feature, the cohort sync history page doesn't allow you to export a CSV for users skipped during the sync. For detailed tracking of skipped users, use hourly or daily syncs instead of real-time syncs.
- **Users are silently dropped upon reaching destination**: Some destinations may return a 2XX response to indicate a successful cohort sync from Amplitude, even though the destination silently dropped users who didn't meet its criteria. In these cases, confirm that Amplitude exported a specific user by checking the CSV file.

> **Note:**
>
> Amplitude uses response codes to detect when third-party destinations don't include users. In some cases, Amplitude can't identify these users. If you have questions, post in the [Amplitude community](https://community.amplitude.com/) or contact the [Support team](https://help.amplitude.com/hc/en-us/requests/new) for assistance.

## Supported destinations

Refer to the [Destination Catalog](https://amplitude.com/docs/data/destination-catalog).

