01
Start at the first signal
Run Stick on your domain. Keep the first-party visitor history and carry journey links across your domains and CRM emails.
- DAY 1Visitor 7f3c, first visit
- DAY 9Back on Safari, 8 days laterSAME PROFILE
Count each customer once. Keep uncertain links in view.
Join visits, forms, bookings and CRM records on evidence. Give each team one profile and show the state of every CRM link.
Example outcome formula
Count each person with a Call booked record once. Open the booking records and inspect the CRM link state.
Drafted from your source definitions. Review before saving.
A dedicated team builds it with you. Start with one decision.
Visitor 7f3c
Email (masked)
Sarah C.
Sarah Chen
ONE PERSON
COUNTED ONCE
Each link with its state.
Required systems
Connect the required systems. Start with the records you have.
Your team brings one decision. Our dedicated team connects the sources and builds it with you.
- Website. visitor history and journey links
- Forms and bookings. contact details supplied by the person
- CRM. trusted emails and customer IDs
- Email platform. recorded journey links
Agree the connection route.
Stick captures website history. Booking and CRM records need trusted identifiers; CRM data joins through your warehouse as agreed in the build.
Know the limits.
An offline visit alone does not identify a person. A second confirmed CRM record is stored as a conflict; candidate links stay labelled.
Inspect the identity evidence. Each CRM link keeps its state.
- WebsiteVisitor 7f3cAnonymous
- Booking formEmail (masked)Step 1 saved
- Booking systemSarah C.Discovery call
- CRMSarah ChenCRM person
Sarah Chen1 PERSON · 4 RECORDS
LINKS, AND HOW WE KNOW
- Website visit to booking formSame browserSAME PROFILE
- Booking form to CRMExact email matchCONFIRMED
- Booking system to CRMExact email match, waiting for a second signalCANDIDATE
Back on Safari 8 days later. Same profile. First-party cookie.
CRM LINK STATES
- CONFIRMEDA unique exact match with a verified journey link
- CANDIDATEAn exact match waiting for a second signal
- CONFLICTThe evidence disagrees
- UNMATCHEDNo matching profile yet
DEMO. Sarah Chen is fictional. Each CRM link keeps its evidence and state.
Check the number. Open the records behind it.
- Source and time. Each count opens to the form, booking, event or CRM records behind it.
- Link evidence. Confirmed, candidate, conflict and unmatched CRM links keep their state in view.
- Your definition. Read the plain-English formula and preview the count before saving.
Book a Call
On the call, we map one outcome and the systems it needs. A dedicated team builds it with you.
Scoped and priced to the outcome, agreed before work begins. No seat licences.
HOW ONE PERSON STAYS ONE
Link the visit to the CRM record. One person, linked on evidence.
A dedicated team agrees the identifiers with you. Confirmed, candidate and conflict links keep their evidence.
SAME PROFILE · SAFARIDEMO - 02
Keep the anonymous history
When a form or booking identifies the person, keep their earlier anonymous visits on the same profile.
VISITOR 7F3C TO SARAH CHENDEMO - BEFOREVisitor 7f3c · 2 visits, pricing twice
- NAMED BYBooking form, step 1
- AFTERSarah Chen · the same 2 visits kept
- 03
Link the CRM on details you trust
Use trusted emails and customer IDs. Show each link's evidence and state. A second confirmed CRM record is stored as a conflict.
CRM LINKSDEMO - CRMExact email, verified journey linkCONFIRMED
- CRMExact match, waiting for a second signalCANDIDATE
- CRMA second confirmed recordCONFLICT
- 04
Give each team the same person
Share one sourced profile in the Glue Console. Send new leads to the CRM. Stream identity links to your warehouse where the build sets that up.
SARAH CHEN · ONE PROFILEDEMO - CONSOLEOne profile, one timeline
- CRMNew lead, with its sourceDELIVERED
- WAREHOUSEIdentity links, as they happen
BUILT ON
One customer, counted once. With the evidence for each link in view.
- A profile per person.Visits, forms, bookings, CRM steps and email on one timeline.
- CRM links with their state.Confirmed, candidate, conflict or unmatched, with the evidence behind each.
- A first-party footing.Stick on your own domain, with sourced visitor history and journey links.
- Identity links in your warehouse.Streamed as they happen where the build sets that up, for your own reporting.
Bring the report that counts people twice. We'll find where the records split.
On the call, we find which identifiers each system holds today. In the Outcome Build, a dedicated team links them on evidence and takes the first result live.
Decide what to build first.
- Which identifiers the business trusts.
- How many customers you really have.
- Which candidate links need a second signal first.
Keep the context you build.
The same model can feed your LLM, BI tool or destination. We agree each connection in the build.
Scoped and priced to the outcome, agreed before work begins. No seat licences.
On the call, we check the outcome, the sources and the fit.