Complex web sites are often built with a few templates, each of which have their own performance characteristics. Each template may be rendered with different content, and accessed using different URLs, but from a performance point of view, they look the same.
mPulse Page Groups help you capture and summarize the performance characteristics of groups of pages that belong together. Your home page may make up one group, while your login page may make up a second, and product pages a third such group. Your search results and checkout pages may also have their own groups.
Page Groups are used in the Page Groups widget (shown below)
In all cases when using Query String Parameter matching (whether for Page Groups, Timers & Metrics), a final filter is run on the result that will strip out any invalid characters for that type. So for Page Groups, mPulse strips out any characters that are non-alphabetic, underscore, dash or space. While for Custom Timers & Metrics, mPulse strips out anything that is not a number, a decimal point or a negative sign.
Page Groups using Query String Parameter utilize a priority system, in which first page group that gets a match is the page group that gets used for a given page or view. You specify a Query String Parameter using * as a wildcard anywhere in the pattern. You can also specify a query string parameter. We will use the value of this query string parameter as the page group.
All of the steps below are performed by the mPulse user with Domain Administration rights.
There are two restrictions on the page group name:
mPulse uses regular expression (below) to validate a page group, and you may use the same to verify your own code:
With the query string type Query String Parameter definition method, mPulse looks for the first matching query string parameter from the page that has an URL Pattern match.
The URL used here must have a query string (e.g., a "?" that precedes the non-hierarchical data that follows).
The query string parameter name used (under Parameter 2) must actually be part of the test URL.
For example, if Parameter 1 is:
And Parameter 2 is:
Entering the test URL :
Will result in a match of
If the match is successful, the Result field is populated with the resulting match.
This definition method strips out the specified substring from the start of the text and then uses whatever is left.
For example, if
*.google.com* is used, then the page group definition will consist of any text that comes after the
This definition method strips out the leading and trailing parts of the URL and uses the remainder.
Within the substring pattern, mPulse looks for any URL that matches the leading pattern + something + the trailing pattern, and then uses that "something". The Query String Parameter with no trailing part is identical to this except trailing is an empty string.
For example, if URL Start is *.google.com/=search?vinyl* and Trailing Text continues with "&oq..." , then for the test URL the portion between is parsed as
This definition method matches the URL to a regular expression and then uses the value of the replaced field.
© 2015 SOASTA. All Rights Reserved. Privacy & Legal