Who it's for
One customer ID, useful to everyone who works with customer data
Business teams get one view of each customer. Data teams get matching they can explain. Managers get reports that agree. DPOs get a clear picture of what's held, and help with erasure.
Business teams
Your customers turn up in your CRM, your billing system and your support desk, often spelt a little differently each time. Jo Bloggs is in the CRM. J. Bloggs is in billing. Joanne Blogs called support last week. Is that one customer or three? Today someone has to work it out by hand, every time it matters.
Samesake works it out for you. It looks past nicknames, typos and dates typed the wrong way round. When the evidence is strong, it links the records on its own.
One view of each customer
See the records linked to a customer across connected systems in one place, with how they were linked.
Fewer duplicates and mistakes
Spot duplicates before they cause mistakes, like two accounts for one customer or a loyal customer treated as new.
Reports that agree
Sales, finance and service count customers the same way, because their reports share one ID for each person.
Your CRM, billing and support systems carry on as they are. Samesake reads from them and never changes or deletes anything in them. Strong matches link on their own; your data team reviews uncertain matches.
- CRMJo Bloggsjo.bloggs@example.com
- BillingJ. Bloggsjo.bloggs@example.com · 07700 900123
- SupportJoanne Blogs07700 900123
Jo Bloggs
One person · 3 records
Data and ops teams
Samesake does the matching and gives your team a fast way to settle the doubtful cases. Every score shows its working, every decision is recorded, and the result flows straight into your BI tools.
Explainable scores
Each field (name, email, phone, address and date of birth) agrees or disagrees with a visible weight, and the total decides what happens. Strong matches link automatically. Doubtful ones go to review.
No model makes the final call on a doubtful pair. Someone on your team does, with the evidence in front of them.
A review queue built for speed
Y confirms and N rejects. Defer, undo and notes work without leaving the keyboard.
- The whole group is shown, not just the pair.
- Conflicts, weakened links and strengthened rejections come back for a second look.
- Every decision records who made it, when, and why.
Decisions that stick, and undo
A rejected pair is never linked automatically. It only comes back to your team if the records change and the evidence becomes strong. A confirmed link isn't silently broken when a record changes later; it's flagged for another look. Made a mistake? Undo it. The full history of who decided what stays.
Straight into Power BI and Excel
The identity map is a read-only OData feed that Power BI, Excel and Azure Data Factory read directly. It carries IDs only: a RecordId for each source record and the PersonId it belongs to.
- Paging and incremental refresh.
- Map updates and merge redirects for your reports to consume as identities change.
- Read-only feed keys, separate from the keys that send data in.
Building a data warehouse or a customer 360? Use the registry to link customer records across sources. Load the identity map through Azure Data Factory or a similar tool, and join on PersonId.
| Field | CRM | Billing | Weight |
|---|---|---|---|
| First nameNickname recognised | Jo | Joanne | +2.5 |
| SurnameDifferent surnames | Bloggs | Smith | −3.5 |
| EmailDifferent emails | jo.bloggs@ | jo.smith@ | −1.0 |
| MobileSame number | 07700 900123 | +44 7700 900123 | +5.0 |
| Date of birthSame date | 12/03/1984 | 1984-03-12 | +4.0 |
| PostcodeSame postcode | LS6 2AB | LS6 2AB | +1.0 |
| Score | +8.0 | ||
Different surnames and emails keep this pair in review, despite the matching date and mobile number.
Default matching settings: review from 6.0, automatic linking from 11.5.
Y confirm ·N reject
| RecordId | PersonId |
|---|---|
| 10442 | P-2071 |
| 10458 | P-2071 |
| 10931 | P-2071 |
Managers
Samesake gives every customer one ID across your systems, links most records without anyone needing to look, and keeps your team in charge of the rest.
Reports that agree
Use the identity map in Power BI and Excel to join customer records. Map updates and redirects let you keep those joins aligned as identities change.
Less time on duplicates
Strong matches link themselves. Your team reviews uncertain matches, with the evidence in front of them.
A clear record
Every decision is recorded: who made it, when, and why. Your DPO gets tools for erasure requests too.
How well it matches
- of same-customer matches linked automatically, with no one needing to look
- About 9 in 10
- of those automatic links correct
- 99.9%
Figures from testing on synthetic data: 41,000 records for 20,000 people. Calibration on real client data is coming.
Little effort to run
Your systems stay as they are. They send records through the API or as CSV files, usually from a simple flow that runs whenever a record changes. We'll get you started on a free setup call, and can help build connectors at a day rate. Keep those source updates flowing and work through the review queue as uncertain matches arise.
What it costs
Plans are priced by the number of customer records across your connected systems, with unlimited users on every plan. You pay for your customer records, not for seats.
Each plan covers a number of sources, meaning the systems that send records: up to 2 on Starter, up to 5 on Business, and unlimited on Enterprise.
Going over your record limit never stops the service. We'll let you know, agree an upgrade with you, and only then charge more.
DPOs and security
Samesake stores the details matching needs, shows its working and helps you track erasure across connected sources. See what it stores, and where its limits are today. See the GDPR support workflow.
What it stores, and what it doesn't
It stores
- A copy of only the fields matching uses: name, email, phone, address and date of birth.
- Normalised versions of those fields, used for matching.
- A permanent record ID for each source record, and the links between records.
- Decisions and an audit trail: who did what, and when.
- For people marked for erasure: keyed fingerprints (one-way hashes of email, phone, or name with date of birth), so a returning record can be spotted.
It doesn't store
- Any other customer data from your systems.
- Marketing data: there are no campaigns or segments.
- A "golden record": your systems keep owning their data.
When one of your systems deletes a record, Samesake blanks its copy of that record's personal details. The IDs, links and audit history stay.
The identity map feed for BI tools carries IDs only, never names or contact details, and BI tools read it with read-only keys.
Erasure support
- Mark a person as "erasure requested".
- See the linked records in connected sources and track their deletion. Search for any further records the registry has not linked.
- Download a checklist of IDs and statuses to support your own request log.
- Investigate an alert if incoming details match the keyed fingerprints retained for an erasure request, for example after a backup restore or a later import. Detection depends on the details available; an alert prompts your authorised team to assess the record and any action needed. Each client has its own fingerprint key.
- A Data Protection Officer role for this work.
Your team deletes data in its source systems and sends those changes to Samesake. Your own request log stays the record of the wider request.
Access and audit
- Roles: admin, member and Data Protection Officer.
- Each client's data in its own database.
- Single sign-on built on Microsoft Entra External ID, so Samesake doesn't keep passwords.
- A full audit trail of decisions and changes, including any changes made by our support staff.
Honest limits
- Erasure scoped to one company in a group of companies. Coming
- Any signed-in user in your organisation can search all your records, and searches aren't logged. Decisions and link changes are.
- The erasure checklist is open to all members, and viewing it isn't logged.
- Viewing by our support staff isn't recorded in your audit history; any change they make is.
- Hosting and processing arrangements are described in the data processing agreement. Contact us for the current details your assessment needs.
See it with your own customer data.
Every new customer gets a free setup call, and we check the first matches together.