A timed event measures the duration of an event or the time between two events and is set with automatic or manual triggers. When a timed event is complete it sends an event named timed_event to Tealium EventStream with the name of the timed event and the timing details.
Use automatic triggers to measure the duration between Tealium events that are already tracked in your app. A timed event is triggered automatically when the specified start event occurs and stops when the specified stop event occurs.
Use manual triggers to measure the duration between events that are not tracked by Tealium or that involve a complex sequence of events. A timed event is triggered manually by starting and stopping the timed event in the app code based on your custom logic.
Each timed event has a name that is set to the event attribute timed_event_name. An event name may be reused after the timed event has ended, but multiple concurrent timed events may not use the same name.
Timed events are not persistent and are discarded if the app terminates before the event ends.
To track a timed event with an automatic trigger, specify the start and stop Tealium event names. These events must already be tracked in your app. The name of an automatic timed event is generated by joining the start and stop event names with two colons (::). For example, when you set an automatic trigger to track the duration between the cart_add event and the purchase event, the event attribute timed_event_name is set to cart_add::purchase.
To track a timed event with a manual trigger, specify a name for the timed event then start and stop the timed event manually in your app code. For example, to manually track the time a user spends viewing a product, start the timed event when the product screen is loaded, then stop the timed event when the user leaves the product screen. The name you use for the timed event is set to the value of the event attribute timed_event_name.