DataGlue
IDENTITY RESOLUTION

Count customers once. Check every match.

Link visits, bookings and CRM records using details you trust. Check each link’s evidence and state: confirmed, candidate, conflict or unmatched.

A dedicated team connects it with you. Keep your tools. Start with one decision.

FIG. 01 · ONE CUSTOMER
IDENTITY · FICTIONAL CUSTOMERDEMO
  1. WEBSITESAME VISITORVisitor 7f3c
  2. BOOKING FORMEXACT EMAILs***@***.com
  3. BOOKING SYSTEMEXACT EMAILSarah C.
  4. CRMCONFIRMEDSarah ChenExact email, with a verified journey link
ONE PERSONSarah Chen

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
WHERE IDENTITY SPLITS
  1. 01 · SALES
    The CRM shows a brand-new lead.

    She'd been on the site for nine days.

  2. 02 · MARKETING
    She came back on Safari eight days later.

    The report counted a new visitor.

  3. 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 no link is guessed, and each one shows its state.

IN PLAIN ENGLISH

Know when separate records belong to the same customer. And show how you know.

Your dedicated team agrees the emails and customer IDs you trust. DataGlue links records on that evidence.

Earlier anonymous visits stay attached when someone identifies. A candidate or conflicting CRM link stays visible until evidence resolves it.

Count the customers who booked or paid with a plain-English formula. Open the count to its records and check each link state.

HOW THE MATCH IS MADE

From anonymous visitor to known customer. Without losing the history in between.

  1. 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.
  2. 02

    Attach the history

    When a confirmed form or booking names the person, their earlier anonymous visits stay on the profile.
  3. 03

    Link the CRM on evidence

    Each CRM person is linked with an explicit state, and the evidence that set it.
  4. 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.
LINK STATES

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.
IDENTITY · LINKSDEMO
  • 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
Back on Safari 8 days later. Same profile. First-party cookie.Every CRM link shows its state.

Bring the customer your systems count twice.

A dedicated team connects it with you. Keep your tools. Start with one decision.

Book a Call

Bring one decision. We check fit.

WHAT CHANGES

One person, from the first visit to the payment. Across the systems your teams already run.

  1. History that survives the form

    The visits before someone identifies stay with them after. Sales sees the nine days, not only the name.

  2. Returns that aren't strangers

    A first-party cookie and cross-domain links keep the same visitor across weeks and domains.

  3. Matches your team can check

    Every CRM link shows its state and the evidence behind it, before anyone acts on it.

Keep your context.

Your living model carries online and offline context to any LLM, BI tool or destination through agreed routes. Export sessions, events and identity links on request.

Keep your systems.

No migration into a new customer database. Your dedicated team confirms the native, API, warehouse or scoped route before connecting it.

Check the integrations library
START WITH THE RECORDS THAT DON'T MATCH

Bring the customer your systems count twice. We'll find where the records split.

In the White-glove Outcome Build, our team agrees the identifiers you trust, links your systems on them and takes the first result live.

DECISIONS TEAMS BRING
  • Which CRM records to merge, and which to leave apart.
  • Who owns the customer after the handover.
  • Which identifiers the business trusts.
  • Which records count as one customer in the report.

A dedicated team connects it with you. Keep your tools. Start with one decision.

Trusted by

  • Ticketek
  • me&u
  • InvestorKit
  • Team Global Express