Reverse ETL Sync Modes

The Reverse ETL sources support two sync modes that you can configure while connecting them to a destination. These modes define how RudderStack syncs your data to the destination:

• Upsert mode
• Mirror mode

Note that:

• When you sync data from the source for the first time, RudderStack performs a full sync by default, irrespective of the sync mode. It then incrementally syncs any new data since the last sync. However, you can force a full data sync using the Force Full Resync option.

• The following sources support syncing data using both upsert and mirror mode:

  • BigQuery
  • Databricks
  • MySQL
  • PostgreSQL
  • Redshift
  • Snowflake
  • Trino

Upsert mode

In this mode, RudderStack supports insertion of new records and updates to the existing records, while syncing data to the destination.

RudderStack supports upsert mode for all destinations except Facebook Custom Audience, Google Ads Remarketing Lists (Customer Match), and Marketo Static Lists.

Whenever you update the column mappings, RudderStack runs a full sync the next time.

Mirror mode

In this mode, RudderStack ‘mirrors’ the source by keeping the destination data the same as the source data. It performs insertion, updates, and deletion of records while syncing data to the destination.

RudderStack does not support track event type for this mode.

RudderStack supports mirror mode for the following destinations:

• Criteo Audience
• Facebook Custom Audience
• Google Ads Remarketing Lists (Customer Match)
• Marketo Static Lists
• Trade Desk Audience

Whenever you update the column mappings, RudderStack runs a full sync the next time. While performing a full sync, RudderStack first deletes all existing records and then syncs the records as per the latest column mappings.

FAQ

What happens to the records that have not been successfully sent to the destination in the previous sync?

In case of an unsuccessful delivery, RudderStack retries sending the events in the next sync.

Questions? Contact us by email or on Slack