Segment
Events enter Segment's HTTP API as track calls, with consistent userId and anonymousId — from there they flow to any destination your Segment source already feeds.
Data delivered
Data delivered
- track events with full properties
- userId (lead) and anonymousId (visitor)
- Deduplication messageId and real timestamps
What it is for
What you can do with it
- Feed an existing Segment stack without re-instrumenting anything
- Migrate gradually: both sides coexist
Why integrate
The business reason, not just the tech
Your current stack keeps working
Everything your Segment source already feeds — warehouse, tools, alerts — now also receives resolved CDP events. Migration becomes a choice, not a prerequisite.
Identity on both sides
userId and anonymousId follow the graph: the person Segment knows is the same one who converted on the ad.
How to connect
Step by step
- Step 1
Create an HTTP API source in Segment and copy the write key.
- Step 2
Create the destination with the write key.
- Step 3
Create a Delivery with the events to forward.
Frequently asked questions
Does this lock me into Segment?
No — it is one more output. The same events remain available in every other destination and in platform queries.
Other integrations
RudderStack
Destination
Events to your RudderStack data plane, in track format.
View integration
mParticle
Destination
Server-side events into mParticle, grouped per person as the API requires.
View integration
AWS Firehose
Destination
Every event becomes a JSONL line in YOUR Firehose — data warehouse without a pipeline.
View integrationStart measuring what actually becomes revenue
Create a free account, connect your first source and see your first lead timeline today. No card required.