Deduplication
Matching against existing records rather than creating a new contact each time.
Connecting a form to a CRM is straightforward. Keeping the CRM usable afterwards is not — duplicates accumulate, attribution is lost, and half the records show no source. CRM integration should deliver every enquiry with the context that makes it actionable, without degrading the data already there.
An integration that creates a new contact for every submission destroys the CRM slowly.
Matching against existing records rather than creating a new contact each time.
Source, campaign and landing page carried through so marketing can be measured.
Queued and retried, so a CRM outage does not lose an enquiry.
To the fields your team actually uses, not to whatever matched by name.
A silent integration failure means lost leads nobody knows about.
More than name and email, and less than everything.
Discuss Your CRM →What they asked, mapped to fields sales will actually look at.
Where they came from, which campaign, which landing page.
Which pages preceded the enquiry, when that helps qualification.
Fields nobody uses make records harder to read, not more informative.
Connection, data quality and the attribution that makes reporting possible.
Attribution for paid campaigns is covered in conversion tracking.
Start with how sales uses the CRM, because that determines what is worth sending.
Which fields are used, which are ignored, and what sales needs.
How an existing contact is recognised.
Queued, retried and validated.
Source captured at entry and carried through to submission.
Test submissions checked in the CRM, with alerting for failures.
It is captured on arrival and needed at submission, and most of the loss happens in between.
A visitor arrives with campaign parameters in the URL. They browse for ten minutes, the parameters leave the address bar, and the form submits with no record of where they came from.
The fix is capturing those parameters on arrival, storing them for the session, and including them in the submission. It is simple and it is frequently missing.
The consequence is a CRM where a large share of records show no source, which makes it impossible to tell which marketing produced revenue.
The default integration behaviour is to create a record per submission. Someone who enquires twice becomes two contacts; someone who fills two different forms becomes two more.
Within a year the CRM holds several records for the same person with different histories, and nobody trusts the reporting because the counts are inflated.
Matching on email before creating, and updating where a match is found, prevents this. It has to be decided at integration time, because cleaning it up afterwards is manual work.







CRM integration connects your website to your CRM so enquiries arrive automatically with the attribution and context sales needs — including deduplication and reliable delivery.
Because the integration creates a record per submission rather than matching against existing ones. Adding matching rules prevents new duplicates; the existing ones need a separate cleanup.
Usually because campaign parameters were captured on arrival and never carried through to the form submission. They leave the URL as the visitor browses, and nothing stored them.
With a queued integration, the submission is stored and retried, so nothing is lost. With a direct submission, the enquiry may simply fail — which is why we queue by default.
Only where the website needs to reflect CRM state, such as a customer portal showing account status. One-way is simpler and sufficient for lead capture.
Still deciding if crm integration is right for you?
Talk to UsNothing dramatic happens on the day a CRM integration goes live. Enquiries arrive, sales works them, and everyone considers it a success.
What accumulates is invisible for months. A second record for a contact who enquired before. A record with no source because the campaign parameters were dropped. A field mapped somewhere nobody looks.
By the time someone tries to report on which marketing produced pipeline, the data cannot answer the question — and the cause was a set of decisions made in an afternoon, a year earlier.
Tell us which CRM you use and how enquiries reach it. We will look at duplication, attribution and delivery reliability.
