By default, dimensions are evaluated immediately when the event occurs. Optionally, you can configure individual dimensions to be evaluated at the end of the session.
Goal Based Dimensions can be used only in cxOverstat report groups. You can mix delayed and non-delayed dimensions in the same cxOverstat report group. These report groups can be associated only with cxOverstat events.
Goal-based dimensions
By default, Tealeaf events and event-related objects, such as dimensions, are recorded as soon as they occur. This immediate responsiveness ensures that event activity and contextual data are captured as a snapshot of the current state of the session or application.
However, cxOverstat events are configured to publish their event data at the end of the session. The event values that were detected at the time the event fired are recorded, but the recording does not occur until the session is completed or times out.
For example, suppose you use a dimension to capture whether a purchase was made. Because that information is not known until the end of the session, you can delay the publishing of cxOverstat events and their related dimensions until the end of the session so the definitive answer (Yes or No) is captured in the dimension value.
A goal-based dimension event can fire multiple times in a session. An event that is configured to fire on the End of Session trigger occurs only one time at the end of the session. As a result, the End of Session event contains none of the context of the hit on which the goal-based dimension event occurred.
Note: All cxOverstat events are configured to have their data published at the end of the session. This setting cannot be modified for these events. Also, goal-based dimensions and events are not searchable and reportable until after the end of the session, if they are configured to be searchable and reportable in the event definition.
Enable goal-based dimensions
For each Processing Server, Goal Based Dimensions are enabled by default. When enabled, a Processing Server detects GBD settings on events and dimensions and publishes the data accordingly.
Goal Based Dimensions are enabled through the raw configuration of each Canister. All cxOverstat events are automatically configured for delayed publishing.
On individual dimensions that are part of cxOverstat report groups, you can configure them to be evaluated and published at the end of the session.
cxOverstat dimensions
To capture cxOverstat data for reporting purposes, Tealeaf provides a set of dimensions, which are used to store client usability data.
To locate these dimensions, enter Step in the filter text box in the Dimensions tab.
Dimension Name | Description | Source Event |
---|---|---|
Step - ScreenView | Records the latest Screenview for each Screenview LOAD message | Step - ScreenView [BB] |
Step - ScreenView URL | Records the latest URL for each Screenview LOAD message | Step - ScreenView URL [BB] |
Step - Target ID | ID of object that is acted on | Step - Usability Target ID + type [BB] |
Step - Target Relative XY | Records the relative position of the action that is based on the object that is acted on | Step - Target Relative XY |
Step - Usability Focal Slice Y | Records the Y focal slice.
Dimension includes a predefined whitelist of values for bucketing of slices for reporting. |
Step - Usability Focal Slice Y [BB] |
Step - Usability View Port Height | Viewport height of the browser window that explores usability overlays
Dimension includes a predefined whitelist of values for bucketing of slices for reporting. |
Step - Usability Attention Map Y View Time |
cxOverstat report groups
cxOverstat provides a set of report groups that contain the provided cxOverstat dimensions. These report groups are predefined to contain only the dimensions that are required for cxOverstat.
The following list displays the dimensions:
- Usability - Attention Map
- Usability - Click
- Usability - Form Analytics
Tealeaf recommends creating separate report groups for use with the cxOverstat system dimensions and then add dimensions as needed. These custom report groups can be added, modified, and removed as needed.
Note: After a dimension is added to any report group and committed to the database, it cannot be removed. Since you are not allowed to remove the default cxOverstat report groups from the cxOverstat events, any dimensions added to these report groups are retained permanently.
cxOverstat report group templates
For cxImpact, the base report group template is Standard
. This report group template supports up to four dimensions.
For cxOverstat, if you want to associate the usability data with other dimensions for cross-dimensional reporting, you can use report group templates as the basis for creating new report groups. A report group template is a template that contains preconfigured dimensions for a new report group when it is created. The report group template can be selected when you create a report group.
You can create duplicates of the custom report groups from these templates. You cannot make report group templates. Only report groups that are based on these associated templates are available for usability events.
The following report group templates are available to capture for cxOverstat:
A report group that is created from one of the cxOverstat report group templates can contain up to eight dimensions.
After you select a report group template, choosing a new report group template automatically removes all dimensions from the report group and starts with the included dimensions of the newly selected report group template.
Name | Description |
---|---|
Usability - Click |
Events operating on comparison analytics, heat map, or link analytics data require these contextual dimensions |
Usability - Attention Map |
Events operating on attention map data require these contextual dimensions |
Usability - Form Analytics |
Events operating on form analytics data require these contextual dimensions |