Skip to content

Fractional CMO & Growth6 min read

Why Your Activation Funnel Isn’t Working (And the Dashboard That Fixes It)

Led growth at cnvrg.io before its acquisition by Intel.

A sculptural metal loop curves around a luminous teal inner edge.

An activation funnel helps investigate whether new users reach the product value you define. This guide illustrates a dashboard method and the evidence needed to interpret it.

Ask what fraction of an eligible signup cohort reached the agreed product value within its observation window. This guide uses seven days as an example. If the answer is unavailable, investigate definitions, event coverage and maturity before concluding whether the product or tracking is the problem.

I build activation dashboards around the product value a customer should experience. This guide uses a six-event example and review-only SQL to show the method; I adapt the event definitions, cohort rules and observation window to each product. It is step 2 of the 1,000-User System.

What Activation Actually Means

Activation is not "the user logged in." It is not "the user completed onboarding." Activation is the moment the user first receives the core value your product promises. At Elementor, that moment is publishing a live page. At Riverside.fm, it is completing a first recording session. To scope execution after identifying the activation constraint, see product growth implementation.

Every product has a different activation event. The mistake most teams make is tracking the wrong one (usually a proxy like "completed step 3 of onboarding") or tracking none at all.

Before you build the dashboard, define the activation event in one sentence: "A user is activated when they [specific action] within [time window]." Write it down. Get the product team to agree. This sentence is the foundation everything else sits on.

The 6 Events the Dashboard Tracks

These six events are an example, not a universal activation definition. Report observed product value separately from the ordered path through onboarding. A user can receive value without every instrumented step being recorded; missing steps require investigation, not an automatic conclusion that the user failed.

#Event NameDescriptionIllustrative drop-off assumption
1signup_completedEmail confirmed or OAuth connected5-15%
2onboarding_startedFirst meaningful product screen reached20-40%
3first_action_takenFirst meaningful interaction (create, connect, import)25-45%
4core_feature_usedThe primary feature that delivers value engaged15-30%
5value_moment_reachedThe activation event (defined above)10-25%
6return_visitUser returns within 48 hours of activation20-40%

Use weekly signup cohorts with explicit denominators: eligible users who have had seven days to activate, users still waiting for that window, observed product value and the ordered path. A return within 48 hours of first value is a separate measure with its own follow-up window; it is not calendar-day-2 retention.

The SQL Query

This PostgreSQL reference expects events(tenant_id, user_id, name, created_at TIMESTAMPTZ) and exactly one analysis_parameters row with tenant_id, as_of and cohort_start. A trusted caller must validate that single row, authorize its tenant and bind the values through the database driver; this SQL does not authenticate callers or reject invalid parameter cardinality. Set the analysis connection to UTC and supply full signup history before filtering the reporting period.

The query was checked on synthetic fixtures in DuckDB and PostgreSQL; validate your actual schema and event definitions before use. Timestamp ties do not establish order; use a trusted sequence key if your product batches events at the same timestamp.

-- Review candidate only. Never executed against a shared/customer database.
-- analysis_parameters must contain exactly one trusted tenant_id/as_of/cohort_start row.
-- Input contract: events(tenant_id, user_id, name, created_at TIMESTAMPTZ).
-- Full signup history must be available before the reporting-window filter.
-- UTC reporting; strictly increasing timestamps for an observed ordered path.
WITH p AS (
  SELECT tenant_id, as_of, cohort_start FROM analysis_parameters
), scoped_events AS (
  SELECT DISTINCT e.tenant_id, e.user_id, e.name, e.created_at
  FROM events e CROSS JOIN p
  WHERE e.tenant_id = p.tenant_id
    AND e.user_id IS NOT NULL AND TRIM(e.user_id) <> ''
    AND e.created_at IS NOT NULL AND e.created_at <= p.as_of
), first_signups AS (
  SELECT tenant_id, user_id, MIN(created_at) AS signup_at
  FROM scoped_events WHERE name = 'signup_completed'
  GROUP BY tenant_id, user_id
), cohort AS (
  SELECT s.*, p.as_of,
    s.signup_at + INTERVAL '7 days' <= p.as_of AS week1_mature
  FROM first_signups s CROSS JOIN p
  WHERE s.signup_at >= p.cohort_start AND s.signup_at <= p.as_of
), paths AS (
  SELECT c.*, ob.at AS onboarding_at, fa.at AS first_action_at,
    cf.at AS core_at, ov.at AS ordered_value_at,
    pv.at AS product_value_at, rv.at AS return_at
  FROM cohort c
  LEFT JOIN LATERAL (
    SELECT MIN(e.created_at) AS at FROM scoped_events e
    WHERE e.tenant_id = c.tenant_id AND e.user_id = c.user_id
      AND e.name = 'onboarding_started' AND e.created_at > c.signup_at
      AND e.created_at <= c.signup_at + INTERVAL '7 days'
  ) ob ON TRUE
  LEFT JOIN LATERAL (
    SELECT MIN(e.created_at) AS at FROM scoped_events e
    WHERE e.tenant_id = c.tenant_id AND e.user_id = c.user_id
      AND e.name = 'first_action_taken' AND e.created_at > ob.at
      AND e.created_at <= c.signup_at + INTERVAL '7 days'
  ) fa ON TRUE
  LEFT JOIN LATERAL (
    SELECT MIN(e.created_at) AS at FROM scoped_events e
    WHERE e.tenant_id = c.tenant_id AND e.user_id = c.user_id
      AND e.name = 'core_feature_used' AND e.created_at > fa.at
      AND e.created_at <= c.signup_at + INTERVAL '7 days'
  ) cf ON TRUE
  LEFT JOIN LATERAL (
    SELECT MIN(e.created_at) AS at FROM scoped_events e
    WHERE e.tenant_id = c.tenant_id AND e.user_id = c.user_id
      AND e.name = 'value_moment_reached' AND e.created_at > cf.at
      AND e.created_at <= c.signup_at + INTERVAL '7 days'
  ) ov ON TRUE
  LEFT JOIN LATERAL (
    SELECT MIN(e.created_at) AS at FROM scoped_events e
    WHERE e.tenant_id = c.tenant_id AND e.user_id = c.user_id
      AND e.name = 'value_moment_reached' AND e.created_at >= c.signup_at
      AND e.created_at <= c.signup_at + INTERVAL '7 days'
  ) pv ON TRUE
  LEFT JOIN LATERAL (
    SELECT MIN(e.created_at) AS at FROM scoped_events e
    WHERE e.tenant_id = c.tenant_id AND e.user_id = c.user_id
      AND e.name = 'return_visit' AND e.created_at > pv.at
      AND e.created_at <= pv.at + INTERVAL '48 hours'
  ) rv ON TRUE
)
SELECT DATE_TRUNC('week', signup_at) AS cohort_week,
  COUNT(*) AS cohort_signups,
  COUNT(*) FILTER (WHERE week1_mature) AS week1_eligible_signups,
  COUNT(*) FILTER (WHERE NOT week1_mature) AS week1_pending_signups,
  COUNT(*) FILTER (WHERE week1_mature AND onboarding_at IS NOT NULL) AS ordered_onboarding,
  COUNT(*) FILTER (WHERE week1_mature AND first_action_at IS NOT NULL) AS ordered_first_action,
  COUNT(*) FILTER (WHERE week1_mature AND core_at IS NOT NULL) AS ordered_core,
  COUNT(*) FILTER (WHERE week1_mature AND ordered_value_at IS NOT NULL) AS ordered_value,
  COUNT(*) FILTER (WHERE week1_mature AND product_value_at IS NOT NULL) AS product_value,
  COUNT(*) FILTER (WHERE week1_mature AND product_value_at IS NOT NULL AND ordered_value_at IS NULL)
    AS value_without_observed_ordered_path,
  ROUND(100.0 * COUNT(*) FILTER (WHERE week1_mature AND product_value_at IS NOT NULL)
    / NULLIF(COUNT(*) FILTER (WHERE week1_mature), 0), 1) AS week1_value_rate,
  ROUND(100.0 * COUNT(*) FILTER (WHERE week1_mature AND ordered_value_at IS NOT NULL)
    / NULLIF(COUNT(*) FILTER (WHERE week1_mature), 0), 1) AS week1_ordered_path_rate,
  COUNT(*) FILTER (WHERE week1_mature AND product_value_at + INTERVAL '48 hours' <= as_of)
    AS return_window_eligible,
  COUNT(*) FILTER (WHERE week1_mature AND product_value_at IS NOT NULL
    AND product_value_at + INTERVAL '48 hours' > as_of) AS return_window_pending,
  COUNT(*) FILTER (WHERE week1_mature AND product_value_at + INTERVAL '48 hours' <= as_of
    AND return_at IS NOT NULL) AS returned_within_48h,
  ROUND(100.0 * COUNT(*) FILTER (WHERE week1_mature
      AND product_value_at + INTERVAL '48 hours' <= as_of AND return_at IS NOT NULL)
    / NULLIF(COUNT(*) FILTER (WHERE week1_mature
      AND product_value_at + INTERVAL '48 hours' <= as_of), 0), 1) AS return_within_48h_rate
FROM paths
GROUP BY 1 ORDER BY 1 DESC;

First check event definitions, missing records, duplicates and mature cohort sizes. Inspect a large observed drop with product and customer evidence before choosing a fix. Keep raw first-value behavior separate from a missing or out-of-order instrumented path, and report an incomplete observation window as pending rather than a failed activation.

What a Series-Stage SaaS Found When They Ran This

Author-reported January 2026 engagement: an activation analysis found 62% of signups dropping off between onboarding_started and first_action_taken. The onboarding flow had 6 steps before users could interact with the core product; we reduced it to 3. I reported week-1 activation moving from 31% to 58% in the following cohort after that onboarding change. This is a reported cohort observation, not an independently verified causal estimate. The revised SQL above is a review-only example rather than an executed client extract, so it does not independently reproduce those figures.

The dashboard identifies a place to investigate. Before judging a change, validate the event coverage, compare cohorts with the same maturity window, account for acquisition mix and record what remains unknown.

Common Mistakes When Building This Dashboard

Mistake 1: Tracking the Wrong Activation Event

If you track "completed onboarding checklist" as your activation event, you are measuring compliance with your UX flow, not value delivery. A user can complete all 5 onboarding steps and never experience the core value. Track the product outcome, not the onboarding behavior.

Mistake 2: Aggregating Across Channels

Segment where the question and available sample support it, for example by acquisition source, buyer type or plan. Preserve the overall denominator and avoid drawing strong conclusions from small subgroups.

Mistake 3: Looking at All-Time Data Instead of Cohorts

Use cohorts with compatible definitions and maturity when investigating change. A weekly cohort is useful for this example; another product may need a different grouping or window. An aggregate can provide context, but can hide changes in acquisition mix or follow-up time.

Mistake 4: Fixing Onboarding Without Fixing the Activation Event Definition

I have seen teams spend 3 months optimising a 6-step onboarding flow without first checking how the proposed value event relates to retention. Compare that event with product behaviour, customer evidence and later retention. Missing or weak association may reflect sample, timing, segment mix or instrumentation; it does not alone prove the event wrong or establish causation.

What Comes After the Dashboard

Choose the improvement target from the baseline, meaningful product value, mature cohorts and commercial economics. Depending on the diagnosed constraint, test removing unnecessary steps, reducing time to value or adapting the path by user segment. Compare equivalent observation windows and keep an inconclusive result when the evidence does not support a decision.

The dashboard identifies patterns to investigate, not a proven cause or an automatic fix. Check event quality, mature cohort size and product and customer evidence before choosing an intervention. Compare subsequent mature cohorts and record other changes that could affect the result.

Next Step

This is step 2 of the 1,000-User System. Step 1 is the activation audit (defining your activation event and getting a baseline number). If you have not done that yet, start there.

Book a Call for the complete activation audit template, the dashboard setup guide, and the event naming convention I use across all client implementations.

If you want me to run the activation audit at your company: Book a Call. Before the call, share your activation definition, event schema and current cohort report. We can assess evidence gaps and agree whether a scoped activation audit is the next step; access and deliverables are agreed separately.

SaaS activation funnel FAQ

What is a SaaS activation funnel?

A SaaS activation funnel measures the path from signup to an agreed first-value event, with explicit eligible and pending cohorts. The event and window follow the product. A missing seven-day report alone does not prove the business lacks an activation funnel.

Which events should a SaaS activation funnel track?

Choose events that represent your product's path from signup to first value and a later return. The six events in this guide are an example, not a universal requirement. Validate your activation definition against product behavior and retention; record observed value separately from the ordered onboarding path.

How do I fix a broken activation funnel?

Validate event definitions, missing records and mature cohort denominators first. Compare observed first value with the ordered path, then use product and customer evidence to investigate a large drop before choosing a fix. Treat incomplete observation windows as pending.

What is an activation event and how do I define one?

An activation event is the moment a user first receives the core value your product promises. It is not a login and it is not completing onboarding. Write it as one sentence: "A user is activated when they [specific action] within [time window]." Get the product team to agree on it. At Elementor, that moment is publishing a live page. At Riverside.fm, it is completing a first recording session.

Why measure activation by weekly cohort instead of an all-time rate?

Compatible cohorts help investigate changes without mixing different follow-up windows or acquisition populations. This example uses weekly signup cohorts and seven-day eligibility; other products may need another grouping. Report pending observations separately and retain aggregates where they answer a useful question.

What data does the activation SQL query need to run?

The query expects an events table with tenant_id, user_id, name and created_at as a timestamp with time zone, plus exactly one analysis_parameters row with tenant_id, as_of and cohort_start. It is a PostgreSQL reference. Set the analysis connection to UTC and supply full signup history before filtering the reporting period. Validate your actual schema and event definitions before use.

Can you run the activation audit for my company, and what should I prepare?

Yes. I personally investigate the agreed activation records and, where scoped, implement the dashboard or product-growth changes. Bring your value-event definition, event schema and current cohort report to discuss the evidence. Access, deliverables and any subsequent implementation are agreed separately.

The Growth Blocker

Get the next playbook in your inbox

Unsubscribe anytime.
All Posts

Work with Yaniv

Fractional Head of Growth for B2B SaaS, B2C, and e-commerce. Revenue that compounds, not spikes. Any channel, any motion, any stage.

Share

About the author

Yaniv Goldenberg, Fractional CMO & Head of GrowthYaniv GoldenbergFractional CMO & Head of Growth

Fractional CMO & Head of Growth — I lead strategy and personally execute across the revenue funnel. He scales post-product-market-fit companies to the revenue milestone that unlocks their next funding round. He scaled Elementor from $200K to $20M in ARR (a 100x increase), grew Riverside.fm’s Net MRR by 337%, and led demand generation at cnvrg.io, which Intel acquired in 2020. With 10+ years operating across every channel, motion, and stage, he hands the growth engine back once a team can run it without him.

  • Elementor $200K→$20M ARR
  • Riverside +337% Net MRR
  • cnvrg.io → Intel
  • 10+ yrs operating

By Yaniv Goldenberg, Fractional CMO & Head of Growth