This guide is applicable for the Reverse ETL sources configured using the Table option. If you have configured your Reverse ETL source using the Model option, refer to the Importing Data using Models guide.

RudderStack gives you two options to map your warehouse columns to specific destination fields while importing the data:

  • Map with Visualizer (Refer to the Visual Data Mapper guide for the list of the supported destinations.)
  • Map with JSON

This guide lists the JSON mapping settings required to import and sync data from your warehouse table to the specified destination.

Data import settings

The settings to import and sync data from your warehouse table are as shown:

Data import settings in RudderStack
  • Schema: Specify your warehouse schema.
  • Table: Specify the table residing in the above schema from which you want RudderStack to import the data.
  • Sync mode: Select the sync mode that RudderStack uses to sync your data.
RudderStack supports two modes for syncing your data - Upsert and Mirror. For more information on these modes, refer to the Sync Modes guide.
  • Primary Key: Select a column from the table specified above to uniquely identify your records in the warehouse.
RudderStack uses this column for diffing in the case of incremental syncs.
  • Choose user identifier: Choose atleast one user identifier from user_id and anonymous_id from the dropdown.

You will also be able to preview a snippet of your data, as shown:

Schema tab options in RudderStack

Here, you can select all or only specific columns of your choice, search the columns by a keyword, and also edit the JSON Trait Key. You can also preview the resulting JSON on the right.

The JSON payload carries the user_id and anonymous_id from the columns selected in the Choose user identifier section. Moreover, the traits are used from the columns selected in the Column section.

Add Constant

You can also use the Add Constant option to add a constant key-value pair which is always sent in the JSON payload, as shown:

add constant

The new constant will appear in the table and also in the JSON preview inside the traits, as shown:

add constant in json

You can also use the dot notation to define a constant, as shown:

dot notation constant

Once you have finalized the configuration, click Save.

Updating an existing configuration

To update an existing configuration, follow these steps:

  1. Go to the Schema tab of your configured source.
  2. Click on the Update button on the top right, as shown:
Updating table selection
  1. Update your column selection.
When updating the configuration, you can only change the existing mappings. The Schema, Table, Sync mode, and the User identifier fields are not editable.
  1. Finally, click the Save button.
After updating the configuration, the next sync will be a full sync.

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

On this page