Core Concepts
Understand the objects and ownership boundaries used throughout Prevenue.
Prevenue is an in-product revenue orchestration layer. It uses product, billing, account, and intelligence evidence to decide and measure customer journeys. It does not replace the customer's authentication, billing, entitlement, CRM, lifecycle, support, or analytics systems of record.
Funnel
A Funnel is a versioned definition for one Grow, Save, or Convert objective. It owns entry, eligibility, placement, customer steps, follow-up, approved actions, and the verified goal.
A published Funnel version is immutable. A later edit creates a new draft/version.
Journey and opportunity
A journey is one account or subject's execution of a published Funnel. An opportunity is the operational view of that journey from detection through a verified, closed, or reversed outcome.
Use Opportunities for work in progress. Use Results for aggregate measurement.
Account and user
An account is the B2B customer record that consolidates billing, plan, trial, lifecycle, product activity, users, lists, Funnels, Opportunities, Signals, Events, and intelligence context.
A user is a person acting inside that account. User role and verified authority can change the available CTA, but they do not change whether the account is eligible. A user without billing authority may request or share an approval instead of taking a commercial action directly.
Event
An event is product, billing, setup, or customer activity. Events need a stable account identity, clear name, timestamp, source, and safe structured properties.
An event can wake Funnel decisioning. It does not prove that a customer is eligible or that a commercial outcome happened.
Mapping
A mapping connects a raw event name and source to a normalized semantic meaning such as usage, activation, limit friction, upgrade intent, checkout, billing lifecycle, downgrade intent, cancel intent, support friction, or integration connected.
Mappings help readiness and intelligence. They are not required for every deterministic event when a Funnel uses an explicit typed event contract.
Signal
A Signal is account-level evidence that Prevenue has classified as a possible revenue moment. Signals can explain Grow, Save, Convert, or Watch context, confidence, reason, recommendation, and delivery history.
Signals may feed Funnel eligibility or prioritization. They do not own the customer journey.
Intelligence
Intelligence includes derived scores, sentiment, momentum, Event KPIs, predictions, timing, preventability, confidence, and caveats.
Deterministic facts can control eligibility directly. Learned fields require validated confidence, freshness, fallbacks, and reporting before they control customer treatment.
Experience, offer, and action
An experience is the rendered modal, drawer, overlay, or other approved surface. An offer is the approved commercial value proposition. An action is a server-authorized request such as upgrade, annual conversion, purchase, trial, save change, approval request, or customer-owned operation.
The browser can request an opaque approved action. It is never billing, entitlement, identity, or financial authority.
Outcome and result
An outcome is authoritative evidence that the Funnel goal happened, failed, or reversed. A click or accepted request is not success.
Results aggregates Funnel opportunities, impressions, clicks, conversions, revenue, outcome types, attribution roles, and reversals without double-counting the same verified result.
Integrations and delivery
Integrations connect sources of truth and optional destinations. Manage providers in Settings > Integrations. Delivery can extend a Funnel into lifecycle, CRM, webhook, Slack, or another approved system, but it does not replace the Funnel's in-product journey or outcome contract.