Segment Source Setup

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

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

What Segment should sendCopy Anchor Link

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 fieldsCopy Anchor Link

Segment payloads should include:

• messageId
• event or type
• userId (on identify calls, this is the user whose name and email you send)
• groupId or equivalent account identity.
• timestamp or sentAt
• properties

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

Account factsCopy Anchor Link

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, support text, query strings, or free-form cancellation reasons.

User names and emailsCopy Anchor Link

Forward Segment identify calls so each Account lists its users by name. SaaSFunnels reads name (or firstName and lastName) and email from traits and keeps them against the userId. An identify call doesn't need a groupId. Traits on track calls (traits or context.traits) work too. Emails stay out of event properties.

Setup stepsCopy Anchor Link

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

Sample event shapeCopy Anchor Link

{
  "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 setupCopy Anchor Link

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

Common problemsCopy Anchor Link

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

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

Related articlesCopy Anchor Link

• Integrations
• Events
• Event Log and Payload Review
• Data Quality Checks