# Real User Monitoring

Real User Monitoring (RUM for short) results in so-called [field data](/md/help-center/glossary/metrics/field-data/). That's because Real User Monitoring -whether your [Core Web Vitals](/md/help-center/glossary/monitoring/core-web-vitals/) data or collected yourselves- results in data collected from real users. This data is collected 'in the field'.

RUM data is convenient in different ways:

- **flexibility**  
   Most RUM providers allow for flexibility, tracking additional information from your real users
- **deep diving**  
   it allows for deep-diving, finding exact root causes of issues that you see in (Google's) [aggregated data](/md/help-center/glossary/dashboarding/aggregation/) (such as [PageSpeed Insights](/md/help-center/glossary/monitoring/pagespeed-insights/) or [Google Search Console](/md/help-center/glossary/monitoring/google-search-console/)).  
   Additionally, you can look into other percentiles besides [75th percentile](/md/help-center/glossary/dashboarding/75th-percentile/) that Google is using for their [Web Vitals](/md/help-center/glossary/metrics/web-vitals/).
- **A/B testing**  
   By using custom dimensions, performance consultants and other [site speed experts](/for-whom/site-speed-experts/) can perform pagespeed A/B tests and see if an adjustment came with a UX improvement (and by how much)

## Who should use RUM?

The short version: everyone should use RUM. But these blogpost are explaining it in more detail:

- [Why you need a Real User Monitoring tool](/md/blog/why-you-need-a-real-user-monitoring-tool/)
- [When not to use Google Lighthouse](/md/blog/when-not-to-use-google-lighthouse/)
- [Is RUM data the same as field data?](/md/blog/is-rum-data-the-same-as-field-data/)

Last changed 5 November 2024
