Settings
A few basic settings can be changed here, such as default percentile to be used in your dashboards as well as open tracking configuration settings. You can also specify if health checks should appear for this domain.
Settings
Available open tracking configuration settings:
When to track
By default, we'll start tracking once our JavaScript has loaded. However, when CSS selectors were used as URL rules, elements that are identified via those CSS selectors might not have been constructed by the browser yet. In those cases, the value for "When to track" will auto-adjust to "interactive".
While you can't change it back to "instant", you can choose to let our script run slightly later after the "onload" event.
Track query string values
By default, our JavaScript won't store query string values, only parameters. For some parameter keys, you might want to make an exception. This can be convenient when you suspect that it's not specifically the keys, but their values that are resulting in anomalies in your data. Tracking values could then be of help.
Tracking anonymization rules
When tracking query string values, there is still a risk of accidentally collecting Personally Identifiable Information (PII). You can specify anonymization rules to remove or replace potential PII before it is ingested into your datasets.
For example, by specifying the following:
{".*@.*..*":"email"} Any value matching this email address pattern will be replaced by email before it is ingested.
When fewer than 2 regular expressions are configured, RUMvision will replace them with a default set similar to the following:
{
"[a-z0-9._%+-]+@[a-z0-9.-]+\\.[a-z]{2,}": "email",
"\\b\\d-\\d-\\d\\b": "ssn",
"\\b[0-9a-f]-[0-9a-f]-[1-8][0-9a-f]-[89ab][0-9a-f]-[0-9a-f]\\b": "uuid",
"\\b\\d{6,}\\b": "id"
}For example, a URL such as /profile/user/31f52c06-8bc7-45ab-8efe-22cd1fccc194.html will be stored as /profile/user/[uuid].html in your data.
By default, a fixed set of fields and all custom data are checked and sanitized against these regular expressions.
Changes to privacy sanitization should be tested carefully. Removing existing protection can allow unwanted values to reach RUM payloads.
When the "Enable rumv() get/set API" feature is enabled, the regular expressions used to sanitize data can also be adjusted at runtime. This can be useful on pages or flows that are more likely to expose PII.
Danger zone
When you cancelled your subscription and want to delete all domain-data, or when you want to start tracking a new domain but aren't ready to upgrade yet, you can delete a domain and all of its data and users.
On the Settings page, scroll to the very bottom of the page. You'll see a Danger Zone marked in red. When proceeding via the red button, the domain along with its URLs, URL categories, alerts, and scheduled reports will be deleted.
You'll first be prompted for your password.
Once this domain is deleted, all of its data will be permanently removed. This action cannot be undone.
