In the More Options step, you can configure the availability of the event occurrence and values in the Portal, replay, and to third-party consumers of the data through the Event Bus.

Note: The Event Bus is a component of cxConnect for Data Analysis, a separately licensed component of the Tealeaf CX platform. For more information, contact your Acoustic representative.

Update session timeout

You may optionally configure the event to change the session timeout setting for this specific session. When a new value is entered for the session timeout, the Canister waits until the specified number of minutes elapsed without extra activity before timing out the session and closing it. Other actions, such as the visitor terminating the session through the web application, may also force the session to close.

• To change the session timeout, click the Update Session Timeout check box. Enter a value in minutes to set the new session timeout for the session. When changes are saved, all subsequent sessions in which the event is triggered are automatically updated with the new session timeout.
• By default, the Canister automatically closes sessions that were not augmented for a specified number of seconds. The changes that you make for the specific event override the configured session timeout value for the Canister.

Minute-level event counts

When Minute Data On is enabled for an event, the Alert Service is used to record minute-level event counts for reporting purposes. You can use this event data to track event activities up to the most recent minute, which is useful for highly sensitive or important metrics.

• The Alert Service is a component that is configured to capture event information every minute.
• Data is retained by the Alert Service for the preceding 24-hour rolling period.

  Note: Minute-level tabulation of event counts requires that the Alert Service is enabled and at least one alert is configured and active.
  If the Alert Service is stopped or restarted, the available minute data from the previous 24 hours is lost. When the Alert Service is restarted, it immediately begins acquiring minute-level event counts.

Events with minute-level data can be used as sources for Live Event dashboard components. This option is functional only if the event is configured to be Searchable & Reportable.

Note: This option should be enabled only for events for which you want to create minute-level dashboard components.

Close session

Sessions are often closed based on a specific URL or a string in the response, such as Order Confirmation. When the event fires, the session fragment is closed, and the other session events are evaluated, after which the session is marked for long-term storage or removal.

A session close event is designed to artificially terminate a visitor's session fragment. These events are useful in two scenarios:

• If the visitors to your website perform the same business transaction multiple times in a single user session, you may desire to have the business transaction tabulated one time only as a session event.
• If your web application is supporting a group of customer service representatives who are constantly repeating the same business transaction on behalf of a phone customer, then you may desire to have the business transaction that is counted once per RTV user session.

When these instances occur, the session should be forced to close, and a new session fragment should be initiated. Any additional hits that are associated with the session ID for this session are added to the new session and assigned the new internal session index identifier. No session data from the original session is preserved.

Clone and close session

When configuring a session to close, you can optionally choose to clone the session attributes that were accumulated in the original session. If extra hits arrive carrying the same session ID as the original session, then a new session is created, and the session attributes values from the original session are added to it, as well as the new hits. The new session is assigned a new internal session index identifier.

Discard session

When a session is marked for discard by an event, the session is deleted when the session closes. Since the session is not archived for storage, it is not indexed for search and is not retrievable.

• Pages in discarded sessions are not counted. Pages are counted as a session-end event, and all event processing in the session stops when the discard action is executed.
• Hits arriving subsequent to the discard session event action are not evaluated for events.

  Note: Any events that were triggered before the session is discarded are retained in the reporting database. Test sessions for discarding in the first hit of the session.

• Session discard events can be configured to be reportable, but you cannot search for or drill-down into these events.
• If the discard session event is configured to fire on the last hit, the session is counted as a session for reporting purposes by default, even though the pages are not counted. To prevent the session being counted, you must either:
  1. Move the discard session event to fire on an earlier trigger
  2. Add the Session Count event as a condition for the firing of the event in which the session is discarded.

If you licensed cxReveal, setting a session to be discarded automatically forces the event to be sent to the Event Bus. cxReveal database search requires updating when sessions were discarded, so this configuration is required.

Note: In Advanced Mode, the TLDiscardSession(); function call discards the session. However, you must manually configure to send the session to the Event Bus through the More Options step.