Try it free

Configure cost and traffic control for web frontends

  • Latest Dynatrace
  • How-to guide
  • Published Nov 18, 2026

By default, Dynatrace captures all user sessions, ensuring complete insight into your frontend performance and customer experience. To lower monitoring cost and traffic, you can reduce the percentage of captured user sessions by configuring cost and traffic control. For example, a capture rate of 10 means that roughly every tenth user session is captured, subject to the limitations of this feature.

To configure cost and traffic control

  1. Go to Experience Vitals Experience Vitals > Overview.

  2. Select Web to view all web frontends.

  3. Select the frontend you want to configure.

  4. Switch to the Settings tab.

  5. Under Enablement and cost control > Real User Monitoring (RUM) > Capture rate of user session, enter a value less than 100.

How cost and traffic control is applied

OneAgent and the beacon endpoint on the Cluster ActiveGate apply cost and traffic control per frontend within a browser session. The state of a browser session is persisted in the dtCookie. A browser session starts when an end user first accesses a page in the cookie domain and ends when they close the browser.

One browser session may span multiple frontends. Whenever the end user accesses a frontend that isn't part of the browser session yet, the capture decision for that frontend (captured or blocked) is made independently of the other frontends in the browser session. Whichever component handles the first request of the browser session for that frontend, OneAgent or the beacon endpoint on the Cluster ActiveGate, makes this decision and stores it in the dtCookie. This first request can be a regular application request or a beacon request.

With automatic injection, the RUM JavaScript is always injected, even when a browser session is blocked. This keeps cost and traffic control compatible with CDNs, which would otherwise intermittently serve HTML without the injected RUM JavaScript.

A blocked browser session is handled in two ways:

  • When the RUM JavaScript reads the blocked state from the dtCookie, it stops sending beacons.
  • When the RUM JavaScript sends a beacon before the capture decision has been made, the beacon endpoint makes the decision and, if the browser session is blocked, doesn't forward the beacon to Dynatrace.

Limitations

As described above, cost and traffic control works on browser sessions, not on user sessions. As a result, the actual percentage of captured user sessions can differ from the configured capture rate. Keep the following in mind when you choose a capture rate and evaluate the results.

Percentage of captured user sessions is approximate

A user session often lasts as long as its browser session, but it can also end earlier. For details, see User session lifecycle. As a result, one browser session can contain multiple user sessions, and all of them share the capture decision of that browser session.

Over time, the percentage of captured user sessions usually comes close to the configured capture rate. The difference can be larger if some of your end users have long-lived browser sessions, because each of these browser sessions can contain many user sessions.

Capture rate takes effect gradually

When you turn on cost and traffic control or lower the capture rate, it can take some time until the configured capture rate is reached, because browser sessions that are already ongoing at that point are still captured until end users close their browsers.

Related topics

  • Understand and manage consumption for Real User Monitoring (DPS)
Related tags
Digital Experience