topic Re: Real User Monitoring in Real User Monitoring

Action name changes (Real User Monitoring)

VFVCLIV — Wed, 11 Feb 2026 15:06:46 GMT

Good day, team.

I'm requesting your support with the following question we've encountered.

We're currently implementing web applications to monitor key actions within the site. We're in the "User action analysis" section, and we want to activate some "key user actions" for use within a dashboard that's being generated. However, the actions we need are linked to an ID, for example:

click on "-next-" on page /step1/step2/step3/12345678901

The idea is to only use the string: click on "-next-" on page /step1/step2/step3/, omitting the generated ID, since it's dynamic and many are generated daily, and marking each of these actions individually would be incorrect.

The question is:

Is it possible to merge this action so we only use the string mentioned, thus marking that action as a "key user action"?

Thank you in advance.

Greetings.

Re: Real User Monitoring

t_pawlak — Wed, 04 Feb 2026 16:44:01 GMT

Hi,
Yes — this can be done by normalizing the user action names using placeholders + naming rules. This way, all actions that differ only by a dynamic ID (for example .../step1/step2/step3/12345678901) will be grouped under one consistent action name, which you can then mark as a Key user action and use in dashboards.
I use Easytravel application as example:

For the “EasyTravel” application go to:
Application settings → Edit → Capturing → User actions and define two placeholders:

PathURL_no_parameters

Source: Page URL: Path

Purpose: filter/remove dynamic parts related to journeyId

XHR_URL_no_parameters

Source: Xhr URL

Purpose: filter/remove dynamic parts (match, journeyId) for XHR actions

Use regular expressions with the condition “replace with a regular expression”:

\?match[^;]*+ -?\d{8,11}

(Result: the URL is reduced to a stable form, without query parameters and without the dynamic ID.)

Naming rules (consistent action names)

Then, in User actions, add two naming rules:

For load actions:

Loading of page {PathURL_no_parameters}

For XHR actions:

{userInteraction (default)} on "{elementIdentifier (default)}" on page {XHR_URL_no_parameters}

ANd then Key user action

After these rules are applied and data comes in, you will see one unified action (without the dynamic ID) — and you can correctly mark it as a Key user action (instead of thousands of unique actions per day).

check also this documentation:
Pages and page groups

Re: Real User Monitoring

VFVCLIV — Thu, 05 Feb 2026 15:18:42 GMT

I understand, this helped me a lot, just one last question.

This action doesn't modify previous actions, only those generated after the placeholders are defined.

Is this correct?

Re: Real User Monitoring

AntonPineiro — Fri, 06 Feb 2026 15:15:09 GMT

Hi,

Correct, those configurations are normally from present to future, it does not change previous user actions monitored.

Best regards