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.
How it works
Feeds allow you to identify your most important types of events and take action on them by sending them to vendor connectors.
Here’s how it works:
- Feed Name
An event feed has a name that identifies it throughout the UI, such as when configuring a connector action. Choose a user-friendly name that will make sense to you and your team.
Purchases with Order Total Over $1,000
Each feed requires one or more conditions that filters it out of the All Events feeds. Use the values of your event attributes (data layer) to construct simple rules that identify a certain type of event.
tealium_event EQUALS "purchase" AND order_total IS GREATER THAN 1000
- View in Live Events
Once feeds are created, you can adjust Live Events to only display events from a specific feed. This is helpful for debugging, creating new event specifications, or just monitoring the health of your feeds.
- Use in Connectors
Once an event feed is created, you can use it in a connector to send data to a vendor. This is the API hub in action!
Here is an example of an event feed that identifies
search events that had
0 results. This feed could be used to monitor the health of your search engine and/or help to improve your search capabilities.
Notice that the feed contains two conditions:
tealium_event EQUALS "search"
search_results EQUALS 0
Example event feed: Search with No Results
Click Next to see how to add an event feed.
Thank you for your feedback!
This page was last updated: January 7, 2023