Use page groups to isolate performance issues

Isolating issues where performance might be impacting your business is critical. Page groups give mPulse a way to identify, capture, and summarize the performance characteristics of pages that belong together logically. These groups let you see performance trends within segments of your site that may not affect the entire site.

For example, your Add-to-Cart is slow and the number of visitors going to Checkout has also decreased. Page groups let you see which pages affect page load time on your site and whether those pages are experiencing increased traffic.

How page groups work

In mPulse, a page group is a true/false rule using match criteria based on URL parameters. In other words, does this URL contain the query string parameters defined in the page group or not? Each page group is defined for a specific segment of your site. mPulse identifies page groups by their name in your data beacons. As mPulse receives beacons, it scans your data to find a match against the page group rule defined in your web app configuration. If a match is found, mPulse associates that page view for that URL with a page group name, and assigns the performance data for that content to the appropriate page group. Page group performance is then reported, and can be used as dimensions to filter mPulse data that’s displayed in the page group widgets.

How to define page groups

You define page groups in your web app configuration on the URLs tab. Consider how you think and talk about your site. Your home page might make up one page group named “Home,” your product detail page a second group, named “Products,” and a third, named “Cart.” Your search results and checkout pages may also have their own page groups.