Segment Source Setup

Forward Segment track and group payloads into Prevenue with a scoped ingest key.

Use Segment when product events already flow through Segment and you want Prevenue to normalize selected track and group events into revenue semantics.

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

What Segment should send

Forward a small allowlist of account-scoped events. Good first examples include:

Product Used
Account Activated
Limit Hit
Upgrade Clicked
Checkout Started
Subscription Updated
Team Invited

Use names that match your product language, but keep them stable over time.

Required fields

Segment payloads should include:

messageId
event or type
userId
groupId or equivalent account identity.
timestamp or sentAt
properties

Prevenue needs group or account identity to attach events to account intelligence and signals.

Account facts

Segment can send standard SaaS account facts on track payloads or group payloads. Include these as bounded properties or group traits when available:

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. Do not forward raw user lists, emails, support text, query strings, or free-form cancellation reasons.

Setup steps

Open Settings > Integrations > Segment.
Create a Segment intake credential.
Copy the endpoint and Authorization: Bearer <key> header.
In Segment, configure a webhook or custom destination for the workspace source.
Set the destination URL to the Prevenue Segment endpoint.
Add the Authorization header.
Forward selected track or group payloads with account identity.
Send a Segment test event.
Return to Prevenue and confirm normalized Segment activity.

Sample event shape

{
  "event": "Upgrade Clicked",
  "groupId": "acct_123",
  "messageId": "seg_evt_001",
  "properties": {
    "account_created_at": "2026-06-01T12:00:00.000Z",
    "active_user_count": 6,
    "is_in_trial": true,
    "plan": "starter",
    "seat_count": 10,
    "trial_ends_at": "2026-06-28T12:00:00.000Z",
    "value": 1
  },
  "timestamp": "2026-06-20T15:00:00.000Z",
  "type": "track",
  "userId": "user_456"
}

Verify setup

Open Settings > Integrations > Segment.
Confirm the status is ready or connected.
Check active keys, last activity, and issues.
Open Events and filter source by Segment.
Confirm account identity is present.
Confirm mappings for the Segment events.
Re-run the Revenue Signal Scan.

Common problems

If Segment events arrive without account identity, review group calls and destination mappings.

If Segment events are too broad, reduce the forwarded event allowlist. Prevenue does not need every client event to produce useful revenue signals.

On this page