The story is in pieces. The Glue keeps it whole.
One living model across your digital and physical customer journeys. People, steps and results, in order, each with its source. Your team works from the same record. Ask in plain words in the Glue Console and get the answer with its evidence.
Bring one decision. We'll find where its data lives today.
- 01THE GLUEPeople, steps, systems and results
- 02YOUR SYSTEMSCRM, email platform, bookings, warehouse
- 03SIGNALSWeb, app and offline signals
- ONE RECORD
- Per person, across systems
- IN ORDER
- Every step with its time
- SOURCED
- Each step names its system
- OBSERVED
- Estimates labelled apart
- 01 · SALES
The CRM has her name. It doesn't have the nine days before it.
So the first call starts from zero.
- 02 · OPERATIONS
Four exports, one spreadsheet, every Monday.
Out of date by the time it's shared.
- 03 · AI / TRANSFORMATION
We pointed the assistant at the CRM. It answered from one system.
Without the visits, the bookings or the emails.
You don't need more data. You need the data you have, glued.
A warehouse stores facts. A connector moves them. The Glue keeps what they mean: whose they are, what happened in what order, and where each one came from.
- WEBSITE
- FORMS
- BOOKINGS
- CRM
- THE GLUE
- CRM
- EMAIL PLATFORM
- YOUR WAREHOUSE
- AD PLATFORMS
- PEOPLEMatched on evidence. Each CRM link carries its state.
- STEPSIn order, each with its time.
- SYSTEMSWhere each step happened, kept as its source.
- RESULTSDeals and payments, counted from the CRM, opening to rows.
We call it the Glue. It holds people, the steps they took, the systems those steps happened in and the results that followed. What was observed stays apart from what was estimated. Web signals come from Stick. App installs, store visits, drive-through orders and car park visits come from your source systems through an API, warehouse or scoped integration. Trusted identifiers determine which steps can be linked. The next decision builds on the same model.
Ten steps. Six systems. One record. From the first ad click to the payment her CRM recorded.
Each value on the record names the step and the system it came from.
- first_touchSearch ad, click id
- pages_readPricing, twice
- emails***@***.com
- bookingDiscovery call, Day 10
- crm_linkCONFIRMED
- call_resultQualified
- email_engagementOpened the ROI email
- lifecycleDeal signed
- paymentPayment received
- Day 1 · 09:12Search adClicked a search ad. Click id read from the landing page URL.
- Day 1 · 09:14WebsiteRead pricing.
- Day 9 · 20:41WebsiteRead pricing again.
- Day 9 · 20:46Booking formSaved at step 1. Left at step 2.
The booking form saved her details at step 1, before she left.
- Day 10 · 08:03CalendlyBooked a discovery call.
- Day 13 · 11:30CRMDiscovery call logged: qualified.
Call results, as your CRM records them.
- Day 14 · 07:55Customer.ioOpened the ROI email.
- Day 21 · 16:20CRMProposal sent.
- Day 23 · 10:05CRMDeal signed.
- Day 23 · 10:40CRMPayment received.
Payments, as your CRM or warehouse records them.
Sarah is a demo of a sales journey. App installs, store visits, drive-through orders and car park visits can join through your source systems, API or warehouse as part of the build. Links require trusted identifiers; an offline visit alone does not identify a person.
People, steps and results. Each with its time, its system and its source.
- 01
People, matched on evidence
Records join on details you already trust: emails, accounts, customer ids. No CRM link is made silently. Each one carries its state: confirmed, candidate, conflict or unmatched.
IDENTITY · SARAH CHENDEMO- Website to booking formJOINED
- Booking form to CRMCONFIRMED
- Calendly to CRMCANDIDATE
- 02
The CRM lifecycle, in order
Pipeline stages, call results, bookings, reschedules, cancellations, deals, payments, refunds and pauses, as your CRM records them. They arrive through your warehouse and land on the person's timeline.
CRM LIFECYCLEDEMO- Pipeline entered
- Discovery call: qualified
- Proposal sent
- Deal signed
- Payment received
- 03
Email and bookings on the same line
Customer.io sends, opens, clicks and bounces. Calendly bookings, reschedules, cancellations and no-shows. Beside the visits, not in another tab.
TIMELINEDEMO- Customer.io · Opened the ROI email
- Calendly · Booked a discovery call
- Website · Read pricing again
- 04
Facts added, with their source
Company, email domain, location and device facts are added on their own. Each one says where it came from and how it was found.
ENRICHMENTDEMO- Company · from the email domainLOOKUP
- Location · from the sessionDETERMINISTIC
- Device · from the browserDETERMINISTIC
- 05
Results defined over all of it
Deal signed. Payment received. Booked, then signed within 30 days. Counted from the CRM, forms, bookings and visits, and every count opens to its rows in the Glue Console.
DEAL SIGNEDDEMODiscovery call booked, then Deal signed, within 30 days12 PEOPLE · SEE THE ROWS - 06
A data dictionary your team writes
What each field means, with sample values and the notes your team adds.
DATA DICTIONARYDEMOdiscovery_outcomeCall result from CRMSample: qualified
Natively where we can. Through your warehouse or our API where we can't.
Stick captures web signals. Booking and email systems can contribute records. CRM history joins through your warehouse or API; lead delivery is mapped in the build. Postgres, signed webhooks and the REST API provide further routes.
App installs, store visits, drive-through orders, car park visits, support records and offline sales join from your existing systems through the API, warehouse or a scoped integration. Source availability, consent and match keys determine what can be linked.
Integrations we run today. Vendor names belong to their owners and imply no endorsement.
Your evidence stays yours. Cloud storage, your Postgres or a self-hosted data service. We agree the setup and coverage in the build.
- DataGlue Cloud
- Managed storage is the default. Account access, workspace settings and orchestration stay in DataGlue Cloud whichever data option you choose.
- Your Postgres
- Connect your own Postgres for supported sessions, events and identity links. Replay files remain in DataGlue Cloud in this mode. We map the reads, writes and warehouse streams covered by your setup.
- Self-hosted data
- Run a dedicated data service for supported journey tables and replay files. After registration, health checks and a verified data move, we can enable it for replay capture, playback and exports. Other application data and workflows keep their existing stores.
- Portable evidence
- Export sessions, events and identity links on request. Counts are checked first, then the files leave with a manifest and checksums behind short-lived signed links.
If you leave, the evidence in your warehouse stays there.
- SessionsCOUNTED
- EventsCOUNTED
- Identity linksCOUNTED
NDJSON · MANIFEST · CHECKSUMS · SIGNED LINK
The export covers sessions, events and identity links.
Stop rebuilding the story. Start the next decision from the same record.
- 01
Stop rebuilding the answer
The Monday spreadsheet becomes a record that stays current, with the source on every step.
- 02
One record for every team
Sales, marketing, operations and finance read the same steps, in the same order.
- 03
History that outlasts a tool
The model sits on top of your systems. When a tool changes, its history stays, and the new one joins through the build.
Bring the decision your systems disagree on. We'll glue only what it needs.
Talk it through with our team. In the Outcome Build, a dedicated team glues the sources behind that decision into the Glue, then extends the same model to the next one.
- Which customers to prioritise this quarter.
- Where the handover from marketing to sales breaks.
- Which result counts as a won customer.
- Which number the leadership meeting uses.
You don't need the answer, only the question.
Trusted by
