Count customers once. Check every match.
One customer often looks like four strangers. Link their visits, bookings and CRM records on details you trust, and see why each link was made.
You don't need a data warehouse project first. We start with one question and the systems you already run.
- WEBSITESAME VISITORVisitor 7f3c
- BOOKING FORMEXACT EMAILs***@***.com
- BOOKING SYSTEMEXACT EMAILSarah C.
- CRMCONFIRMEDSarah ChenExact email, with a verified journey link
Records join on the same visitor or an exact email. Each CRM link keeps its state and the evidence that set it.
- CONFIRMED
- A unique exact match
- CANDIDATE
- Waiting for a second signal
- CONFLICT
- Kept apart, listed for review
- UNMATCHED
- No record matched yet
- 01 · SALES
The CRM shows a brand-new lead.
She'd been on the site for nine days.
- 02 · MARKETING
She came back on Safari eight days later.
The report counted a new visitor.
- 03 · OPERATIONS / AI
Two CRM records share one email.
Nobody knows which one the assistant read.
A wrong merge costs more than a missed one.
So records join only where they clearly match, and every link shows why.
Know when separate records belong to the same customer. And show how you know.
Our team agrees with you which emails and customer IDs to trust. DataGlue links records only where those details match.
Earlier visits stay attached when someone gives their name. A possible or conflicting CRM link stays in view until a second check settles it.
Count each customer with Call booked, once. Open the count to see their records and CRM match.
From anonymous visitor to known customer. Without losing the history in between.
- 01
Keep the visitor
Stick, served from your domain, sets a first-party cookie that outlasts Safari's 7-day cap. Links carry the same visitor across your domains and your CRM's emails. - 02
Attach the history
When a confirmed form or booking names the person, their earlier anonymous visits stay on the profile. - 03
Link the CRM on details you trust
Each CRM person is linked with a clear status, and the reason it was set. - 04
Keep the trail
When a link changes state, the old one is closed, not overwritten. A profile can't hold two confirmed CRM records. A second one is stored as a conflict.
Every CRM link carries its state. Confirmed, candidate, conflict or unmatched. No scores.
- CONFIRMEDA unique exact match, with a verified journey link.
- CANDIDATEAn exact match, waiting for a second signal.
- CONFLICTThe evidence disagrees. The records stay apart and are listed for review.
- UNMATCHEDWe looked. No record matched yet.
- Booking form to CRMexact email matchCONFIRMED
- Booking system to CRMexact email match, waiting for a second signalCANDIDATE
- Email (masked)already confirmed to a different CRM personCONFLICT
- Email (masked)no CRM record foundUNMATCHED
Bring the customer your systems count twice.
Our team connects it with you. Your tools stay where they are.
Bring one question. We check fit.
One person, from the first visit to the payment. Across the systems your teams already run.
History that survives the form
The visits before someone identifies stay with them after. Sales sees the nine days, not only the name.
Returns that aren't strangers
A first-party cookie and cross-domain links keep the same visitor across weeks and domains.
Matches your team can check
Every CRM link shows its status and why, before anyone acts on it.
Keep your context.
Use your joined records, online and offline, in any AI tool, report or system you choose. Visits, activity and record matches export on request.
Keep your systems.
Keep your existing customer database. We agree how each system connects before the build.
Check the integrations libraryBring the customer your systems count twice. We'll find where the records split.
Talk it through with our team. Then we agree the details you trust, link your systems on them and take the first result live.
- Which CRM records to merge, and which to leave apart.
- Who owns the customer after the handover.
- Which details the business trusts to match on.
- Which records count as one customer in the report.
You don't need the answer, only the question.
Trusted by