Read more about Data Workbench’s End-of-life announcement.
Latency table visualizations are tables that include a latency dimension, which is a type of derived dimension that measures the time that has elapsed since a particular event occurred.
You define the event by making selections within one or more visualizations and setting those selections as the event using the Set Event context menu option. Latency tables are especially useful for tracking activity related to a campaign or to a particular customer order in which you are looking for a time correlation.
In Site, latency tables provide information about the visitor sessions that occurred as many as seven days before or after the event, but you can configure latency tables to provide information about different countable and time dimensions. See Configuring Latency Tables.
Elements of the parent dimension, such as a session, which are part of the specific event that you selected, have a latency of zero. All other elements are assigned latencies that reflect the distance (in the appropriate time dimension) from the event.
The following example illustrates how you might use the latency table.
Identify value events in relation to a campaign
Let’s say you want to track the activity of customers during the seven days before and after they responded to a particular advertising campaign. To view the latency for a particular advertising campaign, you would set the campaign of interest as the event for the latency table.
Latency in the workspace below is based on selection of Campaign 11566 (the sessions in response to this campaign).
A latency of “+0 days” identifies the sessions in response to Campaign 11566, as well as all other sessions for those same customers that occurred on the same day.
A latency of “-2 days” identifies the sessions for those same customers that occurred two days before the customers responded to the campaign.
A latency of “+7 days” identifies the sessions for those same customers that occurred seven days after they responded to the campaign.
In addition to the procedures listed in the following sections, you can perform all of the same tasks that you can perform in a table, such as sort elements, mask elements, add a series legend, export data, and so on. For more information, see Tables.
To create a latency table, you begin by making a selection, then setting that selection as the event for which you want to track latency.
Right-click within a workspace and open the desired visualization(s), which must be based on the countable dimension used to configure your latency table.
For example, in Site the visualization(s) would need to be sessions-based.
Open a blank latency table.
Make a selection in your workspace.
Right-click within the latency table and click Set Event.
Events that you select do not persist unless you save the selections as a latency dimension. For steps, see Reusing a Latency Dimension.
If you want to use the same latency table again, you can save the latency table locally or if you have the proper permissions you can save it to the server for all users of a particular profile to access.
To save the latency table for use in other workspaces
To retrieve the saved latency table
If you want to use the same latency dimension again, you can save the latency dimension locally or if you have the proper permissions you can save it to the server for all users of a particular profile to access.
Any latency dimensions that you create are saved in the profile’s Dimensions directory and are available in the Change Dimension drop-down list within Data Workbench.
To save the latency dimension for use in other workspaces
To retrieve the saved latency dimension
For information about exporting windows, see Exporting Window Data.
For information about exporting windows, see Exporting Window Data.