Blog

A popular feature request, has always been the ability to track custom events. Going forward, you can now track custom events by using our JavaScript API. Obviously, this kind of functionality is not available when using the Cubicast browser extension. Here is how custom events appear in the workspace’s Acitvity Log. If you are planning to use this new feature for existing workspaces, make sure you update your JavaScript snippet to the latest version which exposes the new track method.

We are thrilled to announce that our latest release supports recording sessions of private hosts, including localhost. When using our browser extension, no restrictions of any kind apply. Thus, you should be able to capture any private host having pixel-perfect recordings. However, if you have embedded the Cubicast recorder snippet in a private web site, residing in your local machine, intranet or extranet, cross-origin restrictions may apply. If all stylesheets, fonts and images are fetched from the same origin (i.

Now you can automatically track page views, clicks and user input. These events will serve as the basis for our reports and on-demand funnels. Page views are tracked at all times, using both the browser extension and the JavaScript snippet. Clicks and user input can be switched on and off using the browser extension settings tab or the workspace’s recorder settings, depending on the use case. Existing workspaces, may not have clicks and user input tracking enabled by default.

Once we had canvas capturing implemented, adding videos in the loop was a matter of time. The good news is that the latest recorder implementation now supports capturing video elements. Of course, the same limitations with capturing canvases, apply in this case as well. In order to capture videos retreived from other origins, the video has to have the crossorigin attribute set, and the appropriate CORS headers configured on the origin server.

Previously, the Cubicast recorder snippet was relying on 3rd party cookies to function properly. After Apple announcing that Safari now blocks all 3rd party cookies, we had to refrain from using 3rd party cookies. Our latest version now uses the following top-level domain first party cookies: Cookie Name Lifespan Purpose __cc 10 minutes Used for storing the recording details when the page is unloaded, so that it can be resumed when user reloads the page.

We are pleased to announce that our latest recorder release supports capturing uncaught JavaScript errors. This is a significant enhancement as it gives you the ability to know exactly which of your users were impacted by what errors and the exact snapshot of the DOM when this error occurred. The current implementation will capture the error’s stack trace, resolving source maps if available. Furthermore, if you have added a Slack integration in your workspace, you will receive near real-time notifications about JavaScript errors in your configured Slack channel.