Feature
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.
A connection joins one source to one destination. The router turns each accepted event into one delivery job per enabled connection, so one event can reach a webhook, GA4, Mixpanel and S3 at the same time.
Each connection can be switched off, can pass only some event types or some track event names, and can remove fields such as properties.email or context.ip before delivery. A connection can also carry its own delivery rate limit.
More features
All features →- 01
Segment-style tracking API
One endpoint accepts the Segment-style HTTP tracking protocol, so existing analytics SDKs only need a new host.
- 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.