Events
Understand what Prevenue expects from incoming customer, product, and billing events.
Useful signals start with useful events. Prevenue does not need a full clickstream. It needs a small set of account-scoped events that explain activation, value, friction, billing context, expansion intent, conversion intent, and risk.
Required shape
Every useful event should include:
- A stable account, workspace, tenant, company, or customer identifier.
- A clear event name.
- A timestamp.
- A source.
- Structured properties that add context without leaking secrets or raw customer text.
User identity can help connect people to accounts, but account identity is what makes revenue signals reliable.
Event families to prioritize
| Family | Examples | Why it matters |
|---|---|---|
| Usage | feature_used, workflow_completed, report_exported, api_credits_used, generation_completed, sync_completed | Shows value and adoption. |
| Activation | account_activated, first_value_completed, onboarding_completed | Shows whether a customer reached setup milestones. |
| Limit friction | limit_hit, quota_blocked, overage_prompt_viewed | Shows pressure that may become expansion or frustration. |
| Upgrade intent | pricing_viewed, upgrade_clicked, premium_feature_clicked | Shows expansion or conversion interest. |
| Checkout | checkout_started, checkout_completed, checkout_abandoned | Shows conversion progress and drop-off. |
| Billing lifecycle | subscription_updated, invoice.payment_failed, payment_succeeded, plan_changed | Shows billing state and payment risk/recovery context. |
| Downgrade or cancel intent | downgrade_flow_started, cancel_flow_started | Shows retention risk. |
| Team expansion | team_member_invited, seat_added, role_assigned | Shows multi-user adoption and expansion surface. |
| Support friction | support_needed, setup_failed, sync_failed | Shows product blockers and save opportunities. |
| Integration connected | integration_connected, oauth_connected, destination_configured | Shows setup depth and activation. |
Properties
Good properties are bounded and structured:
plan,current_plan,target_planfeature,feature_key,feature_area,is_key_feature,is_premium,quantity,valueusage_ratio,allowanceintegration,providerreason_codesentiment,sentiment_score,sentiment_confidence,sentiment_source
Avoid raw URLs with query strings, cookies, auth headers, secrets, free-text feedback, transcripts, logs, stack traces, prompts, and full request or response bodies.
Sentiment
Sentiment can be sent explicitly on an event or assigned as a mapping default in the Events page. Explicit event payload sentiment wins. Mapping sentiment fills only omitted or unknown event sentiment unless a user intentionally overwrites explicit sentiment in the drawer.
Use:
positivefor healthy intent, completion, activation, upgrade, or successful setup.negativefor limit blocks, failures, support pressure, downgrade, cancel, or abandonment.neutralonly for explicitly neutral product signals.unknownwhen sentiment is unavailable.
The Events page lets operators filter by sentiment, source, and review status; show an optional sentiment column; and edit the mapped default beside the category mapping.
Source guidance
Use Direct API Installation for backend source-of-truth events. Use Web SDK Installation for browser-safe supplemental intent. Use Stripe Connect Setup for customer billing activity. Use PostHog Source Setup or Segment Source Setup when those tools already collect your product events.
Review flow
- Open
Events. - Check pipeline diagnostics for raw, diagnostic, rejected, normalized, mapping, and outcome counts.
- Use Event Log and Payload Review to inspect incoming rows.
- Confirm or edit the event's semantic category.
- Assign, confirm, ignore, or leave unknown the mapped sentiment default.
- Open the event drawer for score, confidence, source preview, and overwrite-explicit controls.
- Use Event Mapping and Signal Readiness to understand readiness impact.
- Use Data Quality Checks when events are rejected, missing identity, duplicated, or too noisy.
Sentiment mapping changes are audit-safe: Prevenue records the previous and new sentiment fields, overwrite flag, affected counts, user context when available, and timestamp. The default propagation path preserves explicit sentiment on existing events.
How many events are enough?
One or two isolated events are diagnostic. Three or more relevant account-scoped events in a 14 day window can become directional. Five or more relevant events in 30 days, especially across more than one event family, can support stronger account-level KPI confidence.
Read Event KPI Signals for the account-level fields powered by sparse, high-quality event data.