PathwAI's Segment integration runs through webhooks rather than a Segment source or destination. PathwAI can post each completed submission from an Ending step, or each mapped Data Platform event from the webhook destination, as JSON to an HTTPS endpoint you run. That endpoint reshapes the payload into the Segment calls your workspace expects and sends it on with your Segment write key.
What data moves
- Ending webhook: The JSON body holds the submission ID, flow ID and a timestamp, plus the answers keyed by each step's custom key. The cart and the user profile are added when you include them.
- Webhook destination: one request per mapped event, such as flow_started, step_entry, step_exit, signup, purchase or flow_completed, carrying the event name, timestamp, consent state and the properties a transformer allows.
- Your endpoint to Segment: whatever it builds from those payloads.
Where it is configured
Ending step webhooks are set under the Ending's Events → Exit. The Data Platform webhook destination is added under Data → Destinations → Webhook, with its URL, headers and optional signing secret.
Use cases
Flow events in the warehouse
Forward flow_started and flow_completed to Segment so funnel volume sits next to the rest of your product data.
Purchases with order IDs
Map the purchase event, which carries value, currency and order ID, so revenue from flows reconciles with your other sources.
Completed intakes for downstream tools
Use the Ending webhook when a downstream tool needs the full set of answers from one submission.
How to set it up
- Stand up an HTTPS endpoint that accepts JSON and calls Segment with your write key.
- In PathwAI, open Data → Destinations, add Webhook, paste the URL and set a signing secret.
- In the Event mapping tab, add the events to send and attach a transformer if a custom property is needed.
- Verify the X-Pathwai-Signature header in your endpoint, then switch the destination on.
Good to know
- The Data Platform webhook destination sends only the events you add and switch on in its Event mapping tab. With a signing secret set, each request carries an X-Pathwai-Signature header with an HMAC-SHA256 of the body, and a failed delivery is retried before it is set aside.
Segment integration FAQ
Does PathwAI send data to Segment directly?
No. PathwAI posts to an endpoint you run, and that endpoint calls Segment. This keeps the Segment write key and the field mapping on your side.
Which events can go to Segment?
The built-in flow events (flow_started, step_entry, step_exit, step_carried, signup, purchase, consent_updated, flow_completed), custom Data Platform events, and website SDK events.
How do I know a request came from PathwAI?
Set a signing secret on the webhook destination and check the X-Pathwai-Signature header, an HMAC-SHA256 of the raw body.
Want to see Segment in a flow?
We can walk through where Segment fits in your funnel and exactly which data it would receive.