Start a Proof Sweep

Sample Path Review Example data

One Path. Three buyer contexts. The evidence behind the difference.

Path Health Inconclusive

EU · Mobile

The expected confirmation email did not arrive within 24h.

  1. Entry and CTA
  2. Form
  3. Submit
  4. Confirmation email Not observed in 24h

Basis: your declared expectation. Both desktop contexts received it this cycle. See the finding ↓

Site
orbit-analytics.example
Expected after submit
Confirmation email within 24 hours
Latest cycle
Jun 16, 2026

Example company and data. Real reviews come from live runs on your Paths.

What this Path is checked for.

Checks used where the Path supports them.

  1. Entry & handoff

    • Buyer context applied
    • CTA handoff
    • Wait until usable
    • Popup over the button
    • Extra step before the form
    • Language continuity

  2. Form

    • Reachability
    • Progression
    • Validation
    • Required consent

  3. Submit

    • Submit state
    • On-page confirmation

  4. Scheduler Not on this Path

    • Reachability
    • Usable slots
    • Timezone and working hours
    • Controls the buyer can reach

  5. After submit

    • Confirmation email
    • Invite or ICS
    • Follow-up or nurture
    • Email rendering

  6. Change over time

    • Run history
    • Last trustworthy proof
    • Suspected affected window
    • Rerun after a fix

The same Path, checked three ways.

One cycle, Jun 16. Each context ran separately and kept its own evidence.

USDesktop EUDesktop EUMobile
Context applied on the runAppliedAppliedApplied
Entry and CTAReachedReachedReached
FormReachedReachedReached
SubmitReachedReachedReached
On-page confirmationObservedObservedObserved
Confirmation emailExpected within 24hObservedObservedNot observed
Run3c81d0a49b27e615f2e632c9 ↓

A difference between contexts is shown as a difference. It becomes a finding when it breaks an expectation you declared, as it does here.

One buyer context changed after submit.

EU · Mobile · run f2e632c9

The expected confirmation email did not arrive

Observed
No buyer-visible response was observed in covered channels within the proof window.
Basis
Your declared expectation: a confirmation email within 24 hours.
Compared with
This context on Jun 9, when it arrived. Both desktop contexts received it this cycle.
Path Health
Inconclusive A missing email is reported as a finding, not as a proven break.
Likely team Inference
Whoever owns follow-up for mobile EU requests, often Marketing Ops.
Next check
Fix it, then rerun this context with the same settings.

Confirmation email, Jun 16Expected within 24h

  • US · DesktopObserved
  • EU · DesktopObserved
  • EU · MobileNot observed
E05Inbox watchNo acknowledgement or follow-up

When this context last had trustworthy proof.

Confirmation email for EU on mobile, run by run.

  1. May 26Observed
  2. Jun 2Observed
  3. Jun 9Observed
  4. Jun 16Not observed
  5. NextRerun after the fix

Shaded: the suspected affected window. Dated from buyer-side runs only.

Last trustworthy proof
Jun 9
Suspected affected window
Between Jun 9 and Jun 16
First observed issue
Jun 16
After the fix
Rerun this context

Open the run behind the finding.

The Run Report for EU on mobile, Jun 16. Every capture and where the evidence stops.

Path HealthDemo request Path /demoRun Report f2e632c9

The form went through. No confirmation email reached the buyer within 24 hours.

Inconclusive
  1. Run started Jun 16, 04:53 PM UTC
  2. Inbox window open for 24h
  3. Report settled Jun 17

Evidence that arrives later stays with this run. It does not rewrite the current Path Health.

Context applied on this run

Network region
EU network, Frankfurt, verified
Device
Mobile
Buyer email
Corporate buyer email
Expected after submit
Confirmation email within 24h
Watched
Browser and buyer inbox, 24h
Submitted
Yes, approved for this Path

How far the buyer got

  1. Public pageReached
  2. CTA clickReached
  3. FormReached
  4. SubmitOn-page thank-you observed
  5. Email or inviteNot observed in 24h
  6. Sales follow-upNot observed in 24h

Evidence gallery

All captured from the buyer's side.

E01Run replayThe whole run, buyer side
E02Landing pageBefore any click
E03Demo formAfter the CTA click
E04Form submissionThank-you page, 04:54 PM UTC
E05Inbox watchNo acknowledgement or follow-up
E06Calendar checkNo invite observed

What reached the buyer after submit

Observed

  • Browser thank-you page

Not observed in covered channels

  • Acknowledgement email
  • Verification email
  • Demo or sales follow-up
  • Invite or ICS
  • Nurture email

Not covered on this run

  • Calls, SMS, WhatsApp. Only when you switch them on.

Where this proof stops. Everything above is what the buyer could see. It says nothing about CRM state, lead routing, ownership, or attribution. Confirming that our test record reached your system is separate, scoped work. How a report settles after the run →

See what changes across your own Path.

Start with a Proof Sweep: $750 for one Path in up to 3 buyer contexts, with one rerun to verify a fix. Credited toward annual coverage within 30 days.

No payment in this form. We confirm fit and scope first, for free.