Live Syncs

Activate Streaming Datasets in Real-time with Live Syncs

Live Syncs are a type of sync that enable real-time data activation. In comparison with traditional "Triggered" syncs, they can provide single-second latency in activating data into a destination. Live syncs are available on our Enterprise plan. While a Live Sync is enabled, Census continually monitors the Source connection, ensuring that any new data is instantly captured and activated.

At this time, a sync's Run Mode (Live vs Triggered) cannot be changed after the sync has been created.

Setting up the Run Mode for a new Sync

The following table summarizes the key differences between a Live and Triggered sync.

Live	Triggered
Real-time; sub-second latency	Minimum latency at least a few minutes
Census monitors the source 24/7 automatically	Can be run manually, on a schedule, or via external triggers. See Triggering & Scheduling.
Only streaming-capable sources are supported	All Source connections supported
Activates data as it changes	Activates records in batches

Supported Sources

Live Syncs are available for sources capable of streaming data, such as Confluent Cloud, Kafka, Google PubSub, Materialize, HTTP Requests, Snowflake, and Databricks*. Please feel free to request a new integration if your streaming infrastructure is not yet supported.

* Coming soon. Email [e-mail] to be added to the private preview.

Supported Destinations

Live Syncs can activate data in real time in all Census destinations with a few exceptions:

• Amazon S3

• Anaplan

• Azure Blob Storage

• Box

• Customer.io Collections

• Google Analytics (UA)

• Google Cloud Storage

• Google Sheets

• SFTP

Additionally, the following Live Sync-compatible sources cannot be used with the Mirror sync behavior, regardless of whether using Live or Triggered run mode:

• Confluent Cloud

• HTTP Request

• Kafka

• Materialize