Custom dimensions

You can share custom dimension information in other ways. Do note that you still need to identify the dimension names to make it work. You will need to add custom dimensions, where the name of the dimension will match the second parameter. 

To pass custom dimensions, you can call the rumv function and pass dimension as the first parameter, and your dimension key as the second parameter. The third parameter should contain your dimension value. This will then become available as custom filters.

Non-JavaScript solution

Do note that you might not always need JavaScript. Our out-of-the-box configuration offers support for metatags. So if you have the option to add custom metatags to your templates and populate them dynamically, then that might be a better fit and will also require less JavaScript work.

Custom dimension examples

Here are some examples how our JS API can be used to submit custom dimensions. For example, sharing your deploy version to better analyze pagespeed differences per deploy, or just exclude informaton from older deploys:

rumv('dimension', 'deploy', 'v3.1');

Share the author of a blogpost etc:

rumv('dimension', 'author', 'Richard');

The following might be a good use-case, as information such as cookie-preferences isn't known from the start, but only when a user interacts with the cookie notice. You could then share the cookie preferences with us, enabling you to compare pagespeed metrics between users who did accept cookies and third parties, and those who didn't.

rumv('dimension', 'cookie-consent', 'functional-marketing');