A data merge change log records the rows updated or deleted during a deduplication operation.
It provides an audit trail after bulk processing and helps synchronize the cleaned result with a CRM or another application.
Why a change log matters
A merge preview shows proposed changes before processing. A change log records the changes that were applied.
Use it to answer questions such as:
- Which records were deleted?
- Which retained records were updated?
- What values did a record contain before the merge?
- What values did the retained record contain afterward?
Datablist change log fields
After a single-collection processing action changes records, Datablist can export a CSV containing:
DatablistId- The change type, such as updated or deleted
- Every previous property value
- Every destination property value
The download is available on paid plans. It records processed changes, not groups left in Needs review or skipped without modifying the collection.
🔍 Use both safeguards
Download the duplicate groups before processing when you need the proposed group membership. Download the change log afterward when you need the applied updates and deletions.
Automatic Remove and Merge operations are also recorded in collection History, where the complete operation can be undone.
Follow the complete deduplication workflow, or see change logs and History in the product reference.