Platform / Match / Identity matching
One person. However they wrote it.
Phone numbers are normalised, emails cleaned, Meta lead IDs kept — and a person is only ever matched by those three. Never by name.
| Anchor | As written | Normalised |
|---|---|---|
| Phone | 07700 900123 · UK | +447700900123 |
| Jane.Miller@Mail.com | jane.miller@mail.com | |
| Meta lead ID | 9012…0123 | kept as is |
How it works
Step by step.
What you actually get
Identity matching, in detail.
Three anchors, no names
Two people can share a name; one person writes it three ways. Names are never used to match.
Phone numbers normalised
Spaces, brackets and leading zeros removed; your country fills in a missing code.
Repeat sign-ups recognised
Someone who fills two forms is one person with two leads.
Conflicts kept apart
When phone points to one person and email to another, the row waits for you.
Lead ID across sources
The same Meta lead in your CRM file stays one application.
Shown as proof
Every matched payment says how it was matched.
Works with
Connect what you already use.
Meta, your website and a CSV from any CRM today. Direct CRM and payment connections are next.
Why not match by name?
Names are not unique and are written differently everywhere. A wrong match puts money on the wrong campaign — so we don't.
What if a customer changed their phone?
Email or lead ID still match. If none match, the payment waits for review.
Is the phone number sent anywhere?
Only hashed, and only if you turn on sending results to Meta.
One person. However they wrote it
on your own data.
Book a 30-minute call — we set it up with you live.
Book demo