In this article
Dealing with duplicate records makes working with data harder. For example, duplicates take up extra rows in your contact lists, causing confusion between the data you need and redundant records. Duplicates would also make you spend extra transactions when sending out emails, not to mention spamming your customers.
Manually controlling duplicates is impossible, so Albato offers a tool to facilitate this. The tool does extra checks to ensure only unique data enters your automations.
This article walks you through the four scenarios of managing duplicates for your automations.
Scenario 1. Do not check for duplicates, always create new record
In this scenario, Albato does not perform additional checks and always sends a request to add a new record. Sometimes errors may occur if the required data uniqueness is not ensured.
Scenario 2. Do not create a record if a duplicate is found
Albato checks if sending data already exist in a receiving system. If such record is found (Duplicate), further processing of the current step will be stopped. And new record will not be created. The fields of the found record are available for the further steps of this automation.
Scenario 3. Update an existing record if a duplicate is found, otherwise create new record
In this scenario, Albato also searches for an existing record and updates its fields when found. If no duplicate is found, then new record is created.
For example, when submitting Facebook lead form, the system creates a customer record in CRM. It has standard fields: name, phone number and email. Next time the customer will communicate with you (e.g., a call after clicking the ad), additional data from ad system will be automatically loaded to his card.
You can delete the current value and enter your own data or select from the drop-down list. The field will be updated.
Scenario 4. Only update an existing record if a duplicate is found.
This is the last option for working with duplicates. It searches for duplicate, and stops if duplicates are not found. The scenario is similar to the previous one and performs the same functions except for creating a new record. Thus, it serves only to update records.
