How it works

Follow one event from your SDK to every destination it is meant for.

Step 1
Your SDK sends a batch
The SDK posts a batch of events with the source’s write key. It reads its client settings from the Pipeo CDN.
Step 2
Ingest stores it
Ingest checks the key, validates every event, applies rate limits and appends the batch durably before it answers 200.
Step 3
The router fans it out
Duplicates of events already accepted are dropped. Each remaining event becomes one delivery job per enabled connection, after that connection’s filter and field removal.
Step 4
Workers deliver
A worker calls the destination’s adapter: a webhook (optionally HMAC-signed), the GA4 Measurement Protocol, the Mixpanel API or a gzipped NDJSON file in S3.
Step 5
Failures retry
Retryable failures back off and try again; a vendor that keeps failing trips its circuit breaker. Jobs that run out of attempts become dead letters for the operator to requeue.
Step 6
The archive keeps a copy
Every accepted event is archived, so a time window can be replayed to a destination, or backfilled into a new one.

Send once, deliver everywhere