On April 15th, 2025, Catchpoint will update its RUM logging domain. This change may require customers to update policies and allow the new domain in customer website content security policies.
The domain name change will apply for new versions going forward.
The new RUM domain going forward will be rjs.3gl.net. We suggest allowing/whitelisting the domain with a wildcard for the script: *.3gl.net. You can continue using the existing RUM tag which utilizes our current domain: r.3gl.net.
V4.0.5
Added support for inline script with defer attribute. User can add one-line reference to a hosted script file with defer attribute instead of adding full content of a large script to test configuration
V4.0.4
Fixed issue with formatting of Promise errors
V4.0.3
Removed FID (First Input Delay) metric
V4.0.2
Replaced Arrow functions and Const keyword with alternative es5 code to resolve compatibility issues with GTM (Google Tag Manager)
V4.0.1
Added 4 frustration Metrics
- Error click
- Rage clicks
- Dead click
- Thrashed cursor
Added INP debug Info
- Capturing the top 10 elements that cause INP greater than 200
- The element that caused the highest INP will be used as Dimension and others can be found in records waterfall
Capture # requests
- We send waterfall data based on the sampling rate, but we should be capturing the request count always.
Capture the transfer size of a waterfall item
V4.0.0
Re-architecting of JSP
- Redesign & Modularization of JSP
- Single script: Now client can inject single script instead of RProfile calling the main script in Iframe
BUG Fixed
- Bug 184072: [RUM] Intermittently missing LCP metric
V3.3.11
Improved error capturing logic
- If a customer wants to capture console.log errors for analytics they have to utilize tracepoints, but there is a character limitation of 32 and therefore we aren't capturing all data, additionally, this was not the intended use of tracepoints.
User Story 182209: Capture onunhandledrejection errors as JS errors for RUM
V3.3.10
Added the ability to only capture Ajax from specific domains for RUM
The current RUM javascript tag collects ajax calls made on each page, but if clients page has many calls from various domains making it hard to see the ones they care about such as "my cart" actions.
Within the Site Properties in Control Center, we added the ability to specify specific domains that Ajax calls are to be collected from, or all. The JSP will then use this information to determine when/where to collect Ajax calls.
Fixed an issue while using GTM custom events to inject RUM Tag
Bug 178844: The latest RUM version 3.3.9 implemented but fails to execute properly.
V3.3.9
Replaced Performance: timing property
In JSP we had to replace https://developer.mozilla.org/en-US/docs/Web/API/Performance/timing as this is depreciated
Now using https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming instead