Integrations
Hober connects to the tools your team already uses, in both directions:
| Integration | Direction | What it does |
|---|---|---|
| Segment | in | track/identify calls from your existing pipeline become Hober events and subscriber attributes |
| Shopify | in | Orders and checkouts become events for abandoned-cart and lifecycle journeys |
| Mixpanel | out | Message engagement and behavioral events forwarded to your Mixpanel project |
| Amplitude | out | The same event stream, delivered to Amplitude |
| Slack | out | Campaign summaries in your team's Slack workspace |
| Zapier | both | Triggers and actions connecting Hober to 7,000+ apps |
| Hightouch | in | Warehouse audiences and traits synced as subscribers via reverse-ETL |
| Census | in | The same reverse-ETL path, from Census |
Connect any of them under Settings → Integrations in the dashboard. Credentials are write-only: they are envelope-encrypted at rest and never shown again after you save them.
Two behaviors hold across every integration:
- Inbound events are first-class. Anything Segment or Shopify sends lands in the same event store as your SDK and server-key events — usable in segments, journey triggers, wait-for-event steps, and Liquid personalization (
{{ event.* }}). - Outbound delivery is best-effort. A provider outage never blocks or delays your messaging pipeline; forwarding failures are logged and counted, and Hober remains the system of record.