Fields reference (pageview)

The list of descriptions of the JavaScript error events. Each event has the same index in all errors.* fields.

The list of timestamps of the JavaScript error events. Each event has the same index in all errors.* fields.

The list of URLs of the files where the JavaScript error events occurred. Each event has the same index in all errors.* fields.

The list of line numbers in the files where the JavaScript error events occurred. Each event has the same index in all errors.* fields.

The list of column numbers in the files where the JavaScript error events occurred. Each event has the same index in all errors.* fields.

The list of Group IDs of the JavaScript error events, used to regroup similar errors together in Contentsquare. Each event has the same index in all errors.* fields.

The list of URL endpoints of the API error events. Each event has the same index in all errors_api.* fields.

The list of HTTP method of the API error events. Each event has the same index in all errors_api.* fields.

The list of HTTP status codes of the API error events. Each event has the same index in all errors_api.* fields.

The list of the API call start timestamps of the API error events. Each event has the same index in all errors_api.* fields.

The list of Group IDs of the API error events, used to regroup similar errors together in Contentsquare. Each event has the same index in all errors_api.* fields.

The list of descriptions of the custom error events. Each event has the same index in all custom_errors.* fields.

The list of timestamps of the custom error events. Each event has the same index in all custom_errors.* fields.

The list of key/value pairs of custom tags of the custom error events. Each event can have a list of several key/value pairs. Each event has the same index in all custom_errors.* fields.

The list of Group IDs of the custom error events, used to regroup similar errors together in Contentsquare. Each event has the same index in all custom_errors.* fields.

If we got all kinds of events (clicks, mouse moves etc.) on the page, value is 1, else 0.

List of page events.

The list of the dates and UTC times of the click events. Each event has the same index in all raw_click.* fields.

The list of the raw events types. Can be either:

• 5: CLICK
• 10: CHANGE
• 11: FOCUS
• 12: BLUR

Each event has the same index in all raw_click.* fields.

Number of milliseconds between the beginning of the view and each of the raw events. Each event has the same index in all raw_click.* fields.

Whether the event was an interaction with a blank field in a form. Can be either:

• 0: Not applicable
• 1: False
• 2: True

Each event has the same index in all raw_click.* fields.

The list of the paths that were clicked. Each event has the same index in all raw_click.* fields.

The list of the paths of the target zone. Each target has the same index in all targets_clicks.* fields.

The number of times the target was clicked on (aggregation of raw_clicks). Each target has the same index in all targets_clicks.* fields.

The delay between the loading of the page and the time the user clicked on the target for the first time (in milliseconds). Each target has the same index in all targets_clicks.* fields.

Time before last hover and first select the target (in milliseconds). Each target has the same index in all targets_clicks.* fields.

List of the raw path of the targets. Each target has the same index in all targets_focus.* fields.

List of the number of times the target was focused on. Each target has the same index in all targets_focus.* fields.

List of times before first focus on a zone (in milliseconds). Each target has the same index in all targets_focus.* fields.

List of the raw path of the targets. Each target has the same index in all targets_hover.* fields.

List of the number of times the target was hovered on. Each target has the same index in all targets_hover.* fields.

List of the total time the target was hovered on (in milliseconds). Each target has the same index in all targets_hover.* fields.

List of times before first hover on a zone (in milliseconds). Each target has the same index in all targets_hover.* fields.

Those fields are only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 1 to indicate whether any API error occurred on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 1 to indicate whether any JavaScript error occurred on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 2 to indicate whether API errors occurred after some clicks. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 2 to indicate whether excessive hovers occurred on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 100 computed based on all other frustration indicators, to express an overall frustration level on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

Whether the page is considered watchable (1) or not (0). Only pages that are watchable have a frustration score. To be considered watchable, the page view must respect the following conditions:

• Be part of a collected session (is_recorded = 1)
• Its duration should be at least 2 seconds
• There should be at least 2 clicks on the page

This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 2 to indicate whether any JavaScript error occurred after clicks on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 1 to indicate whether loading time was slow on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 2 to indicate multiple interactions on button targets on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 2 to indicate multiple interactions on field targets on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 1 to indicate multiple interactions on targets on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 1 to indicate low activity on the page. This field is only exportable for projects with an access to the frustration score in Contentsquare.

A normalized score between 0 and 2 to indicate rage clicks (multiple clicks in a short time frame). This field is only exportable for projects with an access to the frustration score in Contentsquare.

City associated to the user.

Country associated to the user.

Language associated to the user.

Unique project identifier.

Unique user identifier. This is the hash of the user_id_unashed identifier.

Unique user identifier. User id stored in a cookie named _cs_id, which has a lifetime of 13 months.

List of the app event names. Each app event has the same index in all app_events.* fields.

List of dates and UTC time of the app events. Each app event has the same index in all app_events.* fields.

List of the app events types related to the session:

• 0: app start
• 1: app show
• 2: app hide

Each app event has the same index in all app_events.* fields.

The pageview number related to the event. Each app event has the same index in all app_events.* fields.

The client app version.

Pixel density measured in Pixels Per Inch (PPI) on the display.

The mobile device manufacturer.

The mobile device model.

Version of Android or iOS used by the visitor (iOS 13.1. or iOS 13.2 etc.)

The screen name.

List of finger directions related to the swipe events:

• 1: up
• 2: down
• 3: left
• 4: right
• 5: complex

Each target has the same index in all targets_drag.* fields.

The number of times the target was swiped.

Each target has the same index in all targets_drag.* fields.

List of finger directions related to the swipe or fast swipe events:

• 1: up
• 2: down
• 3: left
• 4: right
• 5: complex

Each target has the same index in all targets_drag_and_flick.* fields.

List of orientations related to the swipe or fast swipe events:

• 0: portrait
• 1: landscape

Each target has the same index in all targets_drag_and_flick.* fields.

Each target has the same index in all targets_drag_and_flick.* fields.

Each value has the same array index as their corresponding targets_drag_and_flick.finger_direction and targets_drag_and_flick.orientation.

List of finger directions related to the fast swiped events:

• 1: up
• 2: down
• 3: left
• 4: right
• 5: complex

Each target has the same index in all targets_flick.* fields.

The number of times the target was fast swiped.

Each target has the same index in all targets_flick.* fields.

List of the number of times the target was long press (a target is considered long pressed after at least 500ms).

List of values equal to 1 if the App reacted to the tap, else 0. Each target has the same index in all targets_tap.* fields.

List of the number of times the target was tapped. Each target has the same index in all targets_tap.* fields.

List of delays between the loading of the page and the time the user tap on the target for the first time (in milliseconds). Each target has the same index in all targets_tap.* fields.

Array of keys of custom variables extracted from the website datalayer. Each variable has the same index in all custom_vars_view.* fields.

Array of positions of custom variables extracted from the website datalayer. Each variable has the same index in all custom_vars_view.* fields.

Array of values of custom variables extracted from the website datalayer. Each variable has the same index in all custom_vars_view.* fields.

Page height in pixels.

Page width in pixels.

The time in milliseconds required before the user is able to interact with the page (although all resources may not be fully loaded yet).

Array of keys of integer dynamic variables extracted from the website datalayer of the pageview. Each variable has the same index in all dynamic_vars_int_in_view.* fields.

Array of values of integer dynamic variables extracted from the website datalayer of the pageview. Each variable has the same index in all dynamic_vars_int_in_view.* fields.

Array of keys of string dynamic variables extracted from the website datalayer of the pageview. Each variable has the same index in all dynamic_vars_string_in_view.* fields.

Array of values of string dynamic variables extracted from the website datalayer of the pageview. Each variable has the same index in all dynamic_vars_string_in_view.* fields.

The time in milliseconds required to fully load all the resources of the page, from initiation of the pageview to load completion in the browser.

If the page is the entry page then value is 1, otherwise value is 0.

If the page is the exit page then value is 1, otherwise value is 0.

The last path the was hovered by the visitor.

Interaction time in milliseconds.

Path of the pageview URL.

Host of the pageview URL.

Query of the pageview URL.

Protocol (HTTP or HTTPS).

The portion of the page which was displayed (in percentage points).

Timestamp sent by tag when the rendering of the page started.

The complete URL of the page (concatenation of prefix, path and query).

The URL of the page excluding query parameters (concatenation of prefix and path).

Duration between the page view event time (view_time) and the timestamp of the last interaction event (in milliseconds).

The pageview number in the session.

The pageview date and UTC time.

Array of bottom positions of the screen of the user. A new value is appended in the array after each scroll event if it’s not already present in the array.

The values in this array can be combined with the values at the same index in the arrays viewports.top_screen_position and viewports.exposition_time_msec to find corresponding top position of viewports and the total time the viewport was exposed in a given position.

For example, say a user:

• Starts at a viewport position (top=0, bottom=800) and stays in that position for 30 seconds; then
• Scrolls down to a viewport position (top=600, bottom=1400) and stays there for 10 seconds; then
• Scrolls up again back to the original viewport position (top=0, bottom=800) and stays there for another 20 seconds

Then the 3 viewports array fields will look like this:

• viewports.bottom_screen_position: [0, 600]
• viewports.top_screen_position: [800, 1400]
• viewports.exposition_time_msec: [50000, 10000] (30s + 20s = 50s = 50000ms)

The exposition time in milliseconds of the areas that were exposed to the user. A new value is appended in the array after each scroll event.

The values in this array can be combined with the values at the same index in the arrays viewports.bottom_screen_position and viewports.top_screen_position to find corresponding top position of viewports and the total time the viewport was exposed in a given position.

For example, say a user:

• Starts at a viewport position (top=0, bottom=800) and stays in that position for 30 seconds; then
• Scrolls down to a viewport position (top=600, bottom=1400) and stays there for 10 seconds; then
• Scrolls up again back to the original viewport position (top=0, bottom=800) and stays there for another 20 seconds

Then the 3 viewports array fields will look like this:

• viewports.bottom_screen_position: [0, 600]
• viewports.top_screen_position: [800, 1400]
• viewports.exposition_time_msec: [50000, 10000] (30s + 20s = 50s = 50000ms)

Array of top positions of the screen of the user. A new value is appended in the array after each scroll event if it’s not already present in the array.

The values in this array can be combined with the values at the same index in the arrays viewports.bottom_screen_position and viewports.exposition_time_msec to find corresponding top position of viewports and the total time the viewport was exposed in a given position.

For example, say a user:

• Starts at a viewport position (top=0, bottom=800) and stays in that position for 30 seconds; then
• Scrolls down to a viewport position (top=600, bottom=1400) and stays there for 10 seconds; then
• Scrolls up again back to the original viewport position (top=0, bottom=800) and stays there for another 20 seconds

Then the 3 viewports array fields will look like this:

• viewports.bottom_screen_position: [0, 600]
• viewports.top_screen_position: [800, 1400]
• viewports.exposition_time_msec: [50000, 10000] (30s + 20s = 50s = 50000ms)

Height of the window in which the page is opened.

Width of the window in which the page is opened.

Values are either 1 or 0, to indicate whether the session is generated from bot traffic (1) or not (0).

For Session Replay, indicates whether the session was collected (1) or not (0).

Session start date.

Session duration in milliseconds.

Unique session identifier.

The number of sessions of the user (takes into account how many times the user visited before).

Number of transactions placed during the session.

The number of page views in the session.

The replay link, if the session was collected (see is_recorded field).

Session start date and UTC time.

Total revenue generated by the session (in US dollar cents).

The referring URL to the first page view of the session.

Those fields are only exportable for projects with an access to the Speed Analysis module in Contentsquare.

Delay (in milliseconds) between the request for the web page and when the web browser received the first piece of data. This field is only exportable for projects with an access to the Speed Analysis module in Contentsquare.

Delay (in milliseconds) to render the first piece of content. This field is only exportable for projects with an access to the Speed Analysis module in Contentsquare.

Delay (in milliseconds) to render the largest piece of content (part of Core Web Vitals). This field is only exportable for projects with an access to the Speed Analysis module in Contentsquare.

Score about the layout stability of the page rendering (part of Core Web Vitals). This field is only exportable for projects with an access to the Speed Analysis module in Contentsquare.

Delay (in milliseconds) between the first user interaction and when the web browser can handle it (part of Core Web Vitals). This field is only exportable for projects with an access to the Speed Analysis module in Contentsquare.

Longest visual delay (in milliseconds) experienced by a user when interacting with the page (clicks or keystrokes). This field is only exportable for projects with an access to the Speed Analysis module in Contentsquare.

The browser major version.

The browser name.

The browser version.

Unique device identifier:

• 0: Unknown
• 1: Desktop
• 2: Mobile (Web)
• 3: Tablet (Web)
• 4: Mobile (App)
• 5: Tablet (App)

The operating system name.

The operating system version.

The screen height in pixels.

The screen width in pixels.