Sync Modes
Detailed technical description of the upsert and mirror sync modes for the Reverse ETL sources.
Last updated
Was this helpful?
Detailed technical description of the upsert and mirror sync modes for the Reverse ETL sources.
Last updated
Was this helpful?
The Reverse ETL sources support two sync modes that let you define how to sync your data to the destination:
Upsert mode
Mirror mode
Currently, the Redshift, PostgreSQL, Snowflake, and BigQuery warehouse sources support syncing data via these sync modes.
You can configure the sync mode while connecting a destination with your Reverse ETL source.
By default, these modes sync the data incrementally, meaning they only sync the new data. However, you can choose to run a full sync manually.
In this mode, RudderStack supports insertion of new records and updates to the existing records, while syncing data to the destination.
The upsert mode is supported for all destinations connected to the above-mentioned Reverse ETL sources, except Facebook Custom Audience.
Whenever the columns mapping is changed, RudderStack runs a full sync the next time.
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.
This mode is currently supported only for the Facebook Custom Audience destination connected to the above-mentioned Reverse ETL sources.
Whenever the columns mapping is changed, RudderStack runs a full sync the next time. While performing a full sync, RudderStack first deletes all the existing records and then syncs the records as per the latest column mappings.
In case of an unsuccessful delivery, RudderStack retries sending the events in the next sync.
For queries on any of the sections covered in this guide, you can contact us or start a conversation in our Slack community.
