Tealium EventStream

If you already have a CDP, Signal can be its first-party collector. This integration forwards events from Signal into your existing Tealium EventStream so EventStream’s connector fan-out continues unchanged, while Signal replaces utag.js with a first-party server-side collector on your own domain.

Why route Tealium EventStream through Datafly Signal

• Profiles are updated from the server, not the browser. Events reach Tealium EventStream 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 Tealium EventStream needs to attribute the event to the right session.
• One consent decision governs every destination. Tealium EventStream is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

• A Tealium account with EventStream provisioned.
• Your Tealium account and profile names.
• An HTTP API data source configured in EventStream, and its data source key.

Get your credentials

Configure in Signal

Configuration fields

Management UI setup

1. Go to Integrations > Add Integration > Tealium EventStream.
2. Enter your tealium_account, tealium_profile, and tealium_datasource.
3. Select the General preset.
4. Choose consent categories (default: analytics).
5. 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": "tealium_eventstream",
    "name": "Tealium EventStream Production",
    "enabled": true,
    "config": {
      "tealium_account": "acme",
      "tealium_profile": "main",
      "tealium_datasource": "abc123"
    },
    "consent_categories": ["analytics"]
  }'

API endpoint

POST https://collect.tealiumiq.com/event
Content-Type: application/json

Authentication is by payload, not header: tealium_account, tealium_profile, and tealium_datasource are included in the JSON body and EventStream uses them to route the event to the correct data source.

Event mapping

Retail events use Tealium’s retail data layer names and variables; other events keep the Signal event name:

Every event carries tealium_visitor_id, customer_id, event_id, event_timestamp, ip_address, user_agent, page_url, page_title and referrer. Variables are flat: Tealium rejects a key containing a period. The General preset also forwards events it does not list, with the visitor, page and time variables; the Retail, Insurance, B2B / SaaS, Travel and Media & Streaming presets send the events of their event spec.

Identity

Signal generates a stable first-party anonymous_id and forwards it as tealium_visitor_id. When datafly.identify() is called, the same user_id arrives as customer_id on subsequent events — EventStream’s Visitor Stitching can join the two.

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.
• Segment (as destination) — same pattern for Segment.
• Migration Playbook — phased plan to put Signal in front of an existing CDP.