Anonymous decision progression interpretation

Signals

Optiview structures anonymous session behavior into runtime signals — progression, friction patterns, and stabilization output your stack can activate before identity exists.

Optiview does not claim to know who the visitor is. It helps teams understand where anonymous progress may be slowing.

This page is product orientation: what gets emitted and how it maps to the runtime model. For the full seven-moment guide, see Runtime model.

Runtime model — full guide →

Runtime model

Seven moments teams recognize during anonymous buying — structured as operational state, not funnel steps.

Arrival → compare → hesitate → validate → recover → identify

ArrivingAm I in the right place?
ExploringWhat possibilities exist here?
UnderstandingHow does this actually work?
NarrowingWhich option am I actually considering?
ValidatingCan I trust moving forward?
DecidingAm I ready to complete the action?
RecoveringCan I regain momentum?

Summary only — Full runtime model has the full stage-by-stage breakdown.

How signals map to the runtime model

Session progression

Still figuring out fit, pricing, and setup
Pricing, install, and integration pages suggest active evaluation
May be moving toward demo or signup — or stalled on the same pages

Friction signals

Hard to tell how Optiview differs from analytics or a CDP
Same pages revisited without narrowing — comparison_loops
Slowing before signup or demo — pricing_hesitation or implementation_concern

Downstream activation

Emit context for GTM / CMS rules
Clarify pricing or rollout in plain language
Delay interruption until stabilization crosses threshold

Optiview reads anonymous visits. Your stack — GTM, CMS, Shopify, React, Adobe Target, and your personalization tools — decides what to show.

Signals are not certainty

Signals are clues about what may be happening on this visit. They are not identity claims, predictions, certainty scores, or lead scoring.

Runtime signals are observational output from session structure — not identity, not predictions, and not lead scores. Stabilization and confidence thresholds determine when emission is actionable.

Examples on real visits

Comparison without deciding
What the visitor may be trying to do
Down to a few finalists — still reopening the same pages.
What may be making this decision harder
Differences may be hard to see; comparison_fatigue pattern.
Helpful guidance that could make continuing easier
Emit shortlist context; surface only meaningful deltas downstream.
Affordability uncertainty
What the visitor may be trying to do
Still figuring out price and fit before acting.
What may be making this decision harder
Monthly cost or plan ranges unclear; momentum slows.
Helpful guidance that could make continuing easier
Emit pricing_clarity signal; CMS or GTM activates range band.
Luxury retail — checking authenticity
What the visitor may be trying to do
The visitor may be comparing models seriously — still deciding if this brand feels legitimate and worth it.
What may be making this decision harder
Certification, service, and shipping details may still feel unclear; too many similar pieces can blur together.
Helpful guidance that could make continuing easier
Keep certification and service context visible, simplify movement details, preserve comparison — helpful guidance, not a harder sell.
Editorial landscape (awards coverage)
What the visitor may be trying to do
Making sense of a category — reading, not buying yet.
What may be making this decision harder
Many parallel storylines; thread unclear.
Helpful guidance that could make continuing easier
Preserve reading context; emit related_content for continuity.

Watch runtime on a live visit

Signal reference — wire IDs, payloads, and activation patterns.