An example of how it comes together. One fictional customer, followed across six systems.
Six systems. One Sarah.
Meet Sarah Chen. Your website sees a visitor, your booking system a call, your CRM a deal. DataGlue joins them into one record, with the source on every step.
01CREATE + CONNECT
DataGlue follows each customer from first click to payment. Across every system they touch.
Ad click, website, form, booking, sales call, CRM, email and payment, glued into one record.
- Search adClick id read from the landing URL
- WebsitePricing, read twice
- Booking formSaved at step 1
- Booking systemDiscovery call booked
- CRMCall result, proposal, deal
- Email platformFollow-up email opened
Deal signedEvery step with its source
02RESOLVE
It knows when four records are one person. Matched on evidence, never guessed.
Each link is marked confirmed, candidate or conflict. Nothing merges silently.
- Visitor 7f3cWebsite · anonymous
- Email (masked)Booking form
- Sarah C.Booking system
- Sarah ChenCRM
Sarah Chen4 RECORDS · 1 CANDIDATE
- Website to booking form · same visitorCONFIRMED
- Booking form to CRM · exact email matchCONFIRMED
- Booking system to CRM · similar name, different emailCANDIDATE
03MODEL
It keeps the whole story in one living model. We call it the Glue.
Every step in order, with its system, its time and its source.
- Day 1 · 09:12Search adClicked a search ad. Click id read from the landing URL.
- Day 1 · 09:14WebsiteRead pricing.
- Day 9 · 20:41WebsiteRead pricing again.
- Day 9 · 20:46Booking formSaved at step 1. Left at step 2.
- Day 10 · 08:03Booking systemBooked a discovery call.
- Day 13 · 11:30CRMDiscovery call logged: qualified.
- Day 14 · 07:55Email platformOpened a follow-up email.
- Day 21 · 16:20CRMProposal sent.
- Day 23 · 10:05CRMDeal signed.
- Day 23 · 10:40CRMPayment received.
04ASK
It answers in plain words, with the evidence. In the Glue Console.
Every step of the answer shows what it read.
QUESTION
What did Sarah do before she booked?
- Find Sarah's profile (done)
- profiles · 1 match
- Read her visits, forms and bookings (done)
- search ad · click id
- website · pricing, read twice
- booking form · step 1 saved
- booking system · 1 booking
- Put them in order (done)
- day 1 to day 10
- Answer, with what it read (done)
- 4 sources
ANSWER
She clicked a search ad, read pricing twice in nine days and started the booking form, but left at step 2. She booked a discovery call the next morning.
- Search ad
- Website
- Booking form
- Booking system
05ACT
And it sends what it knows back out. To any destination, BI tool or LLM you choose.
Where connected in the build. Every send is logged, and any row can be retried.
- CRMNew lead, with first, last and converting touchDELIVERED
- Email and ad platformsCall booked, with click id and match keysDELIVERED
- Your warehouseEvidence streamFAILED · RETRYDELIVEREDAFTER 1 RETRY
Every send in one log. Retry a single row.
See Sarah’s full journey
- Day 1 · 09:12Search ad
Clicked a search ad. Click id read from the landing URL.
- Day 1 · 09:14Website
Read pricing.
- Day 9 · 20:41Website
Read pricing again.
- Day 9 · 20:46Booking form
Saved at step 1. Left at step 2.
- Day 10 · 08:03Booking system
Booked a discovery call.
- Day 13 · 11:30CRM
Discovery call logged: qualified.
- Day 14 · 07:55Email platform
Opened a follow-up email.
- Day 21 · 16:20CRM
Proposal sent.
- Day 23 · 10:05CRM
Deal signed.
- Day 23 · 10:40CRM
Payment received.
Check any number before you act on it.
Source on every fact. Each step keeps its system and its time.
Matched on evidence. Links are confirmed, candidate or conflict. Nothing merges silently.
Rows behind every count. Open any number to see the people in it.
“You read our pricing twice before you booked. Let’s start there.”