Segment (as destination)

If you already have a CDP, Signal can be its first-party collector. This integration forwards events from Signal into your existing Segment workspace as an HTTP Source so Segment’s destination fan-out continues unchanged, while Signal replaces the browser SDK with a first-party server-side collector on your own domain.

Why route Segment (as destination) through Datafly Signal

• Profiles are updated from the server, not the browser. Events reach Segment (as destination) even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
• Client IP and user agent are carried in the payload. Both are taken from the original visitor request rather than your server, which is what Segment (as destination) needs to attribute the event to the right session.
• One consent decision governs every destination. Segment (as destination) is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

• A Segment workspace.
• An HTTP API Source configured in that workspace.
• The source write key.
• Knowledge of whether your workspace is in the US or EU region (this determines the endpoint).

Get your credentials

Configure in Signal

Configuration fields

Management UI setup

1. Go to Integrations > Add Integration > Segment (as destination).
2. Enter your write_key.
3. If your workspace is in the EU, override the endpoint to the EU URL.
4. Select the General preset.
5. Choose consent categories (default: analytics).
6. Save and enable.

Management API setup

curl -X POST https://api.example.com/v1/admin/integrations \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "source_id": "src_abc123",
    "vendor": "segment_destination",
    "name": "Segment Production",
    "enabled": true,
    "config": {
      "write_key": "your_write_key",
      "endpoint": "https://api.segment.io/v1"
    },
    "consent_categories": ["analytics"]
  }'

API endpoint

Each call type goes to its own path of the HTTP Tracking API, authenticated with HTTP Basic (write_key:):

POST {endpoint}/track      track events
POST {endpoint}/page       page views
POST {endpoint}/screen     mobile screen views (screen_view)
POST {endpoint}/identify   identify() calls
POST {endpoint}/group      group() calls

Every call carries userId or anonymousId, messageId (the Signal event ID, which Segment uses for deduplication) and timestamp; page and screen carry name, group carries groupId. Calls are limited to 32 KB each.

Presets

Retail: event names

Products map item_id to product_id and sku, item_name to name, item_category to category, item_brand to brand, item_variant to variant, index to position, with price, quantity and coupon unchanged.

Example: purchase with the Retail preset

Signal call:

datafly.track("purchase", {
  transaction_id: "ORD-001",
  value: 129.99,
  currency: "USD",
  items: [
    { item_id: "SKU-A", item_name: "Widget", price: 49.99, quantity: 2 }
  ]
});

Payload sent to {endpoint}/track:

{
  "event": "Order Completed",
  "anonymousId": "anon_a1b2c3",
  "userId": "user_42",
  "messageId": "evt_abc123",
  "timestamp": "2026-05-12T10:00:00.000Z",
  "context": {
    "ip": "203.0.113.50",
    "userAgent": "Mozilla/5.0 ...",
    "page": { "url": "https://example.com/checkout/confirmation" }
  },
  "properties": {
    "order_id": "ORD-001",
    "revenue": 129.99,
    "currency": "USD",
    "products": [
      { "product_id": "SKU-A", "sku": "SKU-A", "name": "Widget", "price": 49.99, "quantity": 2 }
    ]
  }
}

Identity

Signal generates a stable first-party anonymous_id and forwards it to Segment as anonymousId. When datafly.identify() is called, the same userId arrives at Segment on subsequent events.

identify() traits are sent as traits on the /identify call as the visitor supplied them, including email: Segment forwards identity to its own destinations and hashes per destination where a destination needs it. It is the only call that carries personal data; track and page calls carry no traits.

Consent

The default consent category for this integration is analytics. Events are only forwarded when the visitor has granted analytics consent.

Override the category list in the integration config if you need to gate delivery on a different category.

Verify

datafly.track("Test Event", { source: "signal-verify" });

Troubleshooting

See also

• RudderStack — same pattern for RudderStack.
• Tealium EventStream — same pattern for Tealium.
• Migration Playbook — phased plan to put Signal in front of an existing CDP.