Browser Monitors: Automatically assigned applications

HannahM — Mon, 20 Oct 2025 15:33:14 GMT

Summary

Dynatrace Synthetic Browser Monitors can be manually or automatically assigned to a RUM Application. In some cases, automatic assignment does not occur as expected

What is Application auto-assignment?

When a Browser Monitor is executed on a page that has RUM injection, the Dynatrace Synthetic Player sees the RUM injection and applies the Application configuration to the Browser Monitor. The benefit of this, over manual assignment, is that, as well as being able to show the Availability in the RUM application, the Browser Monitor sessions will be seen in the Application as made by a Synthetic user, and you can then analyze them using Session Segmentation, and you can see any related traces.

Session Segmentation

Link from a user action in a user session to a Browser Monitor execution

Clicking on Perform Waterfall Analysis for an action in a Session will take you to the step in the relevant execution in Synthetic Monitoring

Link from a Browser Monitor execution to a user action

The link also works in reverse. Browser Monitor executions link to the relevant User Action in the RUM Application. Clicking on the user action link, a clickable URL in blue, will open the relevant User Action details page.

Link to traces from a Browser Monitor

To view traces from a Browser Monitor, open an execution and click on the relevant event. Scroll down to the 'Detailed breakdown' section and click on the Traces tile, as shown here

Troubleshooting

Where a Browser monitor is not showing as automatically assigned to a RUM Application, the following steps can be used to find and resolve the cause.

Confirm that the page that is being injected is visited by the Browser Monitor.
Dynatrace Synthetic monitoring will only be able to pick up Application details if the pages it visits are injected with RUM.
Confirm that the jsAgent script tag is the first script node on the page.
This is only a requirement for Synthetic, so RUM injection would still work for Real users even when this is not the case.
1. For auto-injected applications, you can add an injection rule to set where the injection is done.
2. For manually injection applications, you will need to work with the team performing the injection to ensure the jsAgent script tag is the first script loaded.
If manual injection is being used, confirm that there are no rules to exclude injection of Synthetic executions.
If manual injection is being used, confirm that the jsAgent script filename matches expected format:

<name>_<featurehash>_<version>.js or <appid>_complete.js
Synthetic only supports these formats.
Confirm that the jsAgent is a supported version, using the Application Health check.

What's Next

If you have resolved any issues highlighted above but are still not seeing any Synthetic sessions in your RUM Application, then please open a chat or Support ticket and provide the following information:

Link to the Browser Monitor in your environment
Link to the RUM Application in your environment

You can find further troubleshooting tips for Synthetic in the Synthetic Troubleshooting Map

article Browser Monitors: Automatically assigned applications in Troubleshooting

Browser Monitors: Automatically assigned applications

Summary

What is Application auto-assignment?

Troubleshooting

What's Next