Segment (as destination)
Forward events to a Segment HTTP API source via /v1/batch. This integration is scoped explicitly as a migration tool: use it during the transition off Segment’s analytics.js browser SDK, so Signal’s collector can keep Segment’s activations running while you cut over vendor-by-vendor.
⚠️
Status: alpha. This is deliberately positioned as a migration destination. If you are on Segment today and plan to stay, use Segment’s own server-side libraries — Signal’s value is in replacing Segment, not in mirroring events to it indefinitely.
Prerequisites
- A Segment workspace with an HTTP API source.
- The source Write Key. Find it under Sources > your source > Settings > API Keys.
- (Optional) A regional endpoint if your Segment workspace is hosted in the EU.
Configuration fields
| Field | Required | Notes |
|---|---|---|
write_key | Yes | Segment HTTP API source write key. |
endpoint | No | https://api.segment.io/v1/batch (default) or EU equivalent. |
Migration posture
Signal and Segment can run in parallel during cut-over:
- Stand up Signal in your VPC (see Migration Playbook).
- Point analytics.js events at Signal as the primary; forward them to Segment via this destination.
- Migrate vendor destinations off Segment one by one, using Signal’s direct blueprints (GA4, Meta CAPI, TikTok, etc.).
- Once every vendor has moved, decommission this Segment destination. Total window: typically 4-8 weeks.