Reading a PostHog funnel: from a drop to a cause

Start with the shape

Open the funnel and find the step with the largest relative drop. Then switch to the trend view: is the drop recent or has it always been there? A sudden change has a cause you can usually find. A permanent weak step needs research, not detective work.

Break it down

Split the step by device, browser, country, plan and acquisition channel. Many drops live in one segment: a layout broken on small phones, a payment method missing in one country, a campaign that brings the wrong audience.

If the drop is the same everywhere, the cause is probably in the product flow itself.

Line it up with releases

Put the release dates next to the trend. A drop that starts the day a version ships is the strongest clue you will get. Read the changes in that release that touch the step, even the ones that look harmless.

Read what users said

Session recordings show hesitation, but support chats and calls explain it. Search for messages from the same period that mention the step. When the release, the segment and the quotes all point the same way, you have the cause.

Close the loop

Fix the step, then watch the same funnel for the following days. Note the fix in your release history so the next person who sees the curve knows what happened.

Wirey reads PostHog funnels, GitHub releases and support conversations together, so this whole path takes minutes and ends with a pull request you approve.