Skip to main content

Product-level funnels

Product-level funnels are journey definitions scoped to a single catalog product (product_id / internal product record). They let each product have its own stages and entry rules while still evaluating accounts (and their activities, subscriptions, and metrics) in your workspace.

They complement the workspace Funnels area in the FunnelStory app. Use that section for account- or workspace-level journey definitions (including timeline vs last match evaluation); product funnels appear in product- and hierarchy-aware account views when your workspace has multi-product and account hierarchy enabled.

Prerequisites​

  1. Products model configured and refreshed.
  2. Accounts list products (JSON array of product_id) consistent with that catalog — see Setting up hierarchy.
  3. Data you want stages to filter on (subscriptions, activities, account metrics, and so on) modeled and refreshing as usual.

What you configure​

For each product funnel:

  • Product — Exactly one product per funnel definition.
  • Name — Label for your team.
  • Stages — Ordered steps. Each stage has a filter (same conceptual filter builder as elsewhere in FunnelStory). Stages with no filter conditions do not count as active funnel stages for evaluation.

One active funnel per product — Activating a funnel for a product while another is active will fail until you deactivate the other. Draft or inactive funnels can coexist.

Product funnels and evaluators​

Workspace Funnels (main Funnels section) can use either timeline or last match evaluation. That choice changes whether progression is driven by historical replay or by which stage filters match right now. See Evaluators: timeline vs last match for a full comparison and when to use each.

Product-level funnels work differently: on each refresh, FunnelStory evaluates your stage filters against current account data and assigns each account to the rightmost (latest in order) stage whose filter matches. That is the same placement rule as last match on workspace funnels. Product funnels do not replay the full timeline the way a workspace funnel set to timeline does.

If your configuration UI shows an evaluator field on a product funnel, it is stored with the funnel; stage placement on refresh still follows this current-data, rightmost match behavior.

How evaluation and refresh work​

  • FunnelStory evaluates product funnels on a background schedule, and you can trigger work from the app when you activate or refresh a funnel (depending on your permission level).
  • After you change stage filters or activation, run a refresh on the funnel (or wait for processing) so account stage membership stays aligned with current data.
  • Stage statistics (accounts entered, in stage, exited) are available for reporting in the funnel experience.

Default stage names suggested in the product include Acquisition, Activation, Realized Value, Growth, and Purchase Intent — you can rename and replace them; what matters is the filter on each stage you want to enforce.

Hierarchy and product funnels​

  • Funnel membership is still per account (and driven by that account’s data).
  • Parent rows do not automatically “inherit” a child’s funnel position unless your stage filters explicitly encode that.
  • If parents are Container rollups only, you typically define stages for child accounts that carry the product usage signals.

Viewing product funnels​

With multi-product and hierarchy enabled, product funnel progress appears alongside per-product revenue and journey context on account views and related dashboards. Exact placement can evolve with the product; look for product selectors and funnel panels on the Accounts / revenue experience for your workspace.