Feature
Segment-style tracking API
One endpoint accepts the Segment-style HTTP tracking protocol, so existing analytics SDKs only need a new host.
Ingest accepts batches on /v1/b and /v1/batch, and single track, identify, page, screen, group and alias calls on their own routes. The write key can come as the Basic auth username, an x-write-key header or a writeKey field, and gzip request bodies are accepted.
Ingest answers only after the batch is durably appended, so a 200 means the events are safe. An event without a message id gets one, and every event is validated before it is accepted.
More features
All features →- 01
Fan-out with per-connection rules
Each source fans out to every destination it is connected to, with an event filter and dropped fields per connection.
- 02
Retries, dead letters and circuit breakers
Failed deliveries retry with backoff, permanent rejections stop at once, and a failing vendor trips a circuit breaker.
- 03
Dedupe of client retries
A client that retries the same event does not cause a second delivery: events are keyed by source and message id.