GuideAnalyticsEvent TrackingFunnels

Building click-funnel events you can trust

All work

The short version

A funnel chart looks like a picture of your customers. It is really a picture of your tracking. Every bar is built from events your product sends when someone does something, and if those events are missing, doubled up, or fired at the wrong moment, the funnel will tell you a confident story that is not true.

This is a practical guide to how funnel events work, how to design them, and how to check them before you make a decision on them. It comes straight out of real work. In a recent onboarding test, the way the events were built changed the size of the headline result.

~7% vs ~1%of buyers were missing at least one step event, old onboarding versus new
+2.0 vs +1.5points of lift on the first, pooled browser read: the full six-step funnel versus the plain signup-to-purchase count

The old version was losing more of its real buyers to tracking gaps, so the detailed funnel made the new version look better than it was. Both numbers also added up weeks while the traffic split moved, and both used the browser's copy. Read week by week on server records, there was no clear difference at all.

How a funnel works

Under the hood, a funnel is a query, not a picture. You hand your analytics tool (Mixpanel, Amplitude, PostHog, and the rest all work this way) an ordered list of events. For each person, it finds the first event, then looks for the next one after it, then the next, inside a time limit you set. Everyone who fires step one is the top of the funnel. Each bar after that is the share of people who made it to the next step, in order.

That means a person only counts at a step if the event for that step exists, belongs to the right person, and happened in the right order. Real behaviour that never became an event does not exist as far as the funnel is concerned.

The settings that change the answer

How an ordered funnel counts four people

Four people go through the same four-step funnel. Here is what each one sent, and what the funnel reports.

  1. 1Signed up
  2. 2Profile completed
  3. 3Plan selected
  4. 4Purchased
1234What the funnel reports
A CustomerEvery event fired, in order.
B Lost at step 3They paid, but the plan event never fired.
C CustomerCounted once, though step 2 sent two events.
D Lost at step 3Left after their profile. A real drop-off.

Look at B and D. The funnel reports them identically: both lost at step 3. Only D actually left. B is a paying customer the chart has thrown away, and nothing on the chart tells you which is which.

What makes a good event

Every event is a small record of one thing one person did. Simplified, it looks like this:

{
  "event": "Plan Selected",
  "user_id": "u_8f3a21",
  "timestamp": "2026-10-14T18:22:05Z",
  "properties": {
    "plan": "monthly",
    "onboarding_version": "v6",
    "platform": "web"
  }
}

Four parts, and each one has a job:

Designing the events for a funnel

  1. Start with the decision. Write down the question the funnel has to answer, such as "does the new onboarding turn more signups into customers?" That fixes the first and last step, and those two matter most.
  2. Mark the step boundaries, not every click. One event at each point where a person has clearly moved forward. Five to eight steps is plenty for most flows.
  3. Send each event from the most reliable place. Money and account events (signups, purchases, refunds) should come from your server or your payment provider's webhook, where ad blockers and closed tabs cannot stop them. Interface events can come from the browser.
  4. Give every version shared milestones. A redesign changes the screens, so old and new versions will not have the same events. Keep a small set of milestones that mean exactly the same thing in both, so you can compare them on equal terms.
  5. Tag everything with the variant. If an event does not carry the version, you cannot break that step down by version later.
  6. Write a tracking plan. One table that lists each event, exactly when it fires, its properties, and where it is sent from. It becomes the contract between product, engineering, and whoever reads the numbers.
A simple tracking plan for a four-step funnel
EventFires whenKey propertiesSent from
Signed UpThe account is createdsignup method, onboarding versionServer
Profile CompletedThe profile saves successfullyonboarding versionServer
Plan SelectedThe plan choice is savedplan, onboarding versionBrowser
Purchase CompletedThe payment succeedsplan, currency, onboarding versionPayment webhook

Why it matters: six ways a funnel can mislead you

How to check a funnel before you trust it

The takeaway

Funnel analysis is only as good as the events underneath it. A few minutes spent naming an event properly, firing it at the right moment, and tagging it with the version saves weeks of arguing about whether a result is real. When the numbers matter, check the plumbing first.

Work with us

Not sure your funnel is telling the truth?

I audit tracking plans, rebuild event schemas, and set up funnels and experiments that hold up to scrutiny, so the next decision you make is based on what customers actually did.