What the API Hub actually does
EventStream API Hub is a server-side ingestion endpoint: events are posted to it directly via API, bypassing a client-side tag entirely. It is the foundation for server-to-server tracking, a mobile SDK relaying events through a backend, or any integration that needs to post events straight into Tealium's collection layer.
When you need it over client-side collection
- Server-side tagging initiatives where reliability cannot depend on a browser executing JavaScript
- Mobile apps sending events through a backend relay rather than a client SDK directly
- Any source needing delivery independent of ad blockers, Intelligent Tracking Prevention, or an in-app webview that limits client-side collection
How to implement it properly
Provision the API Hub source and define the event schema it will accept before any code is written against it - a schema decided during integration, rather than before, invites drift. Authenticate the sending system per the Hub's requirement. Route connector destinations that should consume incoming events, deliberately, rather than defaulting to "send everywhere." Then install and test before production volume - this step is not optional.
How to verify it worked
Send a real test event through the actual sending system (not a generic API client standing in for it), confirm it appears in the source's trace with the fields intact, and confirm at least one downstream connector actually receives it. A Hub that accepts a test call but whose connectors were never re-verified after a later change is a common, quiet failure point.
How this differs from the general EventStream service: the API Hub specifically is the direct-API ingestion path. See the EventStream service page for the fuller server-side collection picture, including specification and connector routing beyond just the ingestion endpoint.