- TLC Home Home
- Discussions & Ideas Discussions & Ideas
- Product Guides Product Guides
- Knowledge Base Knowledge Base
- Developer Docs Developer Docs
- Education Education
- Blog TLC Blog
- Support Desk Support Desk
Event specifications are a way to organize and validate the quality of incoming data. Specifications define the attributes required for types of events and provide code examples for your installation. Once created, specifications allow the data quality of your events to be validated in real-time using Live Events.
This article covers the following topics:
Event specifications represent your data layer in the Customer Data Hub . Events entering the Customer Data Hub are identified by the tealium_event
attribute. The value of this attribute represents the name of the event and the specification associated with it. The specification also indicates which event attributes are required to be populated in the event.
Let's look at an example of an event specification for the event named video_complete
which occurs upon the completion of watching a video.
{ "tealium_event" : "video_complete", // name of event and specification "video_id" : "xWlEk2i9r5Q", "video_length" : 300, "video_name" : "How to track videos in Tealium", "video_platform" : "YouTube", }The
tealium_event
attribute identifies the type of event, in this case video_complete
. The additional attributes provide contextual information about the event and the corresponding event specification defines the required attributes and their expected data types, as shown in the following example.cart_add
event for an iQ Tag Management data source named "My iOS App"Each event specification automatically creates a matching event feed. This feed can be configured for data storage via DataAccess, or linked to connector actions.
Feeds linked to an event specification cannot be deleted and their names cannot be changed.
Example:
Once an event specification is created and the tracking code is implemented, use Live Events to view incoming events in real-time to evaluate their data quality. As events arrive in the Customer Data Hub, when the tealium_event
attribute matches an event specification, the incoming attributes are compared against the requirements of the specification and marked as valid or invalid.
cart_empty
eventcart_empty
event due to lack of matching event specificationThe following sections describe the steps required to add custom event specifications or add events from the event specification marketplace or live events.
Event specifications can be added as custom events or added from the marketplace of built-in events. Custom events can use any event name and any attribute requirements.
Custom specifications use a tealium_event
value that you determine.
Once you create a custom event specification, the name of the event cannot be changed.
Use the following steps to add a custom event specification:
tealium_event
).gallery_view
.The event specification marketplace contains commonly used pre-built events. Once an event is added, the only change that can be made to a marketplace specification is the addition of attributes to the definition.
When adding an event specification from the marketplace, the original event name and attribute list cannot be changed.
Use the following steps to add a marketplace specification:
Event specifications can be added directly from the event details view of Live Events. Live events detect events that match a marketplace specification and provide a preview of the requirements to make it easy to add the specification without leaving the screen.
Events that are unknown can be defined as custom specifications directly from the event details view. The event attributes from the event will be pre-filled in the Add Event Specification modal.
Learn more about using Live Events.
For users of iQ Tag Management, use the Tealium Events extension to populate the tealium_event
variable to match your event specifications.
Creating event specifications is the first step in defining and standardizing your data layer. The second step is implementing the event tracking code on your platform of choice. While each platform has different code syntax, the event and attribute names implemented should be consistent across each of them.
Event specifications combine the event definitions with each of your data sources to provide a full installation guide, complete with the base code and examples for each specification. The resulting installation guide can be downloaded as a PDF and shared with your development team.
Use the following steps to get the code for your event specifications:
Copyright All Rights Reserved © 2008-2021