Visual Data Mapper

The Visual Data Mapper (VDM) offers an intuitive UI to map your warehouse columns to specific destination fields. This is useful especially when mapping your warehouse data to custom fields defined in your destination.

To use this feature, you can use a Reverse ETL source and then connect it to a VDM-supported destination.

Using the Visual Data Mapper

To use the Visual Data Mapper, follow these steps:

  1. Set up a Reverse ETL source and connect it to a destination. You should then see the following screen:
vdm object
If you have set up the source using the Model option, the Schema and Table fields are replaced by the Model field, as shown: VDM model options

By default, Visual Data Mapping is enabled for all the VDM-supported destinations. To configure the data via JSON, click on the Map with JSON button.

  1. Choose the source Model or Schema + Table from where you want RudderStack to import and sync the data.

Upon selection, RudderStack automatically loads the relevant resources. If you have added a new model or warehouse table during this configuration process, click on Reload models/Reload schemas and tables to fetch the latest resources.

  1. Then, select the destination Object where you want to sync the data. An example in case of Customer.io destination is shown below:
vdm 2

RudderStack automatically loads all the relevant destination objects. If you have added a new destination object during this configuration process, click on Reload objects to get all the latest objects.

RudderStack does not support objects that do not have any fields or a unique user identifier.

Choosing the identifier

In the Choose Identifier section, choose a warehouse column and destination field to map your records from the source to the destination. You can choose any column from the dropdown which will act as a unique identifier. An example is shown below:

vdm 3

The identifier (Map with Visualizer) or user_id/anonymous_id (Map with JSON) fields must have unique values in order to successfully sync the data to the destination. The records containing duplicate identifier values will fail to sync. For example, if you have chosen name as the identifier and it contains more than one values as 'Alex', the duplicate record will fail to sync.

Mapping the fields

In the Map Fields section, you can configure the source-destination field mappings by following these steps:

  1. Click on the Map another field option. Select the Destination field from the dropdown. Then, select the Warehouse column to map this field.
vdm 4

RudderStack gives you full visibility into the name and type of the fields that you are mapping.

Mandatory mappings

When sending events to some objects, there are some required fields that need to be mapped. These fields cannot be removed from the mappings. For example, in case of the Salesforce Account object, Account Name is a required field, as seen in the following image:

vdm 5

Mapping fields of different type/format

In case you are mapping fields with different data types or formats, you can use the Transformations feature to do type conversion before sending the events data.

For example, RudderStack lets you map the warehouse column Phone of type string to a destination field Company ID of type float . You can then add a transformation at the destination end to do this type conversion to ensure there is no mismatch.

vdm 6

Creating a custom destination field

This feature is currently available for the following destinations:

RudderStack lets you create a custom destination field and map it to a warehouse column by following the below steps:

  1. Click on the Map another field option.
  2. Type the name of the custom destination field that you want to create, as shown:
Map another field
  1. Finally, click on Create.

Once you have mapped all the source columns to the destination fields, click on Next to complete the destination configuration.

Contact us

For any questions or issues on the Visual Data Mapper feature, you can contact us or start a conversation in our Slack community.

Contents