This feature is available in the Professional Plan.
This article explains in more detail how Smart Source Control exactly works, when to use it and when it is not suited.
Once Smart Source Control is enabled for an integration, DataBridge will keep a one-way hashed version of the entire source record that is processed. A one-way hashed version of a record is a unique value that can be compared with a one-way hashed version of another record to see if a record with the same values was already processed before. If that check tells DataBridge that the same record is processed already in a previous job, DataBridge will not process the record any longer. It will continue with the next record from the source.
Besides the hashed value of the source record, DataBridge also stores the unique ID’s of the destination that matched the source records’ data and deduplication settings.
A simple example
Let’s look at an example.

We have a source file with some records of company data. Each of the records have a unique number that we will use to deduplicate on. The destination platform is SuperOffice.
To process the first line, DataBridge will search for an identical hash in the Smart Source Control history, but it will not find it since this is the first job for this integration.
DataBridge will look for a company with number 101 in SuperOffice. Once it finds this company in SuperOffice, it will update the details. If it can’t find the company in SuperOffice it will create it. In both cases, DataBridge will know the unique ID for this particular company in SuperOffice.
This unique company ID is also stored with the hashed source record.

It will do the same for the other 2 records.
When the same file is processed the next day, without any changes to the first record, DataBridge will hash the values from the new source record and compare the generated hash with the history.
It will find the same hash and decide that further processing of the source record can be cancelled. On to the next records!
Then, the next day, another new file is being handed over to DataBridge. Now let’s assume that the first record with number 101 is changed.
DataBridge will look for the hashed value of the new source record in the history. It will not find it since the record has at least one changed value.
The record is processed and the company is updated in SuperOffice. DataBridge will receive the unique ID that this particular company has in SuperOffice and look for that ID in the Smart Source Control history.
It finds that value stored with the hashed value from the first source record.
DataBridge will now update the hash for this history record.
Source records with more than one entity
In cases where each source record holds information about more than one entity in the destination, storing the hash is the same. However, all involved unique ID’s are stored too. This is done to distinguish the difference between each combination and to be able to update the corresponding hash.
Shall we look at an example again?

In this example we have a source file with 3 records. Each record has company details and contact details. The company details are the same for every record, only the contact details are different. This example is a typical example to use in a DataBridge import scenario.
To process the first line, DataBridge will search for an identical hash in the Smart Source Control history, but it will not find it since this is the first job for this integration.
DataBridge will look for a company with number 101 in SuperOffice. Once it finds this company in SuperOffice, it will update the details. If it can’t find the company in SuperOffice it will create it. In both cases, DataBridge will know the unique ID for this particular company in SuperOffice.
Then DataBridge will look for a contact with the given first and last name that is linked to the given company. If it can’t find it, it will create the contact. Otherwise it will update it. Also here, SuperOffice will return the unique ID for the contact.
This unique company ID and contact ID are both stored with the hashed source record.

The same logic is repeated for all 3 records in our example file. This results in a history as shown in the image. The first column shows both the unique company ID and the contact ID from SuperOffice.
When the next day the same file -without any updates- is processed again, DataBridge will find the hashed value for each new source record and decide not to further process them.
Once an update in one of the records occurs, DataBridge will not find the same hashed value in the history and will further process the source record. That results in an update to the company and the contact in SuperOffice. Both unique ID’s will be handed over to DataBridge and the hash that matches the record with both the company and the contact ID will be updated with the hash from the latest source record. It will not touch the history of any of the other records that have the same company ID stored.
This example has two entities in the destination in one record: company and contact. More complex scenario’s where there are up to 6 entities in one record are also possible (and in some cases even more). An example when importing to SuperOffice is import of quotes and products. In a typical source file we then find details on company, contact, sale, quote, quote alternative and quote line (product). When processing such a record, the Smart Source Control history will keep unique ID’s from all the mentioned entities.
Not suited for Smart Source Control
Not all source records are usable for Smart Source Control. Now that we know exactly how Smart Source Control works, let’s look at an example of a file that has company details including interests that we want to import into SuperOffice. Every record has the same company details but every record also has a unique interest value. This scenario is not suited to use Smart Source Control.

To process the first line, DataBridge will search for an identical hash in the Smart Source Control history, but it will not find it since this is the first job for this integration.
DataBridge will look for a company with number 101 in SuperOffice. Once it finds this company in SuperOffice, it will update the details. If it can’t find the company in SuperOffice it will create it. In both cases, DataBridge will know the unique ID for this particular company in SuperOffice.
This unique company ID is also stored with the hashed source record.
Then it processes the second record with interest Webinars. The hash for this record cannot be found in the history and the record is processed. The company already exists in SuperOffice and only the interest Webinars is added.
SuperOffice returns the unique company ID and DataBridge will look for that in the history. It will find it, from the first source record that has just been processed, and update the hash.
The same for the third record with interest Charity.

The result is only 1 history record for those 3 records in the source file.
Once the file is again processed by DataBridge the next day, without any updates to the data, all 3 records will be processed as new or updated records since there is no corresponding hash to be found in the history.
In this example where we import interests, a better solution would be to have another way of having the details on the interest in the source file.
Automatic clean up
When a history record has not been updated for 365 days, it will be automatically deleted from the history.