Skip to main content

Custom Record Deduping in Outreach

Aye
Updated

Objective

The purpose of this article is to provide direction to Outreach Admins for customizing the deduping criteria when syncing records with CRM.

Applies To

  • Outreach Admins

Before you begin

  • Outreach recommends testing this process in an Outreach Sandbox environment before making changes in the production org.
  • Outreach recommends not setting record deduping on text fields that store long strings. Custom deduping is meant for text fields that store short strings that you can use to dedupe one record from another.

Procedure

  1. Log in to Outreach as an Admin.
  2. Click Administration > Integrations > CRM.
  3. Select the object mapping for which you want to customize deduping criteria
  4. Select the More Actions > Advanced Settings button next to the field mapping that you want to use for deduping when syncing records.
    Screenshot 2024-08-16 at 12.18.08 PM.png
  5. In the Record Deduping dropdown, select if you want to use the field mapping for deduping when syncing data from CRM to Outreach, Outreach to CRM, or in both directions.  This will cause Outreach to use the selected field mapping as a unique identifier when syncing in the direction specified.
  6. Click Done.

Frequently Asked Questions

Q: What happens if I have a record deduping set on more than one field?

A: We will use the combination of all fields on which deduping is set to find existing records in the system before creating a new record.

Q: Why is record deduping not available on any field mapping for Lead and Contact objects?

A:  We use email for deduping prospect records in Outreach. This is preconfigured and cannot be customized. If you have purposeful duplicates enabled on your Outreach org, you can configure custom record deduping for the Lead and Contact objects.

Q: Why am I seeing a message that record deduping will be disabled on unrelated fields when deleting a field mapping?

A: For deduping to work when syncing records into Outreach, we require record deduping to be set on at least one queueable field. If you have only one queryable field in the deduping criteria and you choose to delete this field mapping, we will remove deduping from all other non queryable fields. 

Related articles