Analytics 10 Help, October 2013
Scenario Analysis parameters specify well-known paths or processes in your website and are typically used to measure conversion and abandonment.
In order to report on Scenario Analysis in Webtrends Analytics 9, you must also specify your Scenario Analysis definitions in Analytics 9 Administration.
Visitor Data Mart also recognizes these parameters. For more information, see the Webtrends Visitor Data Mart On Demand User's Guide on the Webtrends Documentation page.
Scenario Analysis definitions use the following attributes:
WT.si_n – Name of the Scenario Analysis
WT.si_p – Identifies the step by name
WT.si_x – Identifies the step by position
WT.si_cs – Identifies the step in which conversion occurs for Visitor Data Mart profiles.
You can configure multiple Scenario Analyses per page. However, you cannot count the same page as two different steps in the same scenario.
Because Scenario Analysis dimensions and measures are visit-based, they should only be used with visit-based dimensions and measures. If you create a custom report that uses Scenario Analysis dimensions with a hit-based dimension such as Page Views, the reported page view count includes all the page views of every visitor who saw one of the steps of the scenario, which inflates the actual page view count.For example, if WT.pn_sku, which is hit-based, is specified on the same page as the Product View scenario step, and you create a custom report using Product SKU as the dimension and four scenario steps as measures, the Product SKU shows a visit for each step of the Scenario, even though it was only specified on one of the steps
Identifies the name of the Scenario Analysis. When configuring a new Scenario Analysis definition using Analytics 9 Administration, make sure that the Scenario Analysis name matches this parameter value.
When specifying multiple Scenario Analysis names, you must also specify multiple step names or step numbers. Each step name or step number is associated with the scenario name having the same position in the list.
Multiple scenario names and steps are supported on one hit.
|Valid Value:||Alphanumeric strings (maximum length 64 bytes)|
Identifies the step by name. When configuring a new Scenario Analysis step using Analytics 9 Administration, the step name needs to match this parameter value.
|Valid Value:||Alphanumeric strings|
The numeric step position within the associated Scenario Analysis.
The value for WT.si_x must be an integer 1 or higher, and values must be sequential.
Do not use if specifying the step by name using the WT.si_p parameter.Also, for Visitor Data Mart only, to translate the position numbers displayed in Webtrends Explore into something more meaningful, create a Scenario Analysis Definition in Analytics 9 Administration. Ensure that you configure a step name for each step.
Identifies whether the page is the step in which conversion occurs when the value is 1. Most likely, this page is the last step in your Scenario.
In addition to this parameter, the web server must also pass the step query parameter for this page. Webtrends Analytics 9 recognizes either WT.si_p or WT.si_x for steps. Visitor Data Mart recognizes WT.si_x for steps.
Multiple values are supported. If multiple values are passed for this parameter and other Scenario event parameters, the Visitor Data Mart correlates the values.
Visitor Data Mart recognizes this parameter. However, this parameter is currently not included in any Webtrends Analytics preconfigured custom reports.
|Valid Value:||1 or 0|