Integrations / Customer Data Platform
Tealium EventStream
Forward first-party events to Tealium EventStream's HTTP API. If you already have Tealium, Signal can be its first-party collector — Signal handles upstream collection on your own domain, EventStream handles fan-out to downstream connectors.
Datafly Signal delivers first-party events to Tealium EventStream server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Tealium EventStream expects.
Why route Tealium EventStream through Datafly Signal
Profiles update 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.
What ships in the blueprint
Mapped events
identifypagepurchaseVertical presets
General. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Tealium EventStream documentation.
Frequently asked questions
Does Datafly Signal integrate with Tealium EventStream?
Yes. Datafly Signal delivers first-party events to Tealium EventStream server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Tealium EventStream expects. The integration is included in every deployment at no additional cost.
How is server-side Tealium EventStream tracking different from the Tealium EventStream tag?
The Tealium EventStream tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Tealium EventStream from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Tealium EventStream?
The blueprint ships with mappings for identify, page, purchase. Any event in your schema can be mapped to Tealium EventStream through pipeline configuration without a code change.
Do I need to keep the Tealium EventStream tag on my site?
No. Signal delivers to Tealium EventStream from the server, so no client-side Tealium EventStream script is required on your site.
Other customer data platform integrations
Ready to move Tealium EventStream server-side?
See how Datafly Signal delivers first-party events to Tealium EventStream from infrastructure you control, with hashed identity and consent enforcement built in.