What is conversion funnel analytics?

Conversion funnel analytics is the chart of an ordered path and the drop between steps. I use it to see where signup or onboarding stopped. It is not cohort retention, which asks whether last week's signups came back on day 7. The one-sentence definition of a conversion funnel stays on the glossary. This page is how I build the steps.

How is a funnel different from retention?

A funnel is a sequence. Did they finish step two after step one. Retention is a return. Did they come back next week. I needed the sequence first, because support was about people stuck in onboarding, not about a day-7 curve. Mixpanel-style products are built for the curve. EventDash is built for the sequence.

What should a funnel step be?

A commitment. signup_completed, workspace_created, teammate_invited. Not page_viewed, and not a nameless click. I name events object_action so a teammate can read the chart without a legend. If I will not act on the step, I leave it out. Two funnels I actually open beat five I built and forgot.

How often should I look at the funnel?

Once a week, on the same activation path. I note launches and pricing changes next to the drop, because the number shows what moved and the note is the only reason I remember why. I add a second funnel when a new workflow becomes the question. I do not add one because the chart looks empty.

← Back to Blog

Conversion Funnel Analytics for Product Teams

Jan 20, 2026•Updated Sep 30, 2026•Wlad

Conversion funnel analytics answers one question. Where did the user stop? I mean the product step, not the page they loaded. Cohort retention answers a different question: do they come back next week?

Small teams usually need the stop first. I did. Support was about people stuck after signup. A day-7 chart would have been a prettier way to avoid the step. The first funnel I built started with page_viewed. It told me the homepage loaded. I already knew that.

The one-line definition of a conversion funnel stays on the glossary. Install and HTML goals are in cookieless conversion funnels. Naming the events is event tracking basics. This post is only the split, so you do not buy a cohort suite to see which button died.

One short path

I start with one funnel and I keep it short:

signup_completed
first_project_created
invite_sent
report_shared

Every step is a commitment. A click with no object is how the chart becomes a junk drawer. If the step is not something a person finished, I do not put it in the funnel.

A retention funnel is a different job

| Question | What I use | | --- | --- | | Which onboarding step dies? | Conversion funnel analytics | | Do last week's signups return on day 7? | Cohort retention, which EventDash does not try to be |

If the search was "retention funnel," decide which job you have before you buy a platform. Mixpanel documents a funnel report inside a product that also does cohorts. EventDash is the sequence: product funnels and goals, not a retention suite. The comparison is EventDash vs Mixpanel.

Commitments, not page views

A weak funnel I have shipped, and regretted:

page_viewed
button_clicked
form_submitted

A stronger one:

signup_completed
workspace_created
first_event_tracked
teammate_invited

object_action keeps the names readable when someone else opens the dashboard. The naming habit is the event-tracking post. The steps themselves are configured in the funnels docs.

Two ways to record the step

HTML attributes. Mark the goal next to the control with data-ed-goal. Reference: HTML attributes.
SDK. For a step that is not one DOM click, such as a signup that finishes after an API call. Reference: JavaScript SDK.

Then I look at drop-off once a week. One activation funnel beats five unused ones. The traffic-versus-drop-off version of this argument is pageview analytics.

A note next to the number

The chart shows what changed. It does not say why. I add a note for a launch, a pricing change, an onboarding tweak. When I look back, the note is the only reason I remember which change lined up with the step. EventDash does not auto-attribute that note to a ranking move. It is a reminder for me.

Two funnels, then stop

Activation. Did they see the first value.
Expansion. Did they scale usage, an invite or a second project.

I add another funnel when a new workflow becomes the question I am actually asking. Free is 100k events/month. Signup if the missing piece is the sequence, not another retention board.

Sources

Mixpanel's funnel report, which sits next to cohort tools, is documented at Funnels. The EventDash definition of a conversion funnel stays on the glossary.

Key takeaways

Conversion funnel analytics answers where the user stopped. Cohort retention answers whether they come back.
Steps should be commitments, such as signup_completed, not page_viewed or button_clicked.
Mark them with HTML goals or the SDK, then review one activation funnel each week.
Pair the drop with a note on the launch or the pricing change, so you know why a step moved.

FAQ

What is conversion funnel analytics?: Conversion funnel analytics is the chart of an ordered path and the drop between steps. I use it to see where signup or onboarding stopped. It is not cohort retention, which asks whether last week's signups came back on day 7. The one-sentence definition of a conversion funnel stays on the glossary. This page is how I build the steps.
How is a funnel different from retention?: A funnel is a sequence. Did they finish step two after step one. Retention is a return. Did they come back next week. I needed the sequence first, because support was about people stuck in onboarding, not about a day-7 curve. Mixpanel-style products are built for the curve. EventDash is built for the sequence.
What should a funnel step be?: A commitment. signup_completed, workspace_created, teammate_invited. Not page_viewed, and not a nameless click. I name events object_action so a teammate can read the chart without a legend. If I will not act on the step, I leave it out. Two funnels I actually open beat five I built and forgot.
How often should I look at the funnel?: Once a week, on the same activation path. I note launches and pricing changes next to the drop, because the number shows what moved and the note is the only reason I remember why. I add a second funnel when a new workflow becomes the question. I do not add one because the chart looks empty.