Cloud Sync

Cloud Sync is a priced offering. Reach out to your CSM or Account Manager to learn more.

Cloud Sync lets you automatically synchronize customer data from your data warehouse or your relational databases into Batch without building custom pipelines or relying on third-party tools.

In just a few minutes, your profile data and behavioral events stay up to date in Batch, helping you launch campaigns faster, reduce engineering dependency, and simplify implementation.

---

What can you sync?

Cloud Sync supports two Destination types:

Destination	What it does
Batch Profile attributes	Updates customer profile attributes (email, plan, country, lifetime value, etc.) in Batch from a table containing one row per profile.
Batch Profile events	Creates behavioral events (purchases, add-to-cart, page views, etc.) in Batch from a table containing one row per event.

You select the destination type when creating a sync in the Batch dashboard.

Note that in addition to Cloud Sync, Batch offers a capacity to connect to Ads destinations, through Ads Sync.

Cloud Sync supports a large variery of Sources:

This sections explains in specific sub-pages the different databases and data warehouses we can integrate with, through Cloud Sync.

It is possible to integrate Batch with other databases or data warehouse, on request. Reach out to your CSM or Account Manager to learn more.

---

How it works

All Cloud Sync configurations share the same core mechanism:

1. You prepare a table or view in your data source that follows the Cloud Sync schema (required columns, naming conventions, type formatting).
2. You create a sync in the Batch dashboard by selecting a source, a sync frequency, and a destination type.
3. Batch runs incremental syncs on your chosen schedule, fetching only rows that changed since the last run using a last_updated_at cursor.

Once enabled, Batch automatically handles batching, retries, and error reporting.

Rate limits — Cloud Sync writes profile attributes and events to Batch through the same pipeline as the Profile API /profiles/mass-update endpoint, and is therefore subject to the same rate limit. See Mass update profile → Rate Limiting.