Who this is for
Teams with form events in PostHog who want to find the stage where visitors drop out, knowing the analysis has not yet run for a client.
Page Doctor is in build, starting with funnel leak analysis.
Page Doctor starts with funnel leak analysis, built as an operator tool on PostHog.
In buildStatus today · Agent: Diane
Part of the Website Optimiser module. Part of this works today and part does not. The scope below says which is which.
Practical purpose
Funnel leak analysis from visitor to captured lead, in build.
Frame a specific stage to investigate once your events are mapped. Page diagnosis and automatic proof of a fix are planned.
It counts visitors, form started, form submitted and lead captured, then ranks the biggest leak by the leads it could recover. It needs your events mapped to those names and has not yet run for a client. Page diagnosis and fix prescriptions are planned. One named leak gives the team a clear decision, where a long checklist can stall.
Service scope
Is this the right fit?
What to bring
Reliable visit, form-start, submission and lead-capture events with agreed definitions. Missing instrumentation has to be fixed before analysing the funnel.
What you receive
A funnel leak analysis and an investigation scope, in build. Page diagnosis, automatic release of a fix and proof of its effect are planned.
Illustrative example
A drop between form submission and lead capture may point to delivery plumbing rather than the page headline. Test that path before changing the creative.
How to evaluate the work
Validate each event with a controlled journey, then compare consistent periods. Exclude internal tests from business outcome reporting.
How it works
The workflow, step by step.
Your funnel is instrumented properly first
Page views alone cannot show you a leak. Form started versus form submitted is the pair that reveals abandonment, and most sites never record it.
The four stages are modelled
Visitors, form started, form submitted, lead captured. Simple on purpose, so the result leads to a decision.
The biggest leak is computed
One stage, named outright. Not a severity-sorted backlog.
A change is agreed, then measured by hand
Agree a baseline and review comparable periods after a supervised change. Automated before-and-after measurement is planned, and a difference alone does not establish causation.
Evidence and scope
Search context and workflow facts.
2,900US searches a month for conversion rate optimization
1 leakthe single stage losing the most people, named. Not a list of ninety
4 stagesvisitors, form started, form submitted, lead captured
Search volume: Google Keyword Planner, United States, pulled 31 Aug 2026. It is historical search demand, not a traffic forecast. Other figures describe the documented Ruh AI record, workflow scope or stated limitations. They are not promised results for your business. Read the Ruh AI evidence and measurement limits.
The system behind it
PostHog and the funnel analysis tool
The funnel analysis is a tested command-line tool that reads PostHog events. It has no dashboard yet and no client run is recorded. Page diagnosis, fix prescriptions and automatic before-and-after proof are planned.
- In build
- built for Ruh AI first
- approval controls depend on the workflow
Signals in
- Your data
- Your brand pack
- What worked last month
Diane · PostHog and the funnel analysis tool
Agree the workflow
- data and access
- approval and delivery
- checks and limitations
Scope notes
Good to know.
- Funnel leak analysis is built and tested. Page diagnosis and automatic proof of a fix are planned.
- It reads the events your site records, so measurement comes first if analytics are not set up yet.
- Channel attribution is a separate piece of work.
Why only one leak?
Because one named stage leads to a clear decision, where a long list of recommendations can stall.
What if I have no analytics installed?
Then instrumentation comes first, so the analysis has events to read.
Why is this in build?
The funnel analysis is built and tested, but it has not run for a client and needs your events mapped. Page diagnosis, fix prescriptions and automatic proof of a fix are planned.
Work in practice
Read the evidence. Then talk about your business.
Two stories with different evidence levels. Read each source and its limits.
All case studiesFirst-party measurement
Ruh AI
Organic leads, with the evidence attached.
Weekly organic leads rose from 6 in early July to 20 in the week of 24 August 2026. August paid spend was $0.
Discuss your goals- Weekly organic leads
- 6 to 20
- Evidence
- First-party
Published Ruh AI customer story
Rapid Innovation
A more connected marketing workflow.
Ruh AI reports 37% more leads for Rapid Innovation after introducing AI-supported research, publishing and lead qualification.
Discuss your goals- Reported leads
- +37%
- Source
- Ruh AI story
These studies explain the wider work behind Ciny. They do not establish results for every capability. Live, Available, In build and Planned labels still apply.
Explore Page Doctor. Ask what works today.
Part of this works today. We show you exactly which part before anything is agreed.