Getting Started
Connect the minimum data, build one Funnel, test the customer journey, and verify the first real outcome.
Use this guide for a new workspace or a workspace that has data but no working customer journey yet.
The shortest useful path
- Choose one objective: Grow, Save, or Convert.
- Connect billing truth and a small set of account-scoped product events.
- Confirm identity, event quality, and the mappings needed for that objective.
- Create one Funnel from a template or start blank.
- Define when it starts, who is eligible, the customer steps, and the verified goal.
- Test one qualifying context and one no-render context.
- Publish only after the native product path, viewer authority, and outcome evidence are safe.
Do not begin by instrumenting every click or building a library of rules. The first milestone is one complete, explainable journey.
Step 1: choose an objective
| Objective | Use it for |
|---|---|
| Grow | Upgrades, annual conversion, seats, add-ons, top-ups, or additional capacity. |
| Save | Churn prevention, contraction save, payment recovery, or a safer support/value path. |
| Convert | Signup, trial-to-paid, free-to-paid, checkout, subscription, purchase, lead, or opt-in conversion. |
Watch remains useful for monitoring and low-confidence investigation, but it is not a Funnel objective.
Step 2: connect the minimum sources
- Use Stripe Connect Setup for plans, trials, MRR, invoices, payment state, and verified billing movements.
- Use Web SDK Installation for browser-visible intent and Funnel placements.
- Use Direct API Installation for durable backend activity, lifecycle state, account identity, and customer-owned outcome events.
PostHog or Segment can forward an existing allowlist when those events already have stable account identity. Start with the few events required by the first Funnel.
Use Developer Tools Overview when you want to validate a payload locally, install an agent handoff file, send a Direct API smoke event, or let an MCP-capable coding agent read setup context safely.
Step 3: verify evidence
Open Events and confirm that recent rows have a stable account identifier, event name, timestamp, source, and safe structured properties. Correct mappings when the raw name does not communicate the event's revenue meaning.
Open Accounts to confirm the billing account, users, plan or trial context, signup date, and current evidence resolve to the same record. Use Signals when you need scored or learned revenue evidence; a deterministic Funnel can start without a prediction.
Step 4: build the Funnel
Open Funnels, select New funnel, and choose a template or start blank.
Keep these decisions explicit:
- What wakes decisioning.
- Which accounts and users qualify.
- Where the experience can appear.
- What the customer sees and what happens after dismissal.
- Whether the viewer can act or must request approval.
- What authoritative evidence marks the goal complete.
Read Funnels for the full model.
Step 5: test and publish
Use Studio test mode with realistic account, user-role, plan, event, and intelligence context. Confirm the experience is usable on desktop and mobile and that the host application's native path remains available when Prevenue does not render.
Publishing makes a version available for runtime decisions; it does not make a click equal a conversion. A real conversion requires verified customer-system or provider evidence.
Step 6: operate and learn
- Use Opportunities to follow live account journeys.
- Use Results to measure reach, conversion, revenue, and reversals.
- Use Intelligence Learning when learned targeting or prioritization would improve the next iteration.
- Configure optional lifecycle and team delivery in Destinations.
Activation milestones
- Setup complete — installation is verified and a Funnel has passed a test.
- Activated — the first real eligible user receives the published Funnel.
- Value realized — the first verified commercial or retention outcome is recorded.