- Go to a browser application.
Select a hosting option.
Customize the code snippet in Step 2: Advanced settings (Optional).
config.useHTTPSAlways = true added to the UI snippet.
|Available in SaaS Controller >= 20.7.0
|Manual Configuration Instructions
|Use HTTPS by default
|Set cookie to strict domain
|Limit the cookie to the full strict domain name. If unchecked, the cookie is set to the broadest version of the originating domain (such as,
|If your application uses internet IP addresses or users connect through a VPN, enter your custom GeoServer URL to map internal IP addresses to physical locations. If unchecked, end-user locations are resolved using the default GeoServer.
|Configure Resource URL Segments
|Set the maximum number of segments and characters in resource URLs to view more or less of a URL in the Controller UI.
|Hide URL query string
|By default, URL query strings may be long or contain sensitive information. Check this box to hide the full string from the Controller UI.
|Cross-domain session correlation
|Enable sessions to continue across subdomains. If unchecked, sessions are restricted to one domain and navigating from one domain to another will end the session.
|Configure request origin location
|Set a specific IP address or location as the origin of the request. You can specify only the IP address, or the complete location (IP, country, region, and city).
|Configure resource options
|Configure which resources are monitored based on how they are ordered, the maximum number of resources that will be evaluated, and whether the resource timing buffer should be cleared when it's full.
|Modify resource sampling options
|Modify how the resources are ordered (using the sampling algorithm) and the maximum number of resources to be evaluate.
|Capture page title
|Capture the page title as part of the beacon, displayed in Browser Snapshots. Uncheck this setting to hide the page title for security or privacy reasons. Check this setting to set a custom page title with an arbitrary URL string.
|Enable SPA2 monitoring
|Enable resource timing buffer clearing for SPAs
|Set the custom page name
|The page name is used to identify and group pages in Pages & AJAX Requests. If unchecked, the default page name consists of the hostname, port, and path.
|Filter virtual pages
|Configure rules to exclude specific virtual pages from being monitored.
|Monitor Fetch API calls
|Set AJAX request limit
|To prevent an overload of AJAX requests, you can limit the number of requests sent per base and virtual pageview. The limit is 250 requests for single-page applications (SPAs) and 50 requests for non-SPAs.
|Filter XHR calls by URL
|Include or exclude specific XHR calls to be monitored.
|Limit beacon types
|By default, sending image beacons is disabled and beacons are only sent with Cross-Origin Resource Sharing (CORS). If you have an older browser that does not support CORS beacons, you can enable sending image beacons.
|Disable browser monitoring programmatically
|Handle the window.onerror event
window.onerror event, add the method
ADRUM.listenForErrors()to the page immediately after setting
|Set Ajax request names based on captured POST parameters
POST parameters and then use the parameter(s) to name the Ajax request in Pages & Ajax Requests. This configuration enables you to identify and sort Ajax requests from the same page based on
|Set custom virtual page names
|Add custom user data to a page browser snapshot
|Add Nonce to adrum-ext.js
|You can add the
nonce attribute in the adrum script tag to make sure the
nonce value is read by
- From Controller Admin, go to Controller Settings.
- For the values of settings
- From the Controller Admin, go to Controller Settings.
- For the values of settings
- Assisted Injection
See Overview of Injection Types for differences between the injection methods.