No (metric) data
If you are not seeing data in RUMvision, the first step is to determine whether you have just started tracking or whether a website that previously collected data has stopped receiving new data.
If you have not installed the RUMvision snippet yet, start by installing the snippet. RUMvision can only collect detailed real-user monitoring data once the snippet is running on your website.
No data after installing RUMvision
If you recently installed the RUMvision snippet but are not seeing any data yet, check the following:
Wait for new traffic and data processing
It can take approximately 3 to 10 minutes before new data becomes available in RUMvision. Data is collected from real visitors, so after installing the snippet you may also need to wait for new traffic to reach your website.
Check your URL rules
RUMvision only tracks pages that match your configured URL rules. If visitors have not reached any matching pages yet, you may not see data.
Review your URL rules and consider adding more pages or page rules to make sure the pages receiving traffic are included.
Check active filters and date ranges
Filters or date ranges from a previous analysis can make it appear as if no data is available. Clear your active filters and check the selected date range.
You can also open RUMvision in a new tab or window to start with reset filters.
Check desktop and mobile data
Your current device filter may not have received enough traffic yet. Check both desktop and mobile traffic to determine whether data is missing for all devices or only for a specific device type.
Check whether the RUMvision snippet is loading
If you still do not see any data, verify that the RUMvision snippet is loading correctly on the website.
Open your browser's DevTools, go to the Network tab and check whether the RUMvision JavaScript file is being requested. If it is missing, review your snippet installation.
Data stopped coming in
If RUMvision collected data before but no longer receives new pageviews, the initial installation was working at some point. First determine when collection stopped and whether the organisation's usage limit was reached. When historical data is available, check previous usage periods for the same pattern before investigating implementation changes. If usage does not explain the interruption, continue with snippet loading, URL matching and recent website or configuration changes.
Check your organisation usage limit
If your organisation has reached its monthly usage limit, RUMvision will stop collecting new data for the remainder of that usage period.
You can check your current and estimated usage at organisation level. This shows your monthly usage limit, how much has already been used and which domains are contributing to it.
If historical RUM data is available, also check previous usage periods. Determine whether data collection stopped around the end of previous periods as well and whether collection resumed when a new usage period started.
A recurring pattern where data collection stops after the monthly allowance has been consumed and resumes in the next usage period is a strong indication that the organisation's usage allowance is structurally too low for its traffic.
In that situation, increasing the available usage is preferable to repeatedly losing monitoring data near the end of the usage period. The organisation can purchase additional pageviews or upgrade its subscription to a plan with a higher included usage allowance.
If there is no historical pattern of usage-related interruptions, continue troubleshooting other possible causes such as snippet loading, URL rules, consent, CSP or recent website changes.
Check whether the RUMvision snippet still loads
Open your website and use the Network tab in your browser's DevTools to verify that the RUMvision JavaScript file is still being requested.
If the request is no longer present, check whether recent changes to your website, tag manager, consent setup, Content Security Policy (CSP), caching or deployment may have affected the snippet.
Check whether your URL rules still match
Changes to your website's URL structure can cause existing URL rules to stop matching. Review your configured URL rules and compare them with the paths currently used by your website.
Check filters and date ranges
Make sure the selected date range includes recent traffic and clear any filters that could be hiding new data.
Missing data for specific metrics
If pageviews and other RUM data are available but a specific metric is missing, this does not necessarily indicate a tracking problem.
Not every browser supports the same performance APIs and not every metric is available for every pageview. Browser support can therefore affect which metrics RUMvision is able to collect.
Some metrics also depend on a specific event or user interaction occurring during the pageview. If only a specific metric is missing, check its documentation and allow enough pageviews to be collected before concluding that there is a tracking issue.
If these steps do not explain the missing data, feel free to contact us.
