Jul 11, 2026
How to Read a PostHog Funnel Without a Data Team
A funnel is the sequence of steps a user walks between arriving at your product and receiving value from it, with the percentage who survive each step. PostHog makes building one genuinely accessible to founders: no SQL, no data team, no analyst on retainer. What trips founders up is not building the funnel, it is reading it, because a funnel full of numbers invites exactly the wrong instinct: trying to fix everything at once.
At On the User we install PostHog at the start of every engagement, and the funnel read is the first hour of real work. This post is that first hour, written down: which funnel to build first, how to find the step that matters, and the two traps that make founders misread their own data.
Analytics
PostHog
Funnels
Which funnel should you build first?
One funnel from signup to activation, five to seven steps, on new users only. Everything else can wait.
The first funnel is always the new-user path: signup started, signup completed, first key setup step, first core action, activation event. Five to seven steps, no more. If you have not defined your activation event yet, do that first; it is the last step of this funnel and the reason it exists.
Two settings matter more than founders expect. First, restrict the funnel to new users, because mixing veterans into a first-run funnel flatters every number. Second, set a realistic conversion window: if your product’s value arrives in one session, a 24-hour window is honest; a 14-day window would hide the problem.
Resist the urge to build five funnels. One funnel, read properly, will produce more action than a dashboard wall.
How do you find the step that actually matters?
Look for the steepest percentage cliff between two adjacent steps, not the biggest raw number, and confirm what you see with session replays.
Founders naturally look at the step where the most users disappear in absolute terms, which is usually the first step because it has the most traffic. The better question is where the survival rate falls hardest: 70% to 30% between two steps is a cliff; 90% to 80% is a slope.
The cliff is your leak. Now comes the part most people skip: do not brainstorm reasons, watch the evidence. PostHog puts session replays next to the funnel, so filter replays to users who reached the cliff step and did not survive it. Watch five. Not fifty, five. You will see the same stumble repeat: the form that asks too much, the button nobody finds, the loading state that reads as broken, the paywall that arrives before the value.
This is the difference between analytics as decoration and analytics as diagnosis. The funnel tells you where; the replays tell you why.
What are the two traps that make founders misread funnels?
Averages that hide segments, and celebrating rate improvements that came from volume changes rather than fixes.
Trap one is the average. A 40% overall conversion may be 70% on desktop and 12% on mobile, and the average will happily conceal that. Before acting on any funnel read, break it down by platform and by acquisition source. Very often “our onboarding is broken” is actually “our onboarding is broken on mobile,” which is a different, smaller, more fixable project.
Trap two is mistaking traffic shifts for progress. If a paid campaign ends and your funnel conversion improves, you did not fix anything; lower-intent users simply stopped arriving. Judge fixes on cohorts: same source mix, before versus after the change. Judge weeks, not days.
Read this way, a funnel stops being a chart and becomes a work order: one cliff, one observed cause, one fix, one measured result.
The funnel read is step one of the method in our free guide to the four leaks that keep products under $10K MRR: Find the 4 leaks holding your app back.
Latest Updates
(GQ® — 02)
©2024
FAQ
01
What does a project look like?
02
How is the pricing structure?
03
What type of industries you work with?
04
What is the ROI?
05
Why should I choose OTU® over a freelancer or design agency?
06
How quickly can we get started?
Jul 11, 2026
How to Read a PostHog Funnel Without a Data Team
A funnel is the sequence of steps a user walks between arriving at your product and receiving value from it, with the percentage who survive each step. PostHog makes building one genuinely accessible to founders: no SQL, no data team, no analyst on retainer. What trips founders up is not building the funnel, it is reading it, because a funnel full of numbers invites exactly the wrong instinct: trying to fix everything at once.
At On the User we install PostHog at the start of every engagement, and the funnel read is the first hour of real work. This post is that first hour, written down: which funnel to build first, how to find the step that matters, and the two traps that make founders misread their own data.
Analytics
PostHog
Funnels
Which funnel should you build first?
One funnel from signup to activation, five to seven steps, on new users only. Everything else can wait.
The first funnel is always the new-user path: signup started, signup completed, first key setup step, first core action, activation event. Five to seven steps, no more. If you have not defined your activation event yet, do that first; it is the last step of this funnel and the reason it exists.
Two settings matter more than founders expect. First, restrict the funnel to new users, because mixing veterans into a first-run funnel flatters every number. Second, set a realistic conversion window: if your product’s value arrives in one session, a 24-hour window is honest; a 14-day window would hide the problem.
Resist the urge to build five funnels. One funnel, read properly, will produce more action than a dashboard wall.
How do you find the step that actually matters?
Look for the steepest percentage cliff between two adjacent steps, not the biggest raw number, and confirm what you see with session replays.
Founders naturally look at the step where the most users disappear in absolute terms, which is usually the first step because it has the most traffic. The better question is where the survival rate falls hardest: 70% to 30% between two steps is a cliff; 90% to 80% is a slope.
The cliff is your leak. Now comes the part most people skip: do not brainstorm reasons, watch the evidence. PostHog puts session replays next to the funnel, so filter replays to users who reached the cliff step and did not survive it. Watch five. Not fifty, five. You will see the same stumble repeat: the form that asks too much, the button nobody finds, the loading state that reads as broken, the paywall that arrives before the value.
This is the difference between analytics as decoration and analytics as diagnosis. The funnel tells you where; the replays tell you why.
What are the two traps that make founders misread funnels?
Averages that hide segments, and celebrating rate improvements that came from volume changes rather than fixes.
Trap one is the average. A 40% overall conversion may be 70% on desktop and 12% on mobile, and the average will happily conceal that. Before acting on any funnel read, break it down by platform and by acquisition source. Very often “our onboarding is broken” is actually “our onboarding is broken on mobile,” which is a different, smaller, more fixable project.
Trap two is mistaking traffic shifts for progress. If a paid campaign ends and your funnel conversion improves, you did not fix anything; lower-intent users simply stopped arriving. Judge fixes on cohorts: same source mix, before versus after the change. Judge weeks, not days.
Read this way, a funnel stops being a chart and becomes a work order: one cliff, one observed cause, one fix, one measured result.
The funnel read is step one of the method in our free guide to the four leaks that keep products under $10K MRR: Find the 4 leaks holding your app back.
Latest Updates
(GQ® — 02)
©2024
FAQ
01
What does a project look like?
02
How is the pricing structure?
03
What type of industries you work with?
04
What is the ROI?
05
Why should I choose OTU® over a freelancer or design agency?
06
How quickly can we get started?
Jul 11, 2026
How to Read a PostHog Funnel Without a Data Team
A funnel is the sequence of steps a user walks between arriving at your product and receiving value from it, with the percentage who survive each step. PostHog makes building one genuinely accessible to founders: no SQL, no data team, no analyst on retainer. What trips founders up is not building the funnel, it is reading it, because a funnel full of numbers invites exactly the wrong instinct: trying to fix everything at once.
At On the User we install PostHog at the start of every engagement, and the funnel read is the first hour of real work. This post is that first hour, written down: which funnel to build first, how to find the step that matters, and the two traps that make founders misread their own data.
Analytics
PostHog
Funnels
Which funnel should you build first?
One funnel from signup to activation, five to seven steps, on new users only. Everything else can wait.
The first funnel is always the new-user path: signup started, signup completed, first key setup step, first core action, activation event. Five to seven steps, no more. If you have not defined your activation event yet, do that first; it is the last step of this funnel and the reason it exists.
Two settings matter more than founders expect. First, restrict the funnel to new users, because mixing veterans into a first-run funnel flatters every number. Second, set a realistic conversion window: if your product’s value arrives in one session, a 24-hour window is honest; a 14-day window would hide the problem.
Resist the urge to build five funnels. One funnel, read properly, will produce more action than a dashboard wall.
How do you find the step that actually matters?
Look for the steepest percentage cliff between two adjacent steps, not the biggest raw number, and confirm what you see with session replays.
Founders naturally look at the step where the most users disappear in absolute terms, which is usually the first step because it has the most traffic. The better question is where the survival rate falls hardest: 70% to 30% between two steps is a cliff; 90% to 80% is a slope.
The cliff is your leak. Now comes the part most people skip: do not brainstorm reasons, watch the evidence. PostHog puts session replays next to the funnel, so filter replays to users who reached the cliff step and did not survive it. Watch five. Not fifty, five. You will see the same stumble repeat: the form that asks too much, the button nobody finds, the loading state that reads as broken, the paywall that arrives before the value.
This is the difference between analytics as decoration and analytics as diagnosis. The funnel tells you where; the replays tell you why.
What are the two traps that make founders misread funnels?
Averages that hide segments, and celebrating rate improvements that came from volume changes rather than fixes.
Trap one is the average. A 40% overall conversion may be 70% on desktop and 12% on mobile, and the average will happily conceal that. Before acting on any funnel read, break it down by platform and by acquisition source. Very often “our onboarding is broken” is actually “our onboarding is broken on mobile,” which is a different, smaller, more fixable project.
Trap two is mistaking traffic shifts for progress. If a paid campaign ends and your funnel conversion improves, you did not fix anything; lower-intent users simply stopped arriving. Judge fixes on cohorts: same source mix, before versus after the change. Judge weeks, not days.
Read this way, a funnel stops being a chart and becomes a work order: one cliff, one observed cause, one fix, one measured result.
The funnel read is step one of the method in our free guide to the four leaks that keep products under $10K MRR: Find the 4 leaks holding your app back.
Latest Updates
©2024
FAQ
What does a project look like?
How is the pricing structure?
What type of industries you work with?
What is the ROI?
Why should I choose OTU® over a freelancer or design agency?
How quickly can we get started?