cuebased
Join the waitlist
Synthetic example

Pricing-to-Security exploration before a confirmed demo request

This page is generated by the same engine the product uses, from synthetic events. Observations cite the exact events behind them — select a time chip to see it in the journey. Possible explanations are kept separate, come with alternatives, and never claim to know why someone acted.

Confirmed by serverDeep storyDesktopHigh evidence
ObservedPossible explanationNot established
Summary

Desktop visit: Pricing → Security → Pricing → Book a demo; the server confirmed the demo request.

Confirmed by your server

A server event confirmed the goal. This is the only way an outcome counts as confirmed.

Worth a look

  • Open the reply with hosting and data residency.

    Your note for “Saw the security details before asking for a demo?” when the answer is yes.

Observations

What the interaction stream shows

  1. Arrived on Pricing from google.com on a desktop device.

  2. The Pricing plans section was on screen for 14 s on Pricing.

  3. Expanded 1 FAQ item on Pricing.

  4. The Pricing FAQ section was on screen for 6 s on Pricing.

  5. Viewed 4 pages: Pricing → Security → Pricing → Book a demo.

  6. The Hosting and data residency section was on screen for 18 s on Security, without interaction.

  7. Scrolled to 81% of Security.

  8. Returned to Pricing after visiting Security.

  9. Activated “Request a demo”.

  10. Started filling in the demo request form.

  11. Submitted the demo request form from the browser.

  12. The server confirmed the demo request.

What the cues add up to

Yes-or-no questions answered from this visit’s evidence. Any answer can be “not enough evidence”; none of them says why someone acted.

Built-in questions

  • Comparing plans

    Yes

  • Checking security

    Yes

  • Looking for proof

    No

  • Comparing services

    No

  • Hit an obstacle

    No

  • Stage

    Acting

  • Friction

    None seen

Your questions

  • Saw the security details before asking for a demo?

    Yes
Possible explanations (not facts)

  • The time spent on pricing details is consistent with comparing plans or checking whether the price fits.

    Moderate support · based on 4 references

  • The sequence is consistent with checking implementation or security requirements while evaluating the offer.

    Moderate support · based on 3 references

Alternative explanations

  • The visitor may only have been checking whether prices are published at all.
  • The page may have stayed open while the visitor was doing something else.
  • The visitor may have been researching on behalf of someone else, such as a procurement or IT colleague.
  • An existing customer or partner may have been looking up reference information.
Not established
  • Role, budget, reasons and emotional state are not established by the interaction stream.
  • Section exposure approximates what was on screen; it does not show reading or attention.
  • Activity in other tabs, on other devices or before consent is not included.

Suggested next steps

Suggestions for a person to review. Cuebased never acts on your site or contacts anyone.

  • Review whether the pricing page makes deployment and security information easy to find.
  • For this confirmed inquiry, prepare material on the topics viewed; a person decides whether to use it in the reply.
How this story was made
feature version
features@1
episode version
episodes@1
category pack
leadgen@1
decision provider
rules@2
question set
leadgen.questions@2
narrative provider
template@1
selection route
requested (p=1)
revision
1

Validation: passed

  • schema
  • evidence resolves
  • numbers supported
  • no motives as facts
  • interpretations hedged
  • no invented quotes

Facts come from deterministic rules; interpretations come from bounded questions that may answer “insufficient evidence”. Every factual sentence must cite evidence from this visit, and numbers are checked against it.

Journey timeline

Select evidence to highlight

  1. Pricing

    0:00

    /pricing · load

    1. Viewed Pricing from google.com

      desktop · fine pointer · load

      0:00

    2. Pointer rested on “Choose Growth”

      1.6 s

      0:09

    3. Pricing plans on screen

      14 s · up to 90% visible

      0:14

    4. Expanded an item in Pricing FAQ

      0:15

    5. Pricing FAQ on screen

      6.4 s · up to 80% visible

      0:22

  2. Security

    0:23

    /security · push

    1. Viewed Security

      desktop · fine pointer · push

      0:23

    2. Hosting and data residency on screen

      18 s · up to 100% visible

      0:43

    3. Scrolled down to 81% of the page

      from 38% · deepest 81% · 2.1 s

      0:43

  3. Pricing

    0:45

    /pricing · push

    1. Viewed Pricing

      desktop · fine pointer · push

      0:45

    2. Activated “Request a demo”

      Followed by navigation

      0:51

  4. Book a demo

    0:52

    /demo · push

    1. Viewed Book a demo

      desktop · fine pointer · push

      0:52

    2. Focused a email field

      0:54

    3. Submitted the demo request form from the browser

      5 of 5 fields filled · an attempt until the server confirms

      1:23

    4. Browser recorded a demo request attempt

      Counts as confirmed only after your server says so

      1:23
  5. Server confirmed the demo request1:24

One story is a clue. Many are a pattern.

Cuebased groups repeated patterns into an opportunity inbox with honest denominators, then helps you test a change.

Join the waitlist