This article is an introduction to Tealium EventStream, a data collection and API hub that sits at the center of your data supply chain.
This guide introduces you to Tealium EventStream and helps you understand the application interface and the fundamental concepts of event data management. Step through this guide to learn how to quickly set up a working server-side profile that includes a data source, event specifications, and a vendor connector. You can then see it in action using live data from your site or application.
A data source is any system that sends data to Tealium EventStream. These systems include websites, native mobile apps, or any custom application that can report event data. Data sources are platform-specific and provide the necessary code and instructions to complete an installation.
This step will use the HTTP API data source as an example, but you can use any platform for which you have access to the code.
Installing and testing the HTTP API is as simple as entering a URL into a browser. If you chose a different platform for your data source go ahead and add the necessary code according to the installation instructions.
Live Events is used to manage and inspect incoming events in real-time. We’ll use this to verify that the test events you send from your data source are being received.
Event specifications are a way to organize and validate the quality of incoming data and they represent your data layer in EventStream. As mentioned earlier, events processed by EventStream are identified by the tealium_event attribute. The value of this attribute represents the name of the event and its associated specification. The specification also indicates which event attributes are required in the event.
tealium_event
Event specifications can be added directly from the event details view in Live Events. Live Events will detect events that match a marketplace specification and provide a preview of the spec to make it easy to add it without leaving the screen.
Now that you have event specifications defined, Live Events will display the quality of your incoming data. The color-coded bars in the chart are segmented according to the validation of the event specifications against your data.
Event feeds are a collection of events that match specific conditions based on their attributes.The default event feed is named “All Events” and contains all incoming events, but you will create additional feeds to identify subsets of events based on their attributes.
This step shows how to create an event feed to capture search events that contain zero results. However, these steps can be used to create any type of event feed.
This step shows how to add a connector, configure an action, and use data mappings.
Trace is the testing and validation tool for EventStream. You use Trace to validate that your configuration is working properly and that connector actions are being triggered.
In this step you will use Trace to validate that all of the previous configuration is working as expected. You will get a trace ID, add it to your application (or use the Tealium Tool), perform a simple test, then inspect the logs in the Trace interface.
Before we conclude this guide, it is important to understand how the save and publish process works and how to navigate your version history. This section will explain the difference between Save, Save as, and Publish and how to view your version history.
Now that you have a basic understanding of how Tealium EventStream works, you are ready to move on.