Segment

Route any billing, support, or survey signal from your existing Segment source.

Category: Data pipes · Auth: Write key / webhook

If you already run Segment, you can route events to ChurnWarn without adding our SDK — ChurnWarn acts as a destination for your existing source. Instead of connecting each tool one by one, you reuse the pipeline you've already built: the billing, support, and product events flowing through Segment can fan out to ChurnWarn alongside your warehouse and analytics destinations. It's the fastest path to coverage for teams with a mature data stack.

What it pulls

Any billing, support, or survey signal already passing through Segment.
Routed from your existing source — no new tracking code, just a new destination.

Signals it feeds

Any metric, depending on what you forward — login, feature_used, plan_upgraded, seat_used, the support and survey events, and more. Because you control the mapping, Segment can fill in whichever signals your direct integrations don't already cover.

Setup

In ChurnWarn, open Settings → Integrations → Segment and copy your ChurnWarn ingest endpoint and key.
In Segment, add ChurnWarn as a destination (webhook) on the relevant source.
Map Segment events to ChurnWarn eventTypes, using userId / groupId as the externalAccountId so events attach to the right account.
Send a test event and confirm it appears on the account.

Avoid double-counting

If a signal already flows through a direct integration (e.g. Stripe), don't also forward it via Segment — you'll count it twice and distort the score. Use Segment for the signals your direct connectors don't cover, and pick one path per signal.

Mind your event names

Segment events only score if their mapped eventType matches a metric a component reads. Map deliberately — an unmapped event is ingested but contributes to nothing until a component references it.

Reference: Segment destinations.