Start a project
Work eventabee Guides Connect Segment

Connect Segment

Send events to Segment as a source for further fan-out.

Updated

Operational

Segment is a customer data platform. Many merchants use eventabee as the ingest layer and Segment for downstream distribution. eventabee sends events via Segment’s HTTP API.

1. Create an HTTP API source

Segment → Connections → Sources → Add Source → HTTP API. Name it (e.g., “eventabee-server”). Copy the Write Key.

2. Paste into eventabee

Destinations → Segment → Connect. Paste the write key. Save.

3. Event shape

Segment accepts track, identify, page, and group calls. eventabee maps:

  • storefront page views → page calls
  • product interactions (view_item, add_to_cart, purchase) → track calls with the standard Segment e-commerce spec names
  • customer identification events → identify calls

Customize mapping in Destinations → Segment → Field mapping.

Segment → Personalization by default, since Segment is usually used for personalization/CDP purposes rather than direct advertising. Switch to Marketing if you use Segment as your advertising distribution hub.

Why use both eventabee and Segment?

  • eventabee owns the raw event capture, consent gating, and the direct ad platform CAPIs where match quality matters (Meta, Google, TikTok).
  • Segment owns the distribution to everything else — internal warehouses, reverse ETL, tools you want to evaluate without a direct integration.

Running them in parallel keeps match quality high (direct CAPIs) while preserving Segment’s distribution flexibility.

Troubleshooting

  • Events arrive but don’t map to Segment destinations. Each Segment destination has its own config; confirm it’s expecting your event names.
  • Rate limiting. Segment’s HTTP API has per-source limits. eventabee batches and retries automatically.