duplicates

How to Deduplicate People and Companies in Bulk and Automatically

You have multiple records that represent the same companies in Intercom. Contacts and conversations may end up associated with a duplicate company record, making them difficult to find, track, and analyze. Duplicate company records can also inhibit your support team from effectively segmenting and personalizing your communications.

Insycle's Merge Duplicates module can identify duplicate companies and merge them flexibly, in bulk, using advanced rules to select the master record and control data retention.

Process Summary

  1. Set rules to identify duplicates.
  2. Review and analyze the identified duplicates.
  3. Choose Bulk Mode.
  4. Set rules to select the master record and determine what field data is retained.
  5. Deduplicate your records in Intercom.

 

Step 1: Configure Rules to Identify Duplicates

Navigate to Data Management > Merge Duplicates, pick the Companies record type, and explore the default templates for a pre-built solution.

This template below matches duplicate Intercom companies using the exact match for the company name.

intercom-companies-template-&-Step-1.png

Click the "Find" button and Insycle will analyze your Intercom data to find duplicate companies using these rules.

Step 2: Analyze the Identified Duplicates

When two or more records represent the same company based on your rules from Step 1, they are clustered together into duplicate groups. Each duplicate group shows the total number of records that were identified as duplicates based on your settings. For example, if you had four records for the same company, it would count as one duplicate group with four duplicate records.

Under Step 2, each row represents a duplicate group, with the number indicating how many duplicate records were found. 

duplicate groups

When you click a row, it expands and shows the duplicate records in the group.

duplicate records in group

Explore the record data in the duplicate groups. Double-check to make sure that the fields you set up in Step 1 are showing what you expected. 

Looking at the record details in several duplicate groups, decide the best way to determine which is the master record the other records will be merged into. Learn more about common practices for picking a master record.

Add more columns to the view using the gear button on the right to get more context.

Step 3: Choose Bulk Mode

The most efficient and sustainable way to merge duplicates is in Bulk mode. This allows you to set rules for determining the master record automatically across all records in your database. With Bulk mode, you'll be able to use saved templates and recipes to repeat the process on a regular basis. 

Under Step 3, the Bulk operation tab is automatically selected. Leave this as is.

step-3-bulk-option.png

If you have duplicate groups that contain more than five records, you may want to change the value in Skip duplicate groups with more than [5] records per group to make sure you can get them all.

Note: When merging in bulk, Insycle limits the duplicate group size based on the entered 'skip' value, skipping groups that contain more records. This is a precaution to ensure that if you use a duplicate matching filter that is too broad in Step 1, you don't accidentally merge a lot of non-duplicate records together. You can adjust the skip value as needed, up to 100 per duplicate group. 

In Manual mode, you have complete control over which records are merged together by selecting them from the Record Viewer. Manual mode should be reserved only for cases where you need a careful, controlled process. Learn more about merging duplicates in Manual mode.

Step 4: Set Rules for Master Record Selection and Data Retention

Configure Rules to Automatically Select the Master Record

Under Step 4 on the Records tab, you define how all of the matching duplicate groups should be merged at scale. To do this you need to create a series of rules that tell Insycle how to select the record from each group to become the master. The master is the record that will remain after the merge.

For example, if you had four records representing the same company, they would make up one duplicate group with four records, all of which would be merged into one master record. The other three records would not exist anymore.

On Step 4, select the matching method—Priority Match, or Absolute Match.

Priority Match looks through the master selection rules one by one, in order. As soon as a record meets one of the criteria, this becomes the master and the rest of the rules are skipped. Most de-duplication operations should use Priority Match.

With Absolute Match, a record must meet all of the listed rules in the Record tab in Step 4 to become the master. If a record does not match every rule listed, no master record will be identified. Absolute Match is appropriate for less flexible master selection. Learn more about these options in the Advanced How-Tos below.

step-4-priority-match-no-arrow-2023-06-01.png

For each duplicate group, Insycle will look at each Record rule to see which of the records in the group meet the criteria. Rules are read in order, from top to bottom and as soon as a record is the only one to meet a rule, it is selected as the master record. The subsequent rules are ignored. 

master record

If none of the records in the duplicate group match any of the rules, the automatic master selection for the group fails. See the Troubleshooting section below for more details.

Configure Rules That Determine Values to Keep

After Insycle has identified the master record, it will use the Field selection rules to automatically pick which values from a duplicate group will be used in the master record.

Duplicates may be exact match versions of another record, but often there is only partial data overlap between the records. When data is split between two different records, both records may contain unique and important information about the customer that you'd like to keep.

Under Step 4, click the Fields tab. For each field you want to control the data retention for, you need to select a Field and tell it where the data for the field should be taken from. This is merged into the master. Any data that is not in the master or not copied to the master is deleted.

step-4-fields-tab-arrow.png

The Criteria dropdown gives you various options for choosing the data to keep:

merge-duplicates-intercom-companies-step-4-field-rules.png

  • From master record – Use the value that exists in the master record.
  • From master record (even empty) – If the field on the selected master record is blank, keep it that way. Don’t automatically fill it in with a value from the most recently updated record.
  • From record where value – Select data from one of the records in the duplicate group based on the values. These options vary depending on the field type. For example, retain the data in the Company Size field that has the highest value.
  • From record based on other field value – Look at the value in a different field to decide which value from the duplicate group should be kept. The example above highlights how a Company Last Seen value can be used to determine which Company Industry value to use.
  • Combine and append all values – You can merge the values from the selected field for all records in the group. For example, if there is some type of Notes field, you could keep the notes from all of the records in the duplicate group.
  • Collect all values from other field – Select a destination field to copy and combine values into, then select what field the data should come from. For example, this could be used to keep the record Owner values of all duplicates and combine them into a custom field.
  • Collect non-master values from other field – Aggregate the values of all the duplicates that are not the master, meaning this excludes the value from the master record itself. This can be especially helpful if you want a record of the object IDs that were removed, so you can also remove them from another system. Select a destination field to copy and combine values into, then select what field the data should come from.

Remember: The Fields tab is a separate set of rules for automatically selecting what data to keep. You still need to configure the rules for automatically selecting the master record in the Record tab.

Step 5: Review Changes and Merge Records

Preview Merged Changes in CSV Report

Now with the filters and master record set up, you can preview the changes you are making to your data. That way, you can check to ensure your deduplication configuration is working as expected before those changes are pushed to your live database. The CSV report that Insycle generates includes records from all the duplicate groups.

Under Step 5, click the Review button and select Preview mode.

merge-duplicates-step-5-review-preview-mode-intercom.png

Click the Next button to go to the Notify screen, where you can select recipients for the email report. You can also add additional context on this screen.

On the When tab, click the Run Now tab, and select which records to apply the change to (you could do All, but if you have a large number of duplicates, you may just want to do a chunk for your preview), then click the Run Now button.

merge-duplicates-step-5-review-preview-run-now.png

Insycle will generate a preview CSV and send it to your email. Open the CSV file from your email in a spreadsheet application.

csv report master

The Result column identifies which were picked as master, and which were identified as duplicates and merged into the master. You'll see the values:

  • Duplicate – The record is part of a duplicate group.
  • Master The master record that was chosen for the duplicate group based on your rules.
  • Master (After) – For each duplicate group, the Master (After) row will show the data the final record will contain, based on master selection and field data retention settings.
  • Error – If Insycle is not able to determine which record would be the master, an error message will appear here. See the Troubleshooting section below for more details.

When a field value in the CSV says "(Default)," it means that Intercom will be using its default processes for dealing with the field. This is typically done for blank fields, system IDs, and other specific situations.

Apply Changes to Your Intercom Records

If everything in your CSV preview looks correct, return to Insycle and move forward with applying the changes to the live Intercom data.

Under Step 5, click the Review button again, and this time select Update mode.

On the When tab, you should use Run Now the first time you apply these changes to Intercom. If you have a large number of records, you may want to do a smaller batch to review the results in your live CRM database.

merge-duplicates-step-5-review-update-run-now-selected.png

Save as a Template and Set Up Automation

After you've seen the results in Intercom and are satisfied with how the merge runs, you can save your configuration as a template.

Return to the Template menu at the top of the page and click Copy to save your configurations as a new version of whatever template you started with. Then click the pencil to edit your new template name.

save-template-copy-and-rename.png

Now you can set up automation so this merge operation runs on a set schedule.

Under Step 5, click the Review button, and select Update mode.

On the When tab, select Automate, and configure the frequency you'd like the template to run. When finished, click Schedule.

merge-duplicates-step-5-review-update-automate-daily.png

If you have several templates you'd like to automatically run together, you can create a Recipe.

Audit Trail and History

The Activity Tracker lets you review all changes made through Insycle. At any time you can download a CSV report of the operation and records affected.

Tips for Merging Duplicates

  • Begin with easy-to-find duplicates. Iterate through fields and rules you know will surface duplicates. Don’t expect to resolve all your duplicates by setting up and running this process once. You will need to run this process multiple times for different fields or nuanced variations.
  • Each time you get a Merge Duplicates process to run the way you want in your database, save it as a template. When you have a solid set of templates that reliably resolve most of your dupes, you can put them together as a Recipe that can run on a regular, automated schedule.
  • You may also need to look for edge cases that fall outside your standard rules. These may be templates you run manually so you can make adjustments based on what you find.
  • Do some experimentation. Use the Preview mode and CSV report to analyze patterns in the duplicates. You may learn what is causing the duplicates and learn how to avoid having them in the first place.

Advanced How-Tos

Step 1: Narrowing Down the Records with a Filter

Use the filter to work with a segment or smaller pool of records. Then Insycle will only analyze the remaining records for duplicates. To add filters, click the Filter button, then choose the field to look at, select the condition, and set the value to look for. The filter is applied before the matching step runs. 

dup10.png

You may want to use a filter if:

  • You know you only want to work with a subset of your data. In this case, there’s no need to run the operation on your whole database.
  • There are an overwhelming number of duplicate results. Add a filter to work with a reasonably sized subset while you work to get the configuration right. 
  • You want the operation to run faster. A refined segment can speed things up since there are fewer records to analyze.

Most of the options in the Field dropdown match the fields that are found in your CRM, and for Contact records, there are three additional options related to the Email value: 

  • Email Username: The portion of the email address before the “@.” For example, if the email address were “maria@acmewidgets.com,” the username value would be “maria.” 
  • Free Email Provider Domain: Choose True to filter out records where the email domain is Gmail, Hotmail, Yahoo, and about 10,000 other free email providers. This filter helps ensure these are real business contacts, or can determine which record is the legitimate one because it’s most likely customer companies aren't using free Gmail accounts (though a contact may have accidentally emailed us from a private account at some point). 
  • Email Top-Level Domain: The top-level domain (TLD) is everything that follows the final dot of a domain name. For example, in the domain name acmewidgets.com', '.com' is the TLD. Some other popular TLDs include '.org', '.uk', and '.edu'. 
Step 1: Setting Up the Fields
Field Name Comparison Rule Ignored Match Parts

Pick a field that you think has some duplicate values.

Running a very simple match operation like just First and Last Name can be helpful in giving you an idea of what you have, but it is too broad to use for reliable analysis and deduplication. There may be legitimate duplicate names–different people with the same first and last name. You need additional, unique criteria to narrow it down.

Choosing Unique Identifiers

Matching duplicates requires unique identifiers—data that is unlikely to be shared by any other record unless it is a duplicate. If you don't use unique identifiers, you are likely to identify unrelated records as duplicates and may accidentally merge them.

Many CRMs match first names, last names, and email addresses. If all of those match, or are similar, you can confidently determine that the record is a duplicate.

Other unique identifying fields that are commonly used in deduplication include:

    • Phone number
    • Mailing address
    • ID numbers

Each row in your matching fields setup is cumulative, so records must meet all of the criteria. For example, looking for records that have the same First Name, AND Last Name, AND Phone Number returns only results where all three values are the same.

To match against one field value OR another, you will need to run two different templates. For example, if you want to use fields like Phone Number OR Mobile Phone Number, you’ll run one template for Phone Number, then a second configured the same except with the Mobile Phone Number field.

The searched value must have four or more characters. For example, values of “Joe” will be ignored.

Step 1: Matching Using Two Different Fields 

Sometimes, you might want to match duplicates using data in two separate fields. For example, you might want to compare your Phone Number field to a Mobile Phone Number field to identify duplicates.

Using the Related Fields feature, you can use two different fields (that contain similar data) as matching fields to catch more duplicates.

You can set up Related Fields in the Advanced tab.

bulk-merge_2.png

Common Examples of Related Field Matching

Matching Field Related Fields
Phone Number Mobile Phone Number, Company Phone
Email Domain Website, Company Domain
Address Company Address
Step 4: Considerations When Picking a Master Record

For contacts, it's often useful to pick master records based on engagement. For example, the highest number of email clicks, or the most recent email opened. You can also use other statuses to pick a master record such as the furthest along in your sales lifecycle, or the most recently updated record. 

For companies, it's often useful to use associated records to determine the master record. For example, the highest number of associated contacts or deals. 

If you have a connected app, like Salesforce or an ERP system, pick the master record that is syncing with the other apps.

Step 4: Selecting Priority Match vs. Absolute Match

step-4-priority-match-no-arrow-2023-06-01.png

Priority Match: Looks through the master selection rules in order, one by one. As soon as a record meets one of the criteria, Insycle makes the master selection and skips the rest of the rules on the list. The vast majority of duplicate templates should use Priority Match.

Absolute Match: The master record must meet all of the listed rules in the Record tab in Step 4. If a record does not match every rule listed, no master record will be identified. Absolute Match is appropriate for less flexible master selection.

For example, if a company wants to ensure the chosen master record is in their sales pipeline and already has a sales rep working the record, they can choose Absolute Match and set the Record rules:

  • Lifecycle Stage is "lead"
  • Contact Owner exists

Choosing Absolute Match can often result in no master record being identified since the record has to match every rule listed, so in most cases, you should select Priority Match.

Step 4: Control What Field Data is Retained

The Merge Duplicates module allows you to control the values saved in the master record after the merge regardless of the default merge behavior. By adding each field you want to control the data retention for and selecting a Condition, you can tell Insycle where the data for the field should be taken from and how to handle it.

For example, if merging Intercom users, you may want to save all of the Owners from records that are merged together and deleted. You can add a new custom attribute, “Merged Owners” to your CRM.

intercom-ui-custom-attribute.png

Then in the Merge Duplicates module under the Fields tab of Step 4, add a rule to override the default merge behavior. Select the "Merged Owners" field, the "Collect non-master values from other field" criteria, and "Owner" as the other field. 

merge-duplicates-intercom-step-4-field-rules-custom-attributes.png

You can use the Preview to see how this will preserve the Owner values of all the duplicates in each duplicate group.

merge-duplicates-intercom-csv-collect-values-custom-attributes.png

Step 4: Customizing Merge Logic

For situations where you need more granular customization for picking duplicate records to include—or exclude—from the deduplication process, you can customize bulk deduplication using exclusions and pre-defined masters via a CSV file. Additionally, you can use this process when there are no common rules you can apply to choose the master record.

Troubleshooting

If you're not seeing the results you expect when merging duplicates, consider these issues:

Insycle was unable to determine the master record

If the Result column of the CSV report displays this error:

Cannot determine master record because multiple records (#) satisfy the master selection rules. In ‘Master Selection’, change/add/reorder the rules such that only one record satisfies them (if cannot determine master based on field values, use ‘ID is lowest’ as the last rule).

This error means that based on the master rules you set, Insycle could not figure out which would be the master.

Check Step 4 to ensure that you have Priority Match selected and not Absolute Match.

priority-or-absolute.png

With Priority Match, the rules configured in the Records tab of Step 4 are processed in order and your master record only has to match one rule. Using Absolute Match, your master record would have to meet all of the rule criteria. The majority of the time it is best to select Priority Match.

If Priority Match was used, then none of the records meet any of the criteria on the list more than the others. In this case, you'll need to experiment with Step 4, reordering or adding additional rules for fields likely to have unique values.

Not all identified duplicates are merging into the master

You have duplicate records that have been identified by Insycle but not all of them are merging into the master. Check to see how many duplicates are in the affected duplicate groups. If you have duplicate groups that contain more than five records, you may want to change the value in Skip duplicate groups with more than 5 records per group to make sure you can get them all.

dup12.png

This setting is intended to protect against the accidental merging of non-duplicate records if the filter in Step 1 is too broad.
Non-duplicate records are being merged together

There are a couple of things to look at that may be misidentifying records as duplicates.

First, you may need a better unique identifier. Under Step 1, if you only use fields that could correctly contain the same values in multiple records, these aren't unique identifiers. In this case, you are likely to identify unrelated records as duplicates and may accidentally merge them.

Unique identifiers are data that is unlikely to be shared by any other record unless it represents the same underlying entity. Fields that are commonly used in deduplication include phone numbers, email, mailing addresses, or ID numbers.

Second, this may indicate the Comparison Rule under Step 1 is too broad. Try using the Exact Match comparison rule instead of Similar Match. Similar Match looks for values that may be close but with a one-character difference (maybe a typo) which broadens the search. 

Remember, always run your deduplication in Preview Mode to confirm things are working as expected before running them in Update Mode and applying the changes to your CRM records.

Insycle isn't finding any duplicates

Most of the time when Insycle can't find duplicates, it is due to your matching rules in Step 1. To better understand how to set up your rules, it is important to analyze the underlying data. A useful exercise can be to set up your matching filters to look for exact matches of just First Name and Last Name. 

step-1-fname-Lname-only.png

When you click the Find button, these rules can show you a broad overview of what duplicates are potentially in your database, and what fields might be useful to include in your matching fields. These settings are just for discovery and should not be used for a final merge operation; many people can have the same first and last names and are not duplicates. 

To get further context, click the gear button on the right side of the Record Viewer pane. Here, you can add any field in your database as a column to the Record Viewer to better understand the data inside of these records. 

dup15.png

There are errors in the CSV Result column

If the Result column of the CSV displays an error, read the error text for help figuring out how to resolve the problem.

dup16.png

The most common error is:

Cannot determine master record because multiple records (#) satisfy the master selection rules. In ‘Master Selection’, change/add/reorder the rules such that only one record satisfies them (if cannot determine master based on field values, use ‘ID is lowest’ as the last rule).

This means that based on all the rules, Insycle could not figure out which would be the master. None of the records meet more of the rules than others. In this case, you'll need to experiment with reordering or adding additional fields likely to have unique values under Step 4.

It's taking a long time for Insycle to find duplicates

It can take a while for Insycle to find and match duplicates if the fields being used to identify them have very long values. The longer the values, the longer it takes Insycle to process the data and generate the results. This might come up when looking for matches based on long ID numbers, LinkedIn bio links, or other URLs with long strings attached (ex, https://www.linkedin.com/in/svadin%C3%ADr-n%C4%9Bmec-1234b31a3/).

You can speed this up by limiting how much of the value Insycle looks at.

If the beginning or ending portion of the values are all unique, you can limit the comparison to the first or last several characters using the Match Parts parameter under Step 1

merge-duplicates-linkedin-bio-step-1-match-parts-last-9-chars.png

merge-duplicates-linkedin-bio-step-2-last-9-chars.png

Or use the Ignore Text (Substrings) parameter, then click the Terms button.

merge-duplicates-linkedin-bio-step-1-ignored-text-terms-button.png

On the Ignored Text tab of the popup, add the common portion of the URL or text string.

merge-duplicates-linkedin-bio-step-1-ignored-text-popup.png

For more help troubleshooting issues with Insycle, refer to our Troubleshooting Issues article.

Frequently Asked Questions

How can I find duplicates when one field is empty?

When using two or more fields to identify duplicates, records can still be considered matches even if one of the field values is blank. You just need to specify which field(s) allow a blank value.

Under Step 1, configure your matching rules in the Simple tab, then click the Conditions tab.

step-1-allow-empty_1.png

All the matching fields you included will automatically appear with the Value Required in All Records condition selected. Change the condition to Empty Allowed in Any Record to allow empty values for certain fields. You can also use the At Least One Record with Non-Empty condition to help you determine which is the master record. Make sure at least one field remains required and is a reliable unique identifier to ensure the records are really duplicates.

step-1-conditions-empty-not-empty.png

For example, on the Simple tab, you may have the matching fields: First Name, Last Name, and Phone Number. But on some of your records, the Phone Number field may be empty. Using the Condition "Empty Allowed in Any Record" or "At Least One Record with Non-Empty," all records with the same name, same phone number, and no phone number will be considered duplicates.

step-1-allow-empty-review.png

Can I match duplicates using two different fields?

Yes. This can be done, for example, if you want to look at both the Phone Number field values and Mobile Phone Number field values as a single pool of values to compare between records and identify duplicates.

Using the Related Fields feature, you can use two different fields (that contain similar data) as matching fields to catch more duplicates. You can set up Related Fields in the Advanced tab.

step-1_related-field.png

How do I ensure that I am not merging non-duplicate records together?

Currently, there are two ways to make sure that the records that you are merging are indeed duplicate records.

First, always run your deduplication templates in Preview Mode before running them in Update Mode. This produces a CSV that shows you how your records would have been merged. Then you can ensure that your Merge Duplicates template is working as expected and not merging non-duplicate records together.

Additionally, you can reduce the risk when merging duplicates by narrowing your duplicate matching settings in Step 1. Try the Exact Match Comparison Rule instead of Similar Match. Then make sure that you are using actual uniquely identifying fields—first name, last name, email, and phone number are popular choices. The more tightly defined your filter is, the less likely you are to merge non-duplicate records.

Insycle is having trouble determining a master record. What could be causing this issue?

If the Result column of the CSV report displays this error:

Cannot determine master record because multiple records (#) satisfy the master selection rules. In ‘Master Selection’, change/add/reorder the rules such that only one record satisfies them (if cannot determine master based on field values, use ‘ID is lowest’ as the last rule).

This error means that based on the master rules you set, Insycle could not figure out which would be the master.

Check Step 4 to ensure that you have Priority Match selected and not Absolute Match.

step-4-priority-match.png

With Priority Match, the rules configured in the Records tab of Step 4 are processed in order and your master record only has to match one rule. Using Absolute Match, your master record would have to meet all of the rule criteria. The majority of the time it is best to select Priority Match.

If Priority Match was used, then none of the records meet any of the criteria on the list more than the others. In this case, you'll need to experiment with Step 4, reordering or adding additional rules for fields likely to have unique values.

I already have a list of duplicate Intercom companies, can Insycle bulk merge them?

Yes. You can use a customized list of duplicates and use the Magical Import module to tag duplicates in your Intercom CRM, then use the Merge Duplicates module to deduplicate in bulk. Include ID numbers from Intercom in your CSV.

Can I select which data is retained in my master record on a field-by-field basis?

Yes, Insycle allows you to select which field data is retained in the master record using the Fields tab under Step 4. See the Bulk Merge Duplicate People, Companies article for more detail.

step-4-field-selection.png
I need to exclude some records from deduplication. Can I do that?

Yes. You can exclude records from deduplication by including a "Deduplication Exclude" field in your CSV, as detailed in the Customize Bulk Deduplication Using Exclusions and Pre-Defined Masters article.

My team needs to review and approve the master, can I accommodate that with Insycle?

Yes, there are several ways to share details and get approval before merging duplicates.

You can manually approve master records and mark them in a CSV, then use Insycle to bulk deduplicate down to those master records. Consult with this Customize Bulk Deduplication Using Exclusions and Pre-Defined Masters article to learn more.

Or, you can run the Merge Duplicates module in Preview Mode, then deliver the preview CSV that Insycle generates. The CSV report that Insycle generates includes your entire merge operation down to individual duplicate groups but does not update your live data. Then your team can approve the merge based on this report, before running Merge Duplicates in Update Mode.

Additionally, team members can review duplicates and manually select the master for each record under Step 4. Review the Manually Merge Duplicates article for more detail.

step-4-manual-select.png

Do my matching fields have to match each other exactly?

No. The Similar Match Comparison Rule found in Step 1 looks for values that may be close but with a one-character difference (maybe a typo) and broadens the search. This search behaves like when Google shows results for a slightly different term, or says “Did you mean...” For example, if a Company Name of, “Acme” is found, it could include records with the Company Name values “Akme, acm, Acma,” etc., as a match.

You should be careful when using Similar Match as the looser criteria can incorrectly identify non-duplicates as duplicates. 

Review the Understanding Similar Matching best practices for more detail.

Why can I only process 50 duplicate groups at a time?

Insycle shows 50 records on the module screen as a preview, this isn't the entire list of records. Include All records when you view the Preview CSV report to see everything.

Insycle can process thousands of duplicate groups in one operation. Potentially, you could deduplicate your entire database in one operation. 

How many duplicates can I merge into one master record?

You can merge up to 100 duplicate records into a single master record. 

If you have duplicate groups that contain more than five records, you may want to change the value in Skip duplicate groups with more than 5 records per group under Step 3 to make sure you can get them all.

step-3-bulk-option.png

This is a precaution to ensure that if you use a duplicate matching filter that is too broad in Step 1, you do not accidentally merge many non-duplicate records together. If you are going to set this number at a high level, it is a good idea to run Preview Mode first to make sure your deduplication template is operating as you intend.

Are there any limits on the number of records that can be identified and merged with my paid subscription?

All plans include unlimited usage, unlimited users, and unlimited operations. See the pricing page for more details. During the free trial, there is a cap of 500 records updated, cleansed, or merged.

Additional Resources

Related Help Articles

Related Blog Posts