These parameters are used by several Webtrends products.
Query Parameter Syntax
Webtrends query parameters follow specific syntax that includes name, value, and format. The following sections describe each of these syntax elements.
The name of each Webtrends query parameter uses the following syntax:
In addition to the query parameters covered in this chapter, the following name spaces are reserved for Webtrends:
Used for product integrations with Webtrends partners.
Used by Webtrends Professional Services for customer integrations.
As a best practice, use the following syntax to create custom query parameters:
For example, you could create a parameter called DCSext.w_articleid to track an article ID.
The values associated with Webtrends query parameters use the following syntax.
Each Webtrends query parameter name may have one or more values. Some parameters can be specified in pairs or in groups of related parameters. When related parameters have multiple values, these values may be correlated and their position becomes important as shown in the following example:
In the previous example, if correlation is specified in the report, name1 is associated with position1 and name2 with position2.
If there are multiple values, they are typically separated using a semicolon (;). You can use other separators, but you must specify the separator in the dimension or measure setting that is based on the parameter.
If the parameter value contains a semicolon, it must be hex-encoded (“%3B”) to differentiate it from the separator.
Numerical Value Format
Unless stated otherwise, numerical values must be specified using the simple US format using the period as the decimal separator with up to 2 decimals and without thousand separators. For example, 12345.67.
The Webtrends query parameters are represented as name/value pairs. The name/value pairs adhere to the following syntax:
The Webtrends query parameters are logged in SmartSource Data Collector log files. Each name/value pair is separated by an ampersand (&).
The Webtrends query parameters must co-exist with other website well-known parameters. This means that Webtrends query parameters can be mixed with standard well-known parameters using the ampersand delimiter. While a Webtrends namespace is part of each query parameter, it is conceivable that parameter collisions may occur. If a query parameter string contains duplicate key values, the first instance is used and the others are discarded.
- Single Parameter With a Single Value
- The following example shows a page associated with the “Finance Offer” advertising view:
- Single Parameter With Multiple Values
- The following example shows a page associated with both the “Finance Offer” and “FishFinder Offer” advertising views:
- Related Parameters With a Single Value
- The following example shows a page associated with the Campaign “New Product” and the Campaign Event Type “click.”
- Related Parameters With Multiple Values
- The following example shows a page associated with content groups and sub-types. The sub-type pressreleases is associated with the corporate content group, while the sub-type specifications is associated with the engineering content group.
- Auto-Configuration Parameters
Webtrends uses certain query parameters to automatically configure the appropriate advanced features and create related reports.
- Custom Report Parameters
This section discusses parameters that are included in a series of preconfigured custom reports.
- Stored Visitor Parameter
The Stored Visitor parameter identifies the unique visitor ID you assign to your visitors.
- SDC-Generated Visitor Parameters
Some visitor-related parameters that are generated and maintained by SmartSource Data Collector (SDC).
- SDC-Parameter Override Parameters
Use these parameters to override SDC parameters on the client side.
- Conversion Plug-In Parameters
The Webtrends encoding conversion plug-in uses the parameters in this section during the character encoding conversion process.
- Mobile Web and Mobile Application Parameters
These parameters are used with the Webtrends Client Libraries for Mobile Applications to track both web and application activity associated with mobile devices.