Installing the snippet

🎬 Rather watch a video tutorial?

Our snippet is used to collect real user data. To get data in RUMvision, each domain requires its own tracking snippet.

Already installed the snippet and now want to make adjustments? Jump to our introduction to Configure snippet

Finding your snippet

Installing the snippet is straightforward.

  1. Go to managesettingssnippet.
  2. If you have an active subscription, you can see the snippet.
  3. Copy the snippet or share the public link with the person responsible for the snippet installation.
  4. The easiest way is to install the snippet via Google Tag Manager (GTM).
  5. After installing the snippet check your network requests and search for your own RUM code to check if everything is working and your website's Content Security Policy is not blocking the snippet.

RUMvision installing real user monitoring snippet

GTM installation

Follow these steps to install our snippet via GTM:

  1. Add a new tag.
  2. Select tag configuration and choose custom HTML.
  3. Paste the snippet in the textbox.
  4. Set the trigger to all pages (type: pageview).
  5. Rename the tag.
  6. Save the snippet and then click the submit button at the top right of the page.

Installing snippet via GTM

We have now started tracking the homepage you specified when you registered your domain. To track more you can set up pages.

Did you add the snippet and now waiting for data? Learn more about how soon you should see data.

When your snippet is added correctly, you'll get an email as soon as we see the data coming in. Often this is within 15 minutes! Of course, enough data needs to be collected to gather a good sample size to draw conclusions, this is typically 24 hours later.

Without Google Tag Manager

If you're not utilizing Google Tag Manager or if you require more data to be tracked without the delay associated with GTM, you have the option to incorporate our code snippet directly into your source code.

You can choose to embed it either in the <head> or <body> section of your HTML documents. Regardless of your choice, you'll always gather valuable RUM data. However, for the sake of data consistency, we recommend placing the script in the <head>.

Here are some performance best practices to consider when incorporating our inline JavaScript into your source code:

In the <head>

When you decide to place it in the <head>, never position our JavaScript after a stylesheet. In other words, be sure to place the inline script just before your first stylesheet. Other scenario's will slow down FCP and potentially LCP.

In the <body>

When placing our inline script in the <body>, it is best to position it at the end of the document instead of the start of the <body>.