Revenue Conduit: Features & Settings

RC Feature: Field To Field Sync for Infusionsoft

Note: We can only detect and sync fields that are native to your shopping cart. We cannot sync custom shopping cart order or customer data that is outside the standard fields for your cart, so if you're using a 3rd party app that is creating custom fields, or you've manually created your own custom fields then this Field to Field feature will not be able to see the fields from that 3rd party app nor the fields you created. Additionally, we cannot sync account username or password fields from your shopping cart, as these are more secure and protected fields within your cart.

Note: If the Infusionsoft Fields you want to use in this feature are NOT showing up in Revenue Conduit, please click the Refresh Fields button in the top right corner and wait 1-2 minutes, then refresh the page. You may need to Logout of Revenue Conduit and log back in if they still aren’t refreshing. Here’s our full article on Refreshing Fields.

Step 1: Create an Infusionsoft custom field in Infusionsoft for your data to get mapped to in Revenue Conduit. Here is Infusionsoft's documentation on how to perform this task

Step 2: Map the custom field created in Infusionsoft to the Revenue Conduit admin portal here Once your logged in you can click on the Infusionsoft tab and then on the Field to Field sync tab. Underneath the dropdown for the store fields, select the field from your store you would like to map. Under the Infusionsoft field, select the field that you created in Infusionsoft for the store data to be deposited and then click add.

Step 3: To see where the field will reside, you can select any contact record page in Infusionsoft and go to it. In the top row of blue tabs, you will see one titled Custom Fields. If you click on the custom fields you will see all the fields you created in step 1 and this is where the information will reside.

To see a list of available fields per shopping cart and how to set up the custom fields please see our Field Types Protocol and Best Practices