Control
Nothing merges unless it clears the threshold you set.
- Tune it per object and per channel.
Prevent
Your rules, applied in bulk
API writes, data loads and integrations get the same rules as manual entry. Clear duplicates merge; the rest queue for review.
What an unchecked integration leaves behind
Before Plauti
- An integration writes records overnight and nobody checks which already existed.
- Contact details arrive unchecked.
WithPlauti
- Every record is scored against your data as it arrives. Matches collect in one queue.
- Email, phone and address are validated on the same insert.
How an automated write is handled
Enabled per object, per channel. One score decides what happens next.
The channels you protect
API inserts and updates, bulk loads, flows and your own code. Each one switched on per object.
A bulk load, cleaned as it lands
High-confidence duplicates are resolved during the import run itself. What is left collects in one review job, instead of spreading through the object unnoticed.
Above your threshold: merged
The incoming record merges into the existing one, following your merge rules. 95% is a common starting point, and any merge can be reversed.
Below it: queued
The record is still written. The match waits in a review job — one per object, which every later match is added to.
Does it work the way you need it to?
The four things admins check before letting anything merge on its own.
No rejected records
An incoming record can carry new consent or activity, so it is always written.
- A merge can be reversed, down to a single field.
Scale
A single job can cover millions of records.
- Offload the heavy runs off-platform.
Governance
It extends the rules you already run.
- Permissions and sharing honoured; every merge logged.
Frequently asked questions
Are records from an integration ever blocked?
No. The insert always succeeds and the calling system gets no error back, so nothing upstream breaks. What changes is what happens to the duplicate afterwards.
How is this different from prevention at the entry form?
Manual entry and web forms can warn a person or block the save. An automated write has nobody to warn, so the same scenarios end in a merge or a queue.
Can I switch it on without anything merging automatically?
Yes. Leave automatic merging off and detection still runs: every match goes to a queue and each merge stays a person's decision.
Where does the processing happen for a very large load?
In the platform, on a local machine, on your own server, or in the cloud. The rules are the same in each; only the engine changes. That is how a job covering millions of records stays clear of your platform limits.
See how it works
Talk with one of our experts to see how that works for your use case.