How it works
What Cuebased notices in a visit, how it turns those cues into moments, intent and a story, and what you get to work with afterwards.
The gap
Each visit was someone trying to do something. That is exactly what you need to know to improve the page.
Dashboards count. Every number, none of the reasons behind it.
Recordings take hours. Watching sessions one by one does not scale, and records more than you need.
Summaries stop at a paragraph. A description of one session is not a decision, and nothing checks the result.
/pricing · last 30 days
Synthetic example403 visits ended without one. What were they looking for?
What Cuebased notices
Recorded only after a visitor allows analytics. Never page text, input values or anything inside a private region.
Lingering
How long an annotated section stays in view, and how much of it is visible. In view is not the same as read.
section_exposure
Pausing
The pointer resting on a link, a button or an annotated action for a moment. Mouse and pen only; a missing hover on touch means nothing.
hover
Scrolling past
How far someone scrolls through a page, and in which direction.
scroll
Going back
Coming back to a page seen earlier in the same visit: by a link, the back button or a page the browser restores.
page_view · back_forward
Opening
Opening an FAQ answer or another disclosure, and closing it again.
toggle
Leaving a form
Moving through form fields, filled or empty, valid or not, and not sending the form. Never what was typed.
field
Dead ends
Activating a button or link when nothing on the page changes within two seconds. Form fields, mail links and new-tab clicks are never judged.
click · none_observed
Stepping away
Another tab, another app or a locked screen, and back again later. Hidden is not the same as gone.
visibility
Waiting
How quickly the page loads, settles and responds, measured with Core Web Vitals. Slow loading is flagged; response times are recorded.
web vitals
Asking
Submitting a form in the browser, and your server confirming what really happened.
form_submit · outcome
From cues to a story
A pause can mean interest, distraction or a slow connection, so no cue is read as a verdict. Cues become moments, moments answer plain questions, and the story says only what the evidence supports. Switch between the visits below.
Visit Qm81xT…r4sD · desktop · 1:24
Synthetic example
Small cues
What they add up to
A choice names the stage, a scale shows friction, and bars count the events behind each yes. “Yours” is the team’s own question. Any of them can be “not enough evidence”.
The story
Pricing-to-Security exploration before a confirmed demo request
Returned to Pricing after visiting Security.
The sequence is consistent with checking implementation or security requirements while evaluating the offer.
If this keeps happening
Put a Hosting and data residency summary on Pricing, then see whether the detour goes away.
The same short list every time, so visits can be compared.
Every yes points to its events. When the stream cannot tell, the answer says so.
No emotion scores, no personality types, no likelihood to buy.
Your questions
Next to the built-in questions, add your own: “Did they see the implementation timeline before contacting us?” Every visit answers it, with the evidence behind each yes.
Built from your site map. Pick pages, sections, buttons, forms and goals you have approved, in order or not, and what must not happen. No page text and no free-text rules.
Answered honestly. Yes, no, or not enough evidence when the signal a missing step needs was never observed. A browser submit never counts as a confirmed goal.
With your own takeaway. Write what the team should do when the answer is yes, or no. It appears on every visit it applies to, next to the evidence.
Counted across visits. See how often each answer is yes among the visits it could answer, and open those visits in one click.
YoursSaw the security details before asking for a demo?
Synthetic exampleYes in 44 of 809 visits
5%
Team note on every yesShow a hosting summary on Pricing, so the detour to Security is shorter.
YoursLooked at the plans but never clicked “Request a demo”?
Synthetic exampleYes in 150 of 809 visits
19%
Team note on every yesMake the next step from the plans easier to see.
Read against your content
Most analytics knows what people clicked. Cuebased also knows what the click was about, so stories can say what people were reading and suggestions can be about your content and its hierarchy.
Your site map, in your wordsToday
You approve page types, section names, key buttons and goals. Stories use them: “the Hosting and data residency section”, not “the third block”.
Your public pages, read oncePlanned
With your permission, Cuebased reads your public pages: headings, plan names, calls to action and their order. Only verified URLs you allow; the SDK still never reads what visitors see or type.
Suggestions about content and orderToday
Every opportunity comes with a proposed test about content or placement. With page reading, suggestions will point at the exact heading or block to move or rewrite.
Attention by section · one visit
Synthetic examplePricing/pricing
Pricing plans14 s
Pricing FAQ6 s
Security/security
Hosting and data residency18 s
Then came back to Pricing and requested a demo, which the server confirmed.
Suggested next step
Add a concise summary of, or link to, the relevant Security information on Pricing, then compare the return pattern and confirmed inquiries.
What you get
Real screens from the sample workspace every new account can explore. The visits in it are synthetic.
01Stories
The journey, what happened on each page and how it ended. Every sentence links to the events behind it.
cuebased.com/app/…/stories/…
Synthetic sample workspace
02Opportunities
Behavior that repeats across visits becomes an opportunity: how many visits it affects, out of how many, with a proposed next step.
cuebased.com/app/…
Synthetic sample workspace
03Improvements
Accept an opportunity and Cuebased drafts the brief, exportable as Markdown for your team or your coding agent. When the change ships, it compares before and after.
cuebased.com/app/…/improvements/…
Synthetic sample workspace
cuebased.com/app/…/improvements/…#review
Synthetic sample workspace
A reviewed change becomes part of the next period’s evidence.
Principles
Built for
Not for
Every story labels what was observed, what could explain it and what is not established.
Built from sanitized interaction metadata. There is no video of your visitors to store.
No page text, input values or query strings. Anything inside data-cb-private is never observed.
Paths, counts and outcomes are computed in ordinary code. A model may interpret, never invent.
Opportunities are ranked by visible components. You never get an invented revenue figure.
Every rate shows its count, denominator and period. Small samples say so.
Questions
Straight answers about what Cuebased does, what it does not do and what it takes to start.
No. It records no screens, video or page text. Stories are built from sanitized interaction metadata, and only after a visitor allows analytics.
It does not claim to know. It asks every visit a short list of plain questions and answers each yes, no or not enough evidence, with the events behind every yes. Explanations are hedged and come with alternatives.
Yes. Add up to 10 per site, built from your approved pages, sections, buttons, forms and goals, with an optional takeaway for your team. Every newly analyzed visit answers them yes, no or not enough evidence, and shows the events behind the answer. Questions never ask about feelings or intent, and takeaways that describe them are refused.
Today it uses the site map you approve: page types, section names, key buttons and goals. Reading your public pages automatically, their headings, plan names and calls to action, is planned and will only run on verified public URLs you allow. The SDK never reads the text your visitors see or type.
No. Visits stay anonymous: Cuebased never identifies visitors, never looks up companies from IP addresses and never joins visits across websites or devices. A planned feature will show the context of a visit next to the inquiry it led to, only for people who contacted you, and never used for outreach without a person approving it.
You need someone who can add a script to every page and connect your consent manager, which is designed to take under 15 minutes on a simple site. Confirming outcomes from your server takes a small backend change; without it, outcomes stay marked as unconfirmed.
No. It sits alongside the analytics you already use. Analytics counts; Cuebased explains visits and turns what repeats into improvements you can measure.
Cuebased is built for consent-first collection: nothing runs until your consent manager grants analytics, Global Privacy Control is respected by default and no page text or input values are collected. Processing is planned in the EU. You remain the controller for your website analytics.
Facts, counts and outcomes are always computed in ordinary code. During the pilot, stories come from tested templates and the questions are answered by deterministic rules. Language models are planned for deeper stories, only after privacy and contractual review, and may interpret facts but never invent them.
The free plan includes 1,000 analyzed visits and 50 deeper stories a month, with no card required. Paid plans start at €49 a month in the proposed pilot pricing.