One HCP, one record, one consent history.
Match & Merge
Match & Merge is the OptInsight module that recognises when an incoming contact is a healthcare professional (HCP) you already know, and combines both into one record with one consent history.
The same HCP often arrives several times, from web forms, events, your call center or your CRM. Match & Merge checks every new contact and asks: is this someone we know?

Where contacts come from
Matching runs automatically for every contact that arrives through an integration:
- Webhook: web forms, portals and other connected systems
- SpotMe: event registrations
- Steam: your call center
Connected systems can send their own identifier along, such as the CRM ID of the HCP in an event platform. Match & Merge recognises it even when one system adds a prefix: NRG-00123 and 00123 count as the same.

Scoring you can explain
Every incoming contact is compared with your existing contacts using an ordered set of scoring rules. Each rule looks at one or more fields and carries a score from 0 to 100. Unique identifiers such as OneKey weigh most; combinations of name, organisation and postal code follow. A candidate gets the highest score of the rules it matches.
| Score | Matches when | What happens |
|---|---|---|
| 100 | Same OneKey, or same Match and Merge ID and last name | Merged automatically |
| 90 | Same Match and Merge ID | Review queue |
| 80 | Same first name, last name and organisation | Review queue |
| 70 | Same first name, last name and postal code | Review queue |
| 50 | Same last name and postal code | Review queue |
| 30 | Same last name or postal code | Review queue |
These are the standard rules. OptInsight sets them up with you during onboarding. A rule can apply to all your environments or only to some, for example a country with its own identifier.
An empty field never matches. A rule that needs a postal code does nothing for a contact without one, so missing data never creates a false match.

Smart normalisation
Before two values are compared, both are cleaned in the same way. By default Match & Merge ignores casing, accents and spaces, so Müller matches muller and Van Dijk matches vandijk.
Fields where every character counts are stricter. A phone number only ignores spaces, and an external CRM ID is compared exactly. Each field can be tuned for your organisation, for example to ignore legal suffixes such as B.V. or GmbH in organisation names.

Automatic where certain, human where it matters
Only rules on a unique identifier merge by themselves. When OneKey matches, the incoming contact is merged into the existing one straight away. Every other match waits for a person, because a merge is permanent.
Those contacts go to the review queue, where a data steward handles the strongest matches first. The Matching window shows the incoming contact above its candidates, sorted by score. Click a score to see how it was reached: the rule, the compared fields, the values on both sides and whether they matched. One click merges the right candidate.

While a contact waits for review, it is on hold. Its consent is stored, but the contact is left out of campaigns, call campaigns, exports and your CRM until it is verified. A possible duplicate never reaches your HCPs or your sales team.

What a merge combines
The incoming contact is merged into the existing contact you choose. That record keeps its own name and organisation and receives:
- all consent registrations, so the full consent history sits in one place
- the mail history
- the most recent contact details, such as email address and phone number
When you merge a contact and your environment is connected to Veeva CRM, its consent is sent to Veeva straight away.

A merge log you can show an auditor
Every merge, automatic or manual, is recorded in the merge log. Per merge you see when it happened, the method, the channel, the reason, the rule with its score and who performed it. Merge details shows both contacts and the value of every compared field at the moment of the merge.
That gives you a complete trail for your GDPR accountability. Filter the log by date, method and channel, and export the review queue with its scores whenever you need it.

Curious?
Schedule a meeting with us.
Tip: involve your colleagues from other departments within your company. In this way we can instantly answer questions and provide clarity from various points of view.
Or are you considering changing consent management provider? Ask about our transition package where we offer you an easy and seamless transition.
Frequently Asked Questions
about match & merge
What is Match & Merge?
Match & Merge is the OptInsight module that recognises duplicate HCP contacts and combines them into one record with one consent history. It scores every incoming contact against your existing contacts and merges automatically only when a unique identifier matches.
Which channels does Match & Merge check?
Every contact that arrives through the webhook (web forms, portals and connected systems), SpotMe (events) or the Steam call center. Contacts you create by hand or import from Excel are not matched.
Why are not all matches merged automatically?
A merge is permanent. Only a unique identifier such as OneKey is certain enough to merge without a check. Every other match goes to a data steward, who sees exactly why a candidate scored as it did.
What happens to a contact while it waits for review?
Its consent registrations are stored, but the contact is on hold. It is left out of campaigns, exports and your CRM until it is merged. You can include these consents in the consent export if you need the full figures.
Can I see why two contacts were matched?
Yes, click any score to see the rule that produced it and, per field, the values on both sides and whether they matched.
Does Match & Merge work with Veeva CRM?
Yes, when you merge a contact in an environment connected to Veeva CRM, its consent is sent to Veeva right after the merge.
Who sets up the scoring rules?
OptInsight sets up the rules with you during onboarding. We can adjust them later, per environment or per country.



