FAQ
Frequently asked questions
Short answers to the questions teams ask first.
Do I need a new SDK?
No. Pipeo accepts the Segment-style HTTP tracking protocol, so an SDK that speaks it, such as @segment/analytics-node or @segment/analytics-next, works once you change its hosts.
Which destinations are supported?
Webhook, Google Analytics 4, Mixpanel and an Amazon S3 file sink. There are no others yet.
When is an event safe?
When ingest answers 200. It answers only after the batch is durably stored, so an event it accepted is not lost if a process restarts.
What happens when a destination is down?
Deliveries retry with backoff for up to 25 attempts or 24 hours, and a circuit breaker pauses a destination that keeps failing. Jobs that run out become dead letters that can be requeued.
Will a retrying SDK cause duplicates?
No. A retry reuses the event’s message id, and Pipeo drops an event it already accepted for the same source and message id.
Can I keep personal data out of a tool?
Yes. Each connection can drop fields, such as properties.email or context.ip, before delivery, and can pass only the event types or track events you choose.
Can I send old events to a new destination?
Yes. Every accepted event is archived, and an operator can replay a time window to a destination, which is how a backfill works.
Is there a public API?
Not yet. The admin API serves the console only. Sending events uses the tracking endpoint and a source’s write key.
How much does it cost?
There is no billing yet. The plans page shows sample pricing only; use the contact form to ask about access.
Still stuck? Contact us.