Segment destination brief
Planned Segment destination scope and the server-side event forwarding path available today.
Segment support is available today by forwarding trusted server-side events to Perkamo. A native Segment destination is planned when customer event catalogs show a repeatable mapping.
Planned native scope
- Receive selected Segment track calls as Perkamo events.
- Map Segment user ids to Perkamo customer ids.
- Preserve deterministic transaction ids for retries.
- Allow customers to choose which event names are forwarded.
- Provide setup guidance for server-side sources first.
Browser-only analytics events should not become authoritative points or reward actions unless they are verified by the customer's backend.
Available now
Forward server-side Segment events to Perkamo from a destination function, warehouse job or backend service.
- Send mapped events with POST /v1/events.
- Use Concepts for event naming and idempotency.
- Validate the first mapped event with the Quickstart.
- Read Security and keys before storing server keys.
Design partner fit
This connector is a good fit when Segment already collects production events and Perkamo should become the rules layer for selected trusted actions. Perkamo can help customers audit the event catalog and choose the first reliable mapping.