Setting Up Beam-R2 Data Conflict Rules

‍

With Beam’s R2 integration, you can enrich your R2 product entries with up-to-date data directly from your product manufacturer’s data repositories. During the data enrichment process, you may run into data conflict issues where Beam's product matching algorithm may find a piece of product data that conflicts with data that you already have in R2. To address these conflicts, Beam lets you set up data conflict rules that dictate which data point to keep. In this tutorial, we'll show you how to configure these data conflict rules in the Beam workspace.

Data conflict rules are set up in the Configuration section of the Beam workspace. To access R2 configuration click on the Configuration button in the sidebar.

On the configuration page, navigate to the R2 configuration by clicking Integrations and then click the Configure button on R2.

In the R2 configuration menu, click on Field Mapping.

In this tab, you will see how your R2 data fields (on the left) are mapped onto your Beam data fields (on the right).

NOTE: This mapping can not be changed from within the Beam UI as it is set up by your R2 workspace admin and Beam Customer Enablement Specialist.

‍

Using the toggle buttons, you can tell Beam which data you want to prioritize in the event of a conflict. In the example below for example, the user has set up their mapping such that if Beam and R2 have different values for the Description, Product Warranty, Manufacturer, or Model, Beam will select and sync the values that Beam's product matching algorithm identified, thus overwriting the values that currently exist in R2. Similarly, if Beam identifies conflicting data between R2’s ‘description’ and Beam’s ‘Product Name’ fields, it will take R2’s description into account to sync the data

‍

It is worth noting, that while these rules are applied to all products enriched by Beam, you will have the option to override these rules on a product-specific basis when you are syncing data between Beam and R2.