Funnel stages that match the product

Someone pastes a “standard SaaS funnel” into the roadmap deck: Awareness → Interest → Consideration → Purchase. Marketing nods. Product stares at an empty “Interest” event in the warehouse. Engineering asks which of seventeen page_view flavors counts as Awareness. Two weeks later every team has a different conversion rate for the same week, all labeled “funnel.”

Funnels are useful when stages match how value is actually created in your product. They become slide fiction when stages are borrowed from a textbook or a different business model. Customer analytics starts here: name the journey with events you can instrument, windows you can defend, and owners who care when a step breaks.

This is Part 1 of Customer analytics basics. Later parts cover conversion math and cohorts. Here we build product-shaped stages (Visit → Signup → Activate → Pay as a running example) and a definition card you can put next to any dashboard. For metric contracts more broadly, see the metrics series. For learning paths across the site, start at Learn.

What you’ll learn

Why generic funnels fail and what “product-shaped” means
A four-stage spine: Visit, Signup, Activate, Pay (and when to add or remove stages)
How to map stages to concrete events and eligibility rules
Definition cards, multi-path journeys, and B2B vs consumer twists
A worked SaaS example, mistakes list, and a 60-minute practice drill

A funnel is a contract about order and meaning

At minimum a funnel answers: who entered a stage, who reached the next stage, in what time window, and with what exclusions. It is not a pretty triangle. It is a set of definitions. If two teams disagree on “activated,” they do not have a funnel debate; they have a vocabulary debate wearing chart clothes.

Good stage names are verbs or clear states customers would recognize: started session, created account, completed first value action, paid. Bad stage names are moods: engaged, interested, aware, loyal. Moods invite redefinition every quarter.

Many digital products can start with a short spine and only branch when the business forces it.

Product-shaped funnel stages: Visit, Signup, Activate, Pay in sequence

Visit: someone showed up with enough identity to count (session, device, or cookied user depending on privacy and product).
Signup: they created an account or otherwise identified for ongoing relationship (not every product needs this before pay).
Activate: they did the first action that predicts retained value (the “aha”), not merely logged in twice.
Pay: money moved under the definition Finance will accept (first paid invoice, subscription start, not “clicked pricing”).

This spine is a template, not a law. Marketplaces may need Supply and Demand funnels. Content sites may care about Subscribe before Pay. Offline retail may start at Store Visit. The rule is: stages must match how you acquire and monetize, and each stage must map to data.

Map stages to events, not vibes

For each stage write the event name, grain, and rules:

Funnel definition card mapping Visit, Signup, and Activate stages to session_start, account_created, and first_value_…

Stage	Example event	Notes to write down
Visit	`session_start`	Bot filter? Logged-out only? App vs web?
Signup	`account_created`	Email verified required? SSO counts?
Activate	`first_value_action`	Which action? Must it be within 7 days of signup?
Pay	`subscription_started`	Trials? Refunds within 24h excluded?

Activation is where teams fight. “Logged in three times” is easy to instrument and often weak. “Created first project and invited a teammate” may be harder and more predictive. Pick the action product believes causes value, then validate with retention later (Part 3). Do not let dashboards invent activation because the event already existed in Segment.

Eligibility between stages

Conversion from stage A to B is only meaningful if the denominator could have done B. People who never signed up cannot activate under an account-based activation definition. Visitors who are already customers should not re-enter a “new signup” funnel without a separate path. Write eligibility: “Activate rate = users with first_value_action within 7 days of account_created, among users with account_created in the cohort window.”

Windows, order, and multi-path reality

Classic funnels assume order: Visit then Signup then Activate then Pay. Real products allow Pay before Activate (gift purchase), or Activate without Signup (guest workflows that later merge). You have three honest options:

Strict order funnel: only count forward progress in order (clean story, undercounts messy truth).
State model: track flags per user (has_visited, has_paid) without forcing a single path (more accurate, harder to draw as a triangle).
Primary path + side paths: report the main ordered funnel for product reviews, plus a small table of alternate paths that matter (guest checkout, sales-assisted).

Pick one primary representation for executive reviews so the room shares a picture. Keep the messy truth available for analysts. Lying with a triangle is worse than showing two paths.

B2B, consumer, and marketplace twists

B2B: the customer may be an account, not a user. Stages might be: Site visit → Demo request → Opportunity → Closed-won → Seat activation. Mixing user-level product activation with account-level revenue without saying so creates fake drop-offs.

Consumer subscription: trial start may sit between Activate and Pay. Refunds and chargebacks need a “net paid” definition Finance trusts.

Marketplace: one funnel for buyers, one for sellers. A single blended funnel hides which side is sick.

When in doubt, write the economic actor in the stage name: “Buyer activate,” “Seller list first item.”

Instrumentation checklist before the pretty chart

Event names stable and versioned (no silent renames).
User and account IDs join cleanly across web, app, and billing.
Timezone and “day” boundary documented (UTC vs user local).
Bot and QA traffic filtered the same way in every stage.
Historical backfill plan if you change activation definition.
Owner for each stage definition (product for activate, finance for pay).

If event quality is weak, fix pipelines and tracking before arguing about a 0.3 point conversion move. The data quality series and data pipelines series exist for that pain. Funnel debates on broken events waste political capital you will need later for real product calls.

Worked example: notes app SaaS

Product: collaborative notes. Acquisition is mostly web. Monetization is team plans.

Stage definitions they ship:

Visit: session_start on marketing or app web, excluding internal IPs and known bots.
Signup: account_created with verified email or SSO.
Activate: first of (note_created and length ≥ 20 chars) or teammate_invited, within 7 days of signup.
Pay: subscription_started with plan in (team, business) and status not refunded within 24 hours.

Toy weekly volumes (illustrative only):

Stage	Users	Step conversion from previous
Visit	50,000	n/a (top)
Signup	4,000	8.0%
Activate	2,200	55.0%
Pay	180	8.2%

Product reads this and does not scream “fix top of funnel” only. Signup-to-activate at 55% may be healthy; pay at 8.2% of activated may be the monetization problem. Or sales cycle length means pay needs a 30-day window, not 7. The funnel card must include windows per step, not one global magic window.

-- Sketch: signup to activate within 7 days
-- Grain: one row per user who signed up in the cohort week
SELECT
  u.user_id,
  u.account_created_at,
  MIN(e.event_at) AS first_value_at,
  CASE
    WHEN MIN(e.event_at) <= u.account_created_at + INTERVAL '7' DAY
    THEN 1 ELSE 0
  END AS activated_7d
FROM users u
LEFT JOIN events e
  ON e.user_id = u.user_id
 AND e.event_name IN ('note_created', 'teammate_invited')
 -- note_created also filtered by length in upstream model
GROUP BY 1, 2;

When AI drafts this SQL for you, check joins, windows, and event filters carefully. Use the habits in How to check AI-written SQL before the funnel becomes a board number.

Common mistakes

Copying another company’s stages without their events or business model.
Calling login “activation.” Login is hygiene; activation is value.
Mixing users and accounts in one funnel without labels.
No time window so late payers inflate old cohorts forever.
Changing activation mid-quarter without versioning, then celebrating a fake lift.
Dashboard-only definitions that do not match the warehouse or Finance.
Twelve stages that nobody can instrument or remember.

When to add stages (and when not to)

Add a stage only when a team will own improving it and when an event can measure it weekly. “Consideration” with no event is not a stage; it is a storyboard caption. Useful adds include Trial start, Invite sent, or First value for a second persona. Useless adds include every micro-click between Visit and Signup that nobody will staff a project to fix.

If leadership wants more stages for storytelling, keep a short operational funnel for weekly reviews and a longer narrative funnel for onboarding docs. Never let the narrative funnel become the only source of “conversion” in OKRs unless it is fully instrumented.

How to practice this week

Write your product’s stages on paper in five names or fewer.
For each stage, name one event (or admit it does not exist yet).
Add a window and an owner per stage on a one-page definition card.
Compare Marketing’s funnel slide to your card. List every mismatch.
Pick the single worst mismatch and open a ticket to fix event or definition, not a ticket to “align offline.”

Quick recap

Funnels work when stages are product-shaped, event-backed, windowed, and owned. Visit → Signup → Activate → Pay is a useful spine, not a universal religion. Definition cards beat decorative triangles. Fix instrumentation before you argue decimals.

Next in Customer analytics basics: conversion math without magic (eligible, success, rate, and windows you can defend).

Sources

Croll and Yoskovitz, Lean Analytics (stage-appropriate metrics by business model): https://leananalyticsbook.com/
Google HEART framework (quality of experience metrics alongside funnels): https://research.google/pubs/pub36299/
Amplitude Docs on funnels (event ordering and conversion windows, product analytics patterns): https://help.amplitude.com/hc/en-us/articles/230403928-Funnel-Analysis
Mixpanel Docs on funnels and conversion: https://docs.mixpanel.com/docs/reports/funnels
Reforge materials on retention and activation (conceptual; many free essays via their blog): https://www.reforge.com/blog