First-party events from every website, app and server, straight into your warehouse.
Collect events from your websites, apps and servers on your own endpoint, check them against schemas you version, and land every one in your workspace's warehouse with nothing to host. Keep the tracker you run today or write your own, and send data onward with destinations in code.
An event stream as its events/ folder declares it: the origins it accepts, batching, and the endpoint your tracker sends to.
Streams declared in code
Each stream is a few lines in events/events.py: its key, how senders authenticate and the shape of its events. It deploys with the rest of the workspace, and the console shows its volume and schema history.
From websites, apps and servers
Servers send with a write key. Websites send from the origins you allow, with no key in the page. A hybrid stream takes both, in batches of up to 100 events per request.
Keep the tracker you run
Segment, RudderStack and GA4 trackers change one setting, the address they send to, and every call lands in your workspace. Or use our open-source web tracker, or a few lines your agent writes.
Schemas that never drop data
Versioned schemas check every event. An event that does not match is kept and flagged, never thrown away, so a tracking bug costs a fix, not a gap in the data.
Straight into your warehouse
Accepted events land in a date-partitioned table in your workspace's warehouse, in its region, with a view per event type. Pipelines model them into sessions, conversions and attribution.
Destinations in code
Send rows and records onward to ad platforms, CRMs and messaging tools through a workspace connection: a pipeline step for batches, an action or workflow for a single business event.
Collection run for you
Collectors are run for you, with nothing to host or scale. Pause or resume a stream, rotate its key or run an end-to-end check from the CLI.
In code
# events/events.pyfrom segmentstream.events import Stream, auth, protocolstreams = ( Stream( key="web", auth=(auth.WriteKey(), auth.Origin(("https://www.example.com",))), protocol=protocol.Json(batch=True), ),)# After segmentstream deploy, any server sends a batch with its write key:$ curl https://collect.segmentstream.com/v1/e/WORKSPACE_ID/web \ -H "Authorization: Bearer $WRITE_KEY" \ -H "Content-Type: application/json" \ -d '{"batch": [{"event_id": "4f1c…", "event_type": "purchase", "event_time": "2026-11-12T09:30:00Z", "schema_version": 1, "payload": {"order_id": "1042", "value": 129.0}}]}'# Check delivery end to end, then read the stream's capture table:$ segmentstream events verify web$ segmentstream events get webUse it, build on it, or have it built
Use it
Declare a stream, deploy, and send events to its endpoint. Volume and schema history are in the console.
Build it with your agent
Your agent declares a stream in events/, writes the tracker or changes one setting in the one you run, and models the events in pipeline/.
Have our engineers build it
Our engineers move your tracking off Segment, RudderStack or GA4 with you, and prove the numbers match before anything is switched off.
Replaces Segment, RudderStack, A Snowplow pipeline you run yourself and Server-side tracking you host.
Works with
Solutions built with it
Read more
- 3 October 2026AI agents can build your BI. Here's why they get the numbers wrong.Benchmarks keep finding that agents writing SQL against raw tables give confident wrong answers, while the same agents answering through a semantic layer get nearly everything right. What that means for how you build analytics now.
- 2 October 2026How to leave GA4 without losing a single reportYou don't have to rip out gtag to own your web analytics. Change where it sends, keep GA4 running while you rebuild, and switch only when the numbers match.
- 30 September 2026The future of ad traffic verification with SegmentStream and JevAd traffic verification is still sold as a black box for $60–100k a year. The next generation runs next to your conversions, is checked against real outcomes, and is decided by a model built for decisions.
Start a pilot.
Want events set up for you? Our forward-deployed engineers build it with you in your workspace, as code you own.
- One solution, on your data, in your own workspace
- First version live in two weeks
- Parity proven before anything is switched off
- Fixed scope and price, credited to your contract if you continue
Not ready for a pilot? Send the form anyway with your question. An engineer will reply, not a sales rep.
How the pilot worksBuild your company’s own software. Let agents run it.
$ segmentstream workspace create acme --region eu --subdomain acme
▸ Created workspace acme · database, warehouse and a private git repository
$ segmentstream workspace WORKSPACE-ID clone acme && cd acme
▸ your coding agent builds what your team asked for and runs the checks
$ git add -A && git commit -m "First version"
$ segmentstream deploy
▸ app, company agent, API and MCP tools live for your invited members
Our engineers build the first version on your data in two weeks, at a fixed price.
Or build it yourself with your coding agent:
curl -fsSL https://segmentstream.com/install.sh | sh