Here are some common questions when using Cronitor Real User Monitoring:
You can find your Cronitor RUM client key by going to your Dashboard > Sites > Your Site > Installation.
When using the default HTML snippet, Cronitor RUM automatically tracks JS navigation changes for you - you’re all set!
However, when using the cronitor-rum-js library you need to trigger pageviews manually. This is so you can have more control over what your application considers a navigation change.
For example, some JS frameworks let you hook into the router to listen for changes:
Cronitor.load(clientKey, config);
// Add on route change handler for client-side navigation
router.events.on('routeChangeComplete', () => Cronitor.track('Pageview'));
No. Cronitor RUM collects the minimum amount of data necessary to provide our service, and we do not sell or rent personal data to anyone.
We’ve designed it in such a way so that you can collect traffic and performance trends in your website without anyone being able to trace the data back to an individual visitor or IP address - not even us.
An event is any datapoint sent by one of your sites. Cronitor automatically tracks events such as Pageview, WebVital and Error but you could record any interaction you’d like using a feature called custom events.
For example, suppose a visitor navigates to 2 pages on your website and also triggers a custom event called ‘NewsletterSignup’. In this case, a total of 3 events will be counted towards your monthly quota (2 page views + 1 custom event).
For billing purposes, we only count events sent within your current billing cycle. Events are kept for the data retention period included in your plan (eg. 6 months).