📄️ Applications
In Real User Monitoring (RUM), customer applications (websites, mobile apps, etc.) are instrumented to report real user visits to the platform for monitoring and analysis. Typical user entry points include web applications running in browsers, as well as mobile applications running on iOS or Android smartphones or tablets.
📄️ User Sessions
In Real User Monitoring (RUM), the user session is the core unit of analysis. It serves as the panoramic vehicle for reconstructing the complete user experience journey, linking experience issues to business impact, thereby bridging the gap between "isolated actions/metrics" and "real user scenarios."
📄️ Pages
User perception of digital product experience essentially boils down to "a complete cycle of page loading and interaction". For instance, when opening an e-commerce homepage, a checkout page, or a payment result page, factors like how fast the page loads, whether it freezes, and whether it functions properly directly determine user satisfaction. Isolated metrics divorced from the "Page" (e.g., "An API response time of 200ms") cannot directly reflect user experience. Only by taking the "Page" as the carrier and correlating technical metrics—such as API performance, resource loading, and frontend rendering—with "user behaviors on the page" (e.g., button clicks, time spent) can we determine whether a technical issue actually impacts users.
📄️ Actions
In Real User Monitoring (RUM), the Action is one of the core analysis objects. An Action serves as the carrier of user interaction behavior and system service capability, acting as a key nexus connecting "user experience perception" with "business goal achievement." Actions directly correspond to the user's core behaviors within an application—whether it's clicking a button to submit an order, loading a product list page, or triggering form validation. Each Action represents a step the user takes to advance a business process.
📄️ Requests
In Real User Monitoring (RUM), network requests are a core analysis object. They connect three critical links: "user experience perception," "frontend interaction response," and "backend service capability." Network requests serve as the most direct data carrier for pinpointing the root causes of "user experience lag/operation failure," quantifying "system service quality," and correlating "business operation success or failure." They are also the essential bridge from "surface-level experience issues" to "underlying technical bottlenecks."
📄️ Users
In Real User Monitoring (RUM), a "User" is not merely a "person using the product". It is an "independent, traceable, and analyzable entity" formed by combining "identity", "behavioral trajectory", and "device environment". It serves as the core dimension for linking "User Sessions, Actions, and performance data". Its definition revolves around "how to accurately identify and correlate user experience data across the entire lifecycle".
📄️ User groups
Due to the typical user volume of an application being in the millions or even tens of millions, performing grouped statistics for every individual user would result in poor performance. Therefore, before conducting user analysis, it is necessary to import core User IDs into the platform and organize them into groups. This ensures that collected metrics related to User Sessions and Actions will carry the User Group dimension, facilitating subsequent statistical analysis.