Error export

This is for:


In this article, we’ll introduce you to our experience errors export and how you can use it to get an insight into the Javascript errors encountered by users viewing an experience.

Reporting detail

This export type provides insight into the JavaScript errors encountered by users viewing an experience. This information is very useful for developers debugging issues with experiences.

As with all Qubit exports, you can specify the level of reporting detail to get a much greater understanding of reportables and focus on the details you are really interested in.

For this export type, you can select:

  • Which experiences to export

  • A date range to include only data covering a defined period of time

  • Exclusion dates to exclude particular days or a period of time from the data

  • Dimensions, including device type and location, which allow you to decide how to break down the data


  • Error data is taken from the debug event event_qubit_debug, which is used to send debug information from the Qubit platform

  • When applying the date range filter, we take the date when the debug event was emitted

  • The event date is based on meta_recordDate, according to the configured timezone

  • The data for the dimensions comes from the session data associated with the debug event. Where there are duplicate events for the same session, we take the first value in ascending alphabetical order

  • The data for each selected experience comes from the Experience event data associated with the view number of the debug event for that visitor

  • We exclude debug events where the message field of the value JSON is null

  • The debug event timestamp is based on the meta_serverTS associated with the debug event, that is, the epoch time in milliseconds for the event when received by the server


There may be a timezone conflict between the debug timestamp, which is in UTC, and the date range filter, which is in the timezone configured for the property.

Dimensions and output


Name Description Output

Device Type

The visitor’s device type when the visitor was served the experience


Browser Version

The detected browser and version number for the visitor when the experience was served



Additional fields not included in the dimensions table above:

Field Description


Time and date of the Debug event (meta_serverTs)


The name of the experience


The name of the experience iteration


The name of the experience variation


The message field of the value JSON of the Debug event


The total number of Debug events