Path segment rules

Real User Monitoring receives URL paths for each page that your users visit on your site. Due to the common use of REST routes and other schemes, it is common for duplicate pages to be created by default when they are the same view.

Path segment rules are a way to group these duplicate URLs together using wildcards.

Example: A common web forum will have mulitple URLs. One being http://foo.com/thread/1 and another like http://foo.com/thread/2. These two urls can show up as two seperate Pages inside Real User Monitoring when really they are two instances of the same thread.

note: Page URLs cannot be changed once they have been ingested.


Default behaviour

Real User Monitoring by default will replace both integer path segments and DateTime strings with the wildcard character *. Meaning the following urls would be grouped as http://foo.com/thread/*

  • http://foo.com/thread/10
  • http://foo.com/thread/28
  • http://foo.com/thread/34

Customising rules

Under each Application’s Real User Monitoring Settings page you can add new rules or remove any rules which are no longer required.

note: Rule changes can take up to 10 minutes to be reflected by new pages sent to RUM.


Grouping rules

Grouping rules enable you to add your own path segment wildwards (the * symbol) to match your routing scheme. You can have as many grouping rules as you need.

Grouping rules UI

tip: Rules are saved whenever the 'Add URL' or the delete button is clicked.

Examples:

A grouping rule of https://foo.com/forum/* group any of the following page visits:

  • /forum/foo
  • /forum/bar
  • /forum/foo/bar

A more specific rule of https://foo.com/forum/*/delete will group any of the following:

  • /forum/foo/delete
  • /forum/bar/delete
Execution order

Pages are tested against rules which are at the top of the list first. The first rule which matches a given page is applied.

Meaning in the last example, if the previous rule https://foo.com/forum/* was added before https://foo.com/forum/*/delete all pages would have appeared under /forum/* instead of forum/*/delete.


Ungrouping rules

Ungrouping rules allow you to prevent pages from being grouped. These rules will also disable the default integer and datetime wildcarding as well.

Ungrouping rules RUM UI

Single URLs

Specific routes which you want to appear unwildcarded can be added. For example adding the following ungrouping rules will result in those pages appearing separately in RUM:

  • http://foo.com/thread/1
  • http://foo.com/thread/2

Whilst a visit to http://foo.com/thread/3 would show up under /thread/*.

Wildcarding URLs

Wildcards can also be applied to ungrouping rules allowing you to mass-ungroup pages. For example a rule of http://foo.com/thread/* will means the following pages would appear individually in RUM:

  • /thread/1
  • /thread/2

Subdomains

Subdomains can also be grouped or ungrouped in the same way as the segments above.

Example:

A rule of https://*.foo.com would group all of the following subdomains:

  • https://subdomain.foo.com
  • https://example.foo.com

Whilst visits to the following pages would appear as https://*.foo.com/bar:

  • https://subdomain.foo.com/bar
  • https://example.foo.com/bar

Mixing ungrouping with grouping

Ungrouping rules coexist alongside grouping rules. Ungrouping rules take precedence over (AKA override) any grouping rules. For example take the following combination:

  • The ungrouping rule: https://www.example.com/route/*
  • The grouping rule: https://www.example.com/route/*/*

Will cause the following two pages to appear as https://www.example.com/route/1/* in RUM:

  • https://www.example.com/route/1/ff000
  • https://www.example.com/route/1/ee00ff