PostHog Source Setup

Use PostHog when your product events already flow through PostHog and you want to forward a small, high-signal allowlist to Prevenue.

Open Settings > Integrations > PostHog in Prevenue to create credentials and review activity.

What PostHog should send

Forward custom product or revenue events that include account identity. Good examples include:

pricing_viewed
workspace_created
onboarding_completed
upgrade_clicked
limit_hit
subscription_updated
invoice_payment_failed
workspace_invited
integration_connected
integration_configured
team_member_invited
downgrade_page_viewed
cancel_started

Do not forward every PostHog SDK/system event. Events whose names begin with $ are usually diagnostic in Prevenue and should not be treated as customer evidence.

Required fields

PostHog payloads should include:

event
uuid or id
timestamp
properties.distinct_id
An account identity such as properties.account_id, properties.group_id, properties.workspace_id, or $groups.workspace

For Prevenue app events, properties.workspace_id is used as the customer/account identity.

Account facts

When PostHog already has account or group traits, forward the standard SaaS facts in properties with the event allowlist:

account_created_at, signup_at, or customer_created_at
plan, plan_name, or current_plan
account_status or subscription_status
is_in_trial, trial_started_at, and trial_ends_at when Stripe is not connected
user_count, active_user_count, seat_count, or member_count

Stripe remains authoritative for billing and trial state when connected. PostHog should not forward raw user lists, emails, support text, query strings, or free-form cancellation reasons.

Setup steps

Open Settings > Integrations > PostHog.
Create a PostHog intake credential.
Copy the endpoint and Authorization: Bearer <key> header.
In PostHog, create a Data Pipelines webhook destination.
Set the destination URL to the Prevenue PostHog endpoint.
Add the Authorization header.
Forward only selected custom revenue or product events.
Exclude PostHog SDK/system events whose names begin with $.
Send a custom test event with account identity.
Return to Prevenue and confirm recent normalized PostHog activity.

The PostHog destination test button may send $pageview. Prevenue can receive that as a diagnostic, but it does not complete customer-event setup.

Sample event shape

{
  "event": "onboarding_completed",
  "properties": {
    "app_area": "onboarding",
    "account_created_at": "2026-06-01T12:00:00.000Z",
    "active_user_count": 6,
    "distinct_id": "user_456",
    "is_in_trial": true,
    "plan": "starter",
    "seat_count": 10,
    "trial_ends_at": "2026-06-28T12:00:00.000Z",
    "workspace_id": "acct_or_workspace_123"
  },
  "timestamp": "2026-06-20T15:00:00.000Z",
  "uuid": "ph_evt_001"
}

Verify setup

Open Settings > Integrations > PostHog.
Confirm the status is ready or connected.
Check last activity and issues.
Open Events and filter source by PostHog.
Confirm the rows are customer events, not only diagnostics.
Confirm mappings for the PostHog events.
Re-run the Revenue Signal Scan.