RudderStack
Forward events to a RudderStack data plane via the Segment-compatible /v1/batch HTTP API. Typical use case: hybrid migration where Signal and RudderStack run in parallel during the transition off a client-side SDK.
⚠️
Status: alpha. Shipped as a scaffolded catalog entry. Event field mappings from Signal’s collector to RudderStack’s track / page / identify / group payloads are configured per pipeline in the current release; a full preset is planned.
Prerequisites
- A RudderStack workspace and an HTTP source configured.
- The Data Plane URL for your workspace (e.g.
https://<id>.dataplane.rudderstack.com). Find it under Sources > your source > Setup Instructions. - The Write Key for the source (kept secret).
Configuration fields
| Field | Required | Notes |
|---|---|---|
data_plane_url | Yes | Your RudderStack data plane URL. |
write_key | Yes | Source write key. |
Endpoint
Events are delivered to:
POST {data_plane_url}/v1/batch
Authorization: Basic {base64(write_key:)}The payload shape is Segment-spec-compatible: { batch: [ { type, event, properties, context, ... }, ... ] }.
Next steps
- Use this integration during migration from RudderStack’s client SDK, not as a long-term parallel architecture.
- For full migration, see the Migration Playbook.