Segment (as a source)

Route your existing Segment pipeline into Hober: track calls become behavioral events, identify calls create or update subscribers. No re-instrumentation — if your product already sends events through Segment, flipping this on makes them available for segments, journey triggers, and personalization immediately. RudderStack webhook destinations send the same payload shape and work identically.

Setup

1. In Hober, open Settings → Integrations → Segment → Connect and set a shared secret (any strong random string — a password generator works).
2. In Segment, add a Webhooks (Actions) destination to your source with:
   • URL: https://api.hober.io/v1/integrations/segment/inbound/<your tenant id> (your tenant id is shown under Settings)
   • Auth: Basic — username = the shared secret, password empty
3. Enable the destination for track and identify calls.

Mapping

Segment	Hober
track event + properties	Behavioral event (same name), properties available as {{ event.* }}
messageId	Idempotency key — Segment retries never duplicate events
userId	Subscriber external_id
anonymousId	Anonymous actor (stitched on identify)
identify traits	Subscriber attributes; the email trait becomes the subscriber's email
page / screen / alias / group	Acknowledged and ignored

Order independence: a track that references a userId Hober hasn't seen yet auto-provisions the subscriber and retries — you don't need identify-before-track ordering.