Guided Onboarding and Setup
Use Setup to connect customer truth, verify data health, and reach the first tested Funnel without unnecessary manual configuration.
Setup is the activation command center. It should lead a workspace from selected objectives to one tested Funnel, not expose every internal data or intelligence control at once.
What Setup owns
Setup can show:
- The selected Grow, Save, or Convert objective.
- Source and destination connection state.
- Required account identity and user-role coverage.
- Recommended event families for the first Funnel.
- Event mapping, signal, and prediction readiness.
- Data gaps that make a journey unsafe or unreliable.
- The next useful setup action.
- Installation and test evidence.
The product should default safe mappings and confidence tolerance when evidence supports them. Operators review uncertainty and exceptions; they should not have to confirm every routine decision.
Recommended order
- Choose one objective and customer moment.
- Connect Stripe or the relevant commercial source of truth.
- Install the Web SDK placement and the smallest useful product-event allowlist.
- Add Direct API events for backend truth and verified outcomes.
- Confirm account and user identity.
- Review uncertain mappings and data gaps.
- Create and test the first Funnel.
- Connect optional lifecycle, CRM, webhook, or Slack delivery.
PostHog and Segment are useful when they already contain clean account-scoped events. Forward a narrow allowlist rather than an unbounded clickstream.
Identity and event quality
Prefer stable account, workspace, tenant, company, customer, or organization IDs. Emails, display names, anonymous IDs, and sessions can be secondary identities, but they should not be the only B2B account key.
Ignore diagnostic, rejected, duplicated, provider-test, and setup-smoke events when deciding whether a workspace is ready. A high event count does not compensate for missing identity or unclear meaning.
Intelligence readiness
Prediction readiness is a data-sufficiency view, not a promise that an account will convert, expand, or churn. Learned evidence can rank or explain accounts before it is safe to control Funnel eligibility.
Use Intelligence Learning for confidence, fallback, and authority boundaries. Use Revenue Signal Scan when the first scan returns gaps.
The first successful Setup run
A Setup run is complete when:
- The customer sources and account identity are verified.
- Required events appear in Events with usable mappings.
- A Funnel is saved and tested against qualifying and no-render contexts.
- Viewer authority and the approval fallback are defined.
- The goal has an authoritative verification path.
External destinations are optional for activation. Add them when they close a real operational gap; do not require them before the in-product journey itself works.