Funnels
Build and operate in-product journeys that turn customer moments into measurable Grow, Save, or Convert outcomes.
Funnels is the primary place to solve a revenue problem in Prevenue. A Funnel decides when a customer journey starts, who is eligible, where the experience appears, what the customer sees, which approved action can happen, and which outcome proves success.
Open Funnels to create a Funnel, manage its lifecycle, or open its results.
The Funnel path
A Funnel keeps these decisions separate:
- Objective — Grow, Save, or Convert.
- Starts when — a product event, lifecycle/API call, signal or intelligence condition, or named placement wakes decisioning.
- Eligibility — account, user, role, plan, lifecycle, saved-list, or bounded intelligence conditions decide who qualifies.
- Customer steps — the modal, drawer, overlay, offer, follow-up, and alternate path the customer experiences.
- Commercial action — an approved upgrade, annual conversion, purchase, trial, save action, approval request, or customer-owned server action.
- Verified goal — authoritative evidence that the intended commercial or retention outcome happened.
An event tells Prevenue when to evaluate. Intelligence helps decide whether and which path is appropriate. The Funnel defines how the journey works.
Start from a template or blank Funnel
Use a template when the objective and journey resemble a common pattern such as feature-gate expansion, usage-limit expansion, trial conversion, annual conversion, cancellation recovery, contraction save, reactivation, or signup.
Start blank when the trigger, offer, steps, or outcome are specific to the product. Templates are editable starting points, not fixed campaigns.
Build and test
The Studio keeps the journey path and customer preview together. Use it to edit customer steps, targeting, outcome, and validation without treating the preview as proof that targeting or billing works.
Before publication:
- Confirm the entry and eligibility rules.
- Test a qualifying and a no-render context.
- Confirm viewer authority and the approval fallback for users who cannot act.
- Confirm the native product path still works when Prevenue does not render.
- Confirm the goal uses authoritative outcome evidence.
Published versions are immutable. Later edits create a new draft/version rather than rewriting the version already used by customer journeys.
Follow-up and delivery
In-product follow-up belongs to the Funnel. It can control repeat placement, cooldowns, caps, dismissals, and the next step while the account remains eligible.
Lifecycle and team destinations remain optional extensions. Configure providers in Settings > Integrations, then select the approved delivery behavior from the Funnel. External delivery is never enabled merely because intelligence found a pattern.
Operate and measure
- Use Opportunities for the live account-level journey queue.
- Use Accounts and Account Intelligence to investigate customer context.
- Use Results for Funnel performance and verified outcomes.
- Use Signals and Events when you need the evidence behind targeting or prioritization.