User sessions API - User session structure

The version of the application where the user session has been recorded.

This information is provided by another integration, such as OpenKit.

The type of the application used in the user session.

The user session has (true) or doesn't have (false) a bounce.

A bounce means there is only one (or less) user action in the user session.

The family of the browser used for the user session.

The version of the browser used for the user session.

The ID of the Synthetic browser monitor that created the session.

The name of the Synthetic browser monitor that created the session.

The type of browser used for the user session.

The carrier information of the mobile user session.

The city from which the user session originates (based on the IP address).

The time offset of the client, in milliseconds

Additional information about the client.

This field can not be queried via the user session query language. Use the browserType field instead.

The serialized connection type of the mobile user session.

The continent from which the user session originates (based on the IP address).

The country from which the user session originates (based on the IP address).

If a mobile session crashed, this is the ID of the group to which the crashed session belongs.

If the session did not crash or the session is not a mobile session, it has the null value.

A list of custom properties of the user session with date values.

The detected device used for the user session.

The detected screen resolution of the device used for the user session.

A list of custom properties of the user session with floating-point numerical values.

The duration of the user session, in milliseconds.

This is calculated as the amount of time between the start of the first user action and the end of the last user action.

The reason for the end of the user session.

The timestamp of the last user action in the user session, in UTC milliseconds.

A list of errors recorded in the user session.

A list of additional events recorded in the user session.

The user session includes (true) or doesn't include (false) a crash.

The user session includes (true) or doesn't include (false) an error.

Session Replay is (true) or is not (false) available for the session.

The unique ID of the user that triggered the user session.

The IP address (IPv4 or IPv6) from which the user session originates.

The internet service provider from which the user session originates (based on the IP address).

A list of custom properties of the user session with integer (short or long) values.

The detected manufacturer of the device used for the user session.

A list of conversion goals achieved by the user session.

Additionally, you can define conversion goals for a single user action.

The number of conversion goals achieved by the user session.

The network technology information of the mobile user session.

The user is a first-time (true) or a returning user (false).

The number of rage clicks detected in the user session.

The number of rage taps detected in the user session.

The type of operating system used for the user session.

The version of the operating system used for the user session.

User sessions can be split into multiple parts for various technical reasons (e.g. after 200 user actions). This partNumber represents the number of each part of the overall user session.

The reason for absence of Session Replay.

The reason for absence of Session Replay on mobile.

The region from which the user session originates (based on the IP address).

The timestamp of the Session Replay end, in UTC milliseconds.

The timestamp of the Session Replay start, in UTC milliseconds.

The mobile device is rooted/jailbroken (true) or genuine (false).

Has the value of null if the status is unknown or undefined. Custom applications always report unknown/undefined.

The detected screen height of the device used for the user session.

The detected screen orientation of the device used on the device for the user session.

The detected screen width of the device used for the user session.

The timestamp of the first user action in the user session, in UTC milliseconds.

A list of custom properties of the user session with string values.

A list of synthetic events recorded in the user session.

The ID of the Dynatrace environment that captured the user session.

This field can not be queried via the User Session Query Language.

The number of errors detected in the user session.

Number of resulting billed sessions: Dynatrace classic licensing, Dynatrace Platform Subscription.

The number of user actions in the user session.

A list of user actions recorded in the user session.

The user experience score of the user session.

The user ID provided for the user session by session tagging.

The unique ID of the user session.

The type of the user. Indicates either a real human user (REAL_USER) or a robot (ROBOT or SYNTHETIC).

The custom key of the property.

The date value of the property.

The custom key of the property.

The floating-point numeric value of the property.

The name of the application, based on the configured detection rules.

The DNS domain where the error has been recorded.

The Dynatrace entity ID of the application.

This information is useful when calling various REST APIs, for example, as a key for time series queries.

The name of the error.

The timestamp of the error, in UTC milliseconds.

The type of error.

The name of the application, based on the configured detection rules.

The DNS domain where the event has been recorded.

The Dynatrace entity ID of the application.

This information is useful when calling various REST APIs, for example, as a key for time series queries.

The metadata attached to the event.

The name of the event.

The name of the page the user navigated to during a page change event.

The page group is automatically derived from the page.

The name of the previous page from which the user navigated from during a page change event.

The page referrer group is automatically derived from the page referrer.

The timestamp of the event, in UTC milliseconds.

The type of event.

The custom key of the property.

The Long value of the property.

The custom key of the property.

The string value of the property.

The error code of the error that occurred during this event.

Description of the error that occurred during this event.

The name of the synthetic event.

The sequence number of the synthetic event in scope of the complete browser monitor.

The Dynatrace entity ID for the synthetic event.

The timestamp when the synthetic event was simulated, in UTC milliseconds.

The type of the synthetic event. For example click or keystroke.

The user experience index of the user action.

The name of the application where the user action has been recorded.

The time spent waiting for CDN resources for the user action, in milliseconds.

The number of resources fetched from a CDN for the user action.

The cumulative layout shift (CLS) is the total amount of all individual scores for every unexpected layout shift that occurs during the entire lifespan of the page.

The CLS is an important user-centric metric for measuring visual stability. It quantifies how often users experience unexpected layout shifts. A low CLS indicates that the page is delightful.

The total number of custom errors during the user action.

A list of custom properties of the user session with date values.

The amount of time spent until the document for the user action became interactive, in milliseconds.

The amount of time until the DOM tree is completed, in milliseconds.

The amount of time until the DOM tree is loaded, in milliseconds.

The DNS domain where the user action has been recorded.

A list of custom properties of the user session with floating-point numerical values.

The duration of the user action, in milliseconds.

This is calculated as the of time between the start and the end timestamps of the user action.

The end timestamp of the user action, in UTC milliseconds.

The first input delay (FID) is the time (in milliseconds) that the browser took to respond to the first user input.

The FID is an important user-centric metric for measuring load responsiveness. It quantifies the user experience when trying to interact with unresponsive pages. A low FID indicates that the page is usable.

The time spent waiting for resources from the originating server for the user action, in milliseconds.

The number of resources fetched from the originating server for the user action.

The amount of time spent on the frontend rendering for the user action, in milliseconds.

The user action has (true) or doesn't have (false) a crash.

The Dynatrace entity ID of the application where the user action has been recorded.

This information is useful when calling various REST APIs, for example as a key for time series queries.

The Dynatrace entity ID of the key user action.

The total number of Javascript errors during the user action.

The action is (true) or is not (false) a key action.

The largest contentful paint (LCP) is the time (in milliseconds) that the largest element on the page took to render.

The LCP is an important user-centric metric for measuring load speed. It marks the point when the page's main content is likely loaded. A low LCP indicates that the page loads quickly.

The amount of time until the load event ended, in milliseconds.

The amount of time until the load event started, in milliseconds.

A list of custom properties of the user session with integer (short or long) values.

A list of conversion goals achieved by the user action.

Additionally, you can define conversion goals for a user session as a whole.

The name of the user action.

Typically, this is the name of the page that is loaded as part of a user action or a textual description of the action, such as a mouse click.

The timestamp of the navigation start, in UTC milliseconds.

The amount of time spent on the data transfer for the user action, in milliseconds.

The total number of request errors during the user action.

The amount of time until the request started, in milliseconds.

The amount of time until the response ended, in milliseconds.

The amount of time until the response started, in milliseconds.

The amount of time spent on the server-side processing for the user action, in milliseconds.

The speed index of the user action, in milliseconds.

This is calculated as average time it takes for all visible parts of a page to display.

The start timestamp of the user action, in UTC milliseconds.

A list of custom properties of the user session with string values.

The name of the Synthetic event that triggered the user action.

The ID of the Synthetic event that triggered the user action.

The target URL of the user action.

The time spent waiting for third party resources for the user action, in milliseconds.

The number of third party resources loaded for the user action.

DEPRECATED

The total blocking time is the total time (in milliseconds) between the first contentful paint and the time to interactive, during which the browser has been blocked long enough to prevent input responsiveness.

The type of the user action.

The total number of properties in the user action.

The amount of time until the page is visually complete, in milliseconds.