News regarding the latest Cubicast development and features.

Size Limits for Assets Used in Web Pages

To ensure our API’s smooth operation, we have introduced the maximum allowed sizes for assets used in web pages. After monitoring our API’s response times, we’ve seen some unusual spikes. Diving deeper, we’ve seen that these spikes were caused by uploading chunks with huge image data URLs (sometimes exceeding 5MB). After looking into this client’s use case, we discovered that an image-processing plugin generates huge data URLs for IMG elements. The existing approach was causing some side effects, such as having these chunks rejected on the server side because of exceeding the maximum request payload of 2MB or being dismissed on the client side by not being able to send these chunks with beacons.

Read more

Releasing Support for Customer Support Integrations, With Zendesk Being the First One

Finally, we are happy to note that we have released our first integration with an external customer support service. The first platform of choice is Zendesk, with support for more customer support services coming in the future. After adding a customer support integration, you must enable the switch to accept customer support requests in the recorder settings section. Each workspace allows only one customer support integration. Therefore, you cannot add a new customer support integration once you have already added another one.

Read more

Don't Touch My DOM!

The good news is that the latest Cubicast recorder release no longer modifies any of your HTML elements. Other than adding the necessary elements for it to function properly, the rest of the DOM is left intact. The new approach solves two problems, with the first one being obvious. Some clients complained about the recorder adding custom attributes to their elements. This is no longer the case. The second one, and possibly the most important, was the scenario of capturing with our extension a website that already has our recorder script added, which could lead to unexpected results on both recordings because of conflicting element identifiers.

Read more

User Frustration Signals

How can you tell when users are frustrated? Typically, there are a bunch of user reactions that reveal frustration. In detail, user frustration signals fall into the categories below. Rage Clicks Rage clicks are when users click or tap several times an element of a website or app. Most of the time, this indicates frustration. Users click on a button, nothing happens, and they click it again and again. Our latest release supports capturing rage clicks.

Read more

How is your Website Performing Around the Globe? Performance API to the Rescue!

We are pleased to announce that our latest release supports tracking of slow resources, including slow-loading pages, API endpoints, scripts, images, and CSS resources. Slow resources The recorder hooks into the Resource Timing API if tracking of slow resources is enabled. Users can choose the types of resources that are tracked from the following resource types: API requests Scripts Images CSS style sheets and related resources In addition, users can also specify the request duration threshold at which each resource should be logged as an issue and track resources only from specific hosts.

Read more

Announcing New Pricing Model and Plans

In the past few months, we focused on a new initiative towards optimizing our infrastructure and vendor costs. As it turns out, the outcome of this process is more than rewarding for all our existing and new customers. For new customers, new pricing is effective starting today. For existing customers, the new pricing is in effect starting from the next billing period. The highlights of the new pricing model are:

Read more