# Sync Cohorts with Destinations

Source: https://amplitude.com/docs/data/sync-cohorts-with-destinations

---

On this page

- [One-time sync](#one-time-sync)
- [Scheduled sync](#scheduled-sync)
- [Real-time sync](#real-time-sync)

# Sync Cohorts with Destinations

You can synchronize the cohorts you create in Amplitude with third-party [destinations](/docs/data/destination-catalog) like ad networks, attribution providers, and marketing automation platforms.

The sync cadence you define affects both how often Amplitude sends cohorts or cohort updates to the destination, and which destinations are available.

## One-time sync

Use a one-time sync to send a cohort to your destination once. Use this option if you need to export a cohort to the destination and don't require continuous updates.

## Scheduled sync

Use a scheduled sync to send cohort updates to your destination on an **hourly** or **daily** basis. Amplitude queues sync jobs throughout the hour or day, depending on your selection. You can't select the time of day that a sync occurs.

Scheduled 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 sync

Use a real-time sync to keep the destination updated with the most recent cohort information. Real-time sync checks for updates and sends them to the destination every minute.

Amplitude recommends real-time syncs for cohorts that require minute-by-minute precision and 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, hourly sync may work better for your use case.

Real-time sync limitations

Real-time sync supports cohorts of 1,000,000 users or fewer, and all cohort types except:

- Funnel
- Retention
- Stickiness
- Nth time event
- Event within
- Distinct interval

Real-time sync supports all cohort destinations except:

- [Facebook Ads](/docs/data/destination-catalog/facebook-ads)
- [Google Ads](/docs/data/destination-catalog/google-ads-cohort-syncing)
- [Twitter (X) Ads](/docs/data/destination-catalog/twitter-ads-cohort)
- [Hubspot](/docs/data/destination-catalog/hubspot-cohort-sync)
- [Qualtrics](/docs/data/destination-catalog/qualtrics)
- [S3 cohort sync](/docs/data/destination-catalog/amazon-s3-cohort)
- [TikTok Ads](/docs/data/destination-catalog/tiktok-ads)
- [Enterpret](/docs/data/destination-catalog/enterpret)
- [SFMC](/docs/data/destination-catalog/salesforce-marketing-cloud-v2)
- [The Trade Desk](/docs/data/destination-catalog/thetradedesk)

Was this helpful?

<!--$-->

<!--/$-->