Request Metrics protects user privacy by default. Users are not tracked across browsers or sites. However, it is often useful to know when a user or customer is seeing poor performance or running into other user experience problems.
Warning: If you send sensitive data, or data that may make the user identifiable, you must obtain consent from the end-user in compliance with local regulation. See End User Data for more.
By default the Request Metrics dashboard displays anonymous user names. These are generated from basic information about the user include their anonymized fingerprint. These user names look like, “Firefox/Windows in USA (FEAB04C)”. Identifying users allows you to override this behavior.
Identify a User
You must have a unique ID, name or other value to identify the user. When you identify the user, Request Metrics will use your user ID in place of its own user finger printing. All user information shown in dashboard is then based on your identifier. The only required field is the user’s unique identifier:
Add More Context
Additional metadata can be included in the
RM.identify() call. This gives you additional context and visibility into how specific subsets of users are experiencing your site.
Display Name and Email
Two special metadata keys are used by the Request Metrics dashboard.
name key overrides the username displayed in the UI and
Arbitrary key/value pairs are also supported. These can be anything important to you or your users.