Page Groups
Many websites are modular or built on templates (e.g. most eCommerce sites.) For such sites Catchpoint provides a feature called Page Groups, which enables you to group related pages and view their monitored data in aggregate. There are two methods you can use to associate tests with a Page Group: regular expressions and tag tokens.
-
By Regular Expression - Page groups may be defined using regular expressions to match a portion of the URL. For example, if all product pages contain
/products/in the path, you can configure a page group with a regex matching this substring, and Catchpoint will automatically associate data from all product pages with this page group. The regex is always checked against the path, filename, and query string. You can include the hostname by selecting the Regex include host name option. -
By Tag Token - A tag token is an arbitrary unique identifier that you define in the Page Group configuration, and add to each page in a corresponding tag. Tag tokens are supported by multiple different features in Catchpoint. You can find full details on tag token syntax below in the Tag Tokens section.
Each test is checked against your page groups in order from top to bottom until a match is found, and then no further page groups are checked. If two or more page groups use regular expressions that would match a given page, only the page group on top will take effect.
Variations
Some websites vary the content of the page delivered to users in order to test different versions of content or features. The Variations feature accommodates these scenarios by tracking data from all variations of a page together. Variations are determined using tag tokens (more detail below in the Tag Tokens section).
Insights
Catchpoint has the ability to collect custom metrics. There are two types of custom metrics: Indicators (numerical values) and Tracepoints (string values). For example, a common use for Indicators would be "Server Processing Time", and a common Tracepoint is "Server Name”. Insight functionality relies on the use of tag tokens, which are described in the Tag Tokens section.
Zones
Zones allow you to create custom groups of network requests made by websites to help understand the impact various content providers have on UX. For example you could have one zone that includes domains you control, and another that includes domains for CDNs that your system uses, enabling you to see how CDN performance compares to origin performance. Zones are defined using Regex which is applied to the domain name only.
Tag Tokens
A tag token is a unique identifier associated with a Page Group, Variation, Insight Indicator, or Insight Tracepoint. To create a tag token, enter a unique value in the tag token field under the feature you are configuring, and manually include the same value in a corresponding tag in the page source of each each page that you want to include.
- For Variations and Insights, the tag should come just after the tracking tag in the head.
- For Page Groups, the tag should be included with the code for that module. For example, a Page Group tag for product pages might be included in a file called products.php.
*Tag tokens must be lower-case and can be up to 30 characters. Tokens do not allow special characters such as hyphens.
Tag Syntax:
- Page Group:
RProfiler.addInfo('pageGroup', '<tag token>'); - Variation:
RProfiler.addInfo('variation', '<tag token>'); - Insight Indicator:
RProfiler.addInfo('indicator', '<tag token>', <indicator value>); - Insight Tracepoint:
RProfiler.addInfo('tracepoint', '<tag token>', ‘<tracepoint value>’);
Tag tokens are contained within <script> tags, as in the following example:
<script language="javascript" type="text/javascript">
RProfiler.addInfo('pageGroup', 'pg1');
</script>
To keep the browser from attempting to create tag tokens before the Catchpoint script is loaded, use the "GlimpseLoaded" event as follows:
<script language="javascript" type="text/javascript">
function init() {
window.RProfiler.addInfo('tracepoint', 'vt', ttoken);
}
window.RProfiler ? init() : window.addEventListener("GlimpseLoaded", init);
</script>