Navigation-related events

Latest Dynatrace
Reference

Navigation-related events encompass navigations, app starts, visibility changes, as well as page and view summary events. These events capture information about how users navigate through the application.

Application start

An application start event represents the initialization of a mobile application and measures the time it takes for the first view to become visible after the app is launched by a user. Dynatrace RUM classifies each start as cold, warm, or hot based on the app's process state at launch time. Only supported by OneAgent for Mobile.

Query

This query searches for all application starts.

fetch user.events
| filter characteristics.has_app_start == true

Application start characteristic fields

Attribute	Type	Description	Examples
`characteristics.classifier`	string	experimentalFixed value `app_start`.	`app_start`
`characteristics.has_app_start`	boolean	stableFixed value `true`.	`true`
`characteristics.has_navigation`	boolean	stableFixed value `true`.	`true`
`characteristics.has_visibility_change`	boolean	stableOptional value `true` if `visibility.state` could be detected.	`true`

Application start fields

Attribute	Type	Description	Examples
`app_start.type`	string	experimentalThe type of app start.	`cold`; `warm`; `hot`
`app_start.start_time`	duration	experimentalThe start time of the App Start. The value is relative to `start_time`.	`0`
`app_start.end_time`	duration	experimentalThe end time of the App Start. The value is relative to `start_time`.	`253`

app_start.type MUST be one of the following:

Value	Description
`cold`	A cold app start means that the app started from scratch. For example, this happens in case the app launched for the first time since the device booted.
`hot`	A hot app start has lower overhead than a cold or warm start. If the app state still resided in memory, operations such as object initialization, layout inflation, and rendering may be avoided.
`warm`	A warm app start encompasses a subset of the operations that take place during a cold start. For example, this can happen if the user backs out of the app but then re-launches it. This may differ significantly depending on the platform.

Application start Android fields

OneAgent for Mobile sends native Android and cross platform app start attributes in a single event for cross platform implementations.

Attribute	Type	Description	Examples
`app_start.android.application.on_create.start_time`	duration	experimentalThe start time of the phase from `Application.onCreate` to the first `Activity.onCreate`. The value is relative to `start_time`.	`0`
`app_start.android.application.on_create.end_time`	duration	experimentalThe end time of the phase from `Application.onCreate` to the first `Activity.onCreate`. The value is relative to `start_time`.	`123`
`app_start.android.activity.on_create.start_time`	duration	experimentalThe start time of the phase from `Activity.onCreate` to the first `Activity.onStart`. The value is relative to `start_time`.	`123`
`app_start.android.activity.on_create.end_time`	duration	experimentalThe end time of the phase from `Activity.onCreate` to the first `Activity.onStart`. The value is relative to `start_time`.	`456`
`app_start.android.activity.on_start.start_time`	duration	experimentalThe start time of the phase from `Activity.onStart` to the first `Activity.onResume`. The value is relative to `start_time`.	`456`
`app_start.android.activity.on_start.end_time`	duration	experimentalThe end time of the phase from `Activity.onStart` to the first `Activity.onResume`. The value is relative to `start_time`.	`789`
`app_start.android.activity.on_resume.start_time`	duration	experimentalThe start time for phase going from `Activity.onResume` to Activity running state. The value is relative to `start_time`.	`789`
`app_start.android.activity.on_resume.end_time`	duration	experimentalThe end time for phase going from `Activity.onResume` to Activity running state. The value is relative to `start_time`.	`890`

Application start iOS fields

OneAgent for Mobile sends native iOS and cross platform app start attributes in a single event for cross platform implementations.

Attribute	Type	Description	Examples
`app_start.ios.pre_runtime_init.start_time`	duration	experimentalThe start time for the system interface phase, which goes from `processStartTime` to `loadTime`. The value is relative to `start_time`.	`0`
`app_start.ios.pre_runtime_init.end_time`	duration	experimentalThe end time for the system interface phase, which goes from `processStartTime` to `loadTime`. The value is relative to `start_time`.	`123`
`app_start.ios.runtime_init.start_time`	duration	experimentalThe start time for the runtime init phase, which goes from `loadTime` to `app init`. The value is relative to `start_time`.	`123`
`app_start.ios.runtime_init.end_time`	duration	experimentalThe end time for the runtime init phase, which goes from `loadTime` to `app init`. The value is relative to `start_time`.	`456`
`app_start.ios.uikit_init.start_time`	duration	experimentalThe start time for the UIKit init phase, which goes from `app init` to `applicationWillFinishLaunching`. The value is relative to `start_time`.	`456`
`app_start.ios.uikit_init.end_time`	duration	experimentalThe end time for the UIKit init phase, which goes from `app init` to `applicationWillFinishLaunching`. The value is relative to `start_time`.	`789`
`app_start.ios.application_init.start_time`	duration	experimentalThe start time for application init phase, which goes from `applicationWillFinishLaunching` to `loadView`. The value is relative to `start_time`.	`789`
`app_start.ios.application_init.end_time`	duration	experimentalThe end time for application init phase, which goes from `applicationWillFinishLaunching` to `loadView`. The value is relative to `start_time`.	`1234`
`app_start.ios.initial_frame_render.start_time`	duration	experimentalThe start time for initial frame renderer phase, which goes from `loadView` or `applicationWillEnterForeground` for hot starts to `applicationDidBecomeActive`. The value is relative to `start_time`.	`1234`
`app_start.ios.initial_frame_render.end_time`	duration	experimentalThe end time for the initial frame renderer phase, which goes from `loadView` or `applicationWillEnterForeground` for hot starts to `applicationDidBecomeActive`. The value is relative to `start_time`.	`1567`

Application start Flutter fields

Attribute	Type	Description	Examples
`app_start.flutter.pre_plugin_init.start_time`	duration	experimentalThe start time for the Flutter engine initialization phase, which triggers the init of the Dynatrace plugin. The value is relative to `start_time`.	`0`
`app_start.flutter.pre_plugin_init.end_time`	duration	experimentalThe end time for the Flutter engine initialization phase, which triggers the init of the Dynatrace plugin. The value is relative to `start_time`.	`123`
`app_start.flutter.main_init.start_time`	duration	experimentalThe start time for the main init phase, which includes the main function call and Dynatrace functionality setup. The value is relative to `start_time`.	`123`
`app_start.flutter.main_init.end_time`	duration	experimentalThe end time for the main init phase, which includes the main function call and Dynatrace functionality setup. The value is relative to `start_time`.	`456`

Application start React Native fields

Attribute	Type	Description	Examples
`app_start.react_native.run_js_bundle.load_time`	duration	experimentalThe point in time when the bridge is started, essentially when a load or reload happens. The value is relative to `start_time`.	`3`
`app_start.react_native.download.start_time`	duration	experimentalOnly available in development. The start time of the development bundle download phase. The value is relative to `start_time`.	`112`
`app_start.react_native.download.end_time`	duration	experimentalOnly available in development. The end time of the development bundle download phase. The value is relative to `start_time`.	`123`
`app_start.react_native.run_js_bundle.start_time`	duration	experimentalThe start time for the React Native JavaScript bundle loading phase. The value is relative to `start_time`.	`134`
`app_start.react_native.run_js_bundle.end_time`	duration	experimentalThe end time for the React Native JavaScript bundle loading phase. The value is relative to `start_time`.	`135`
`app_start.react_native.content_appeared`	duration	experimentalThe point in time when the initial component is mounted. The value is relative to `start_time`.	`1234`

Basic user event fields

The basic attributes for all user events are defined in the user event base model.

A navigation event marks the transition to a new view. Supported by RUM JavaScript and OneAgent for Mobile.

Query

This query searches for all navigation events.

fetch user.events
| filter characteristics.has_navigation

Attribute	Type	Description	Examples
`characteristics.classifier`	string	experimentalFixed value `navigation`.	`navigation`
`characteristics.has_navigation`	boolean	stableFixed value `true`.	`true`

User action status fields

Attribute	Type	Description	Examples
`user_action.status`	string	experimentalIndicates why no corresponding user action was created for this event. Only available for hard navigations and only supported by RUM JavaScript.	`not_initialized`

Attribute	Type	Description	Examples
`navigation.type`	string	experimentalThe navigation type.	`hard`
`navigation.tab_state`	string	experimentalGives additional information about the browser tab.	`new`

navigation.type MUST be one of the following:

Value	Description
`hard`	A hard navigation reloads the entire page by fetching it from the server.
`soft`	A soft navigation only updates parts of the webpage dynamically without a full reload.

navigation.tab_state MUST be one of the following:

Value	Description
`duplicated`	Navigation through the browser's `Duplicate Tab` functionality.
`existing`	Navigation within an existing tab.
`existing_invalid`	Navigation within an existing tab but the available tab ID was invalid. This can happen if the RUM JavaScript's browser storage state is externally modified.
`new`	First navigation or navigation through the browser's `Open in New Tab` functionality.

Attribute	Type	Description	Examples
`view.sequence_number`	long	experimentalThe number of views throughout the page's lifespan up to now. This is incremented consecutively with each navigation.	`1`

Attribute	Type	Description	Examples
`page.source.url.domain`	string	experimentalThe URI host component of the source page URL. This is extracted from `page.source.url.full`.	`www.foo.bar`
`page.source.url.fragment`	string	experimentalThe URI fragment component of the source page URL. This is extracted from `page.source.url.full`.	`#dashboard;id=cff3752c-890d-4795-9955-3e1108fe3f6e;gf=all;gtf=-2h`
`page.source.url.full`	string	experimentalThe page URL of the previous page, provided in the format `scheme://host[:port]/path[?query][#fragment]`. This value is captured using `document.referrer` and may be missing or incomplete.	`https://www.foo.bar/path?q=value#dashboard;id=cff3752c-890d-4795-9955-3e1108fe3f6e;gf=all;gtf=-2h`
`page.source.url.path`	string	experimentalThe URI path component of the source page URL. This is extracted from `page.source.url.full`.	`/path`
`page.source.url.query`	string	experimentalThe URI query component of the source page URL. This is extracted from `page.source.url.full`.	`q=value`
`page.source.url.scheme`	string	experimentalThe URI scheme component of the source page URL. This is extracted from `page.source.url.full`.	`https`; `http`

Basic user event fields

The basic attributes for all user events are defined in the user event base model.

Page summary

A page represents a single HTML document and all events that occur during its lifetime. A page instance begins with each hard navigation and ends when the next document request starts or when the tab is closed. A page summary event is emitted when the page instance ends and aggregates all captured data for that page instance. Only supported by RUM JavaScript.

Query

This query searches for all page summaries.

fetch user.events
| filter characteristics.has_page_summary == true

Page summary characteristics fields

Attribute	Type	Description	Examples
`characteristics.classifier`	string	experimentalFixed value `page_summary`.	`page_summary`
`characteristics.has_page_summary`	boolean	stableFixed value `true`.	`true`

User action status fields

Attribute	Type	Description	Examples
`user_action.status`	string	experimentalIndicates why no corresponding user action was created for this event. Only supported by RUM JavaScript.	`not_initialized`

user_action.status MUST be one of the following:

Value	Description
`not_enabled`	The RUM JavaScript was enabled after the `onload` event fired.
`not_initialized`	The RUM JavaScript was initialized after the `onload` event fired.

Page summary performance fields

Attribute	Type	Description	Examples
`performance.activation_start`	duration	experimentalThe time when a prerendered document is activated. The value is relative to `performance.start_time`. This is an experimental feature that is only available in some browsers.	`0`
`performance.time_origin`	timestamp	experimentalThe timestamp of the beginning of the current page's lifetime in client time. The value is a UNIX Epoch time in nanoseconds.	`1667469141402000000`

Error fields

Attribute	Type	Description	Examples
`error.csp_violation_count`	long	experimentalThe number of CSP rule violations.	`1`
`error.dropped_exception_count`	long	experimentalThe number of exceptions that are observed, but which are not captured due to error capture limits.	`1`
`error.exception_count`	long	experimentalThe total number of exceptions that are observed, including exceptions that are not captured.	`1`
`error.http_4xx_count`	long	experimentalThe number of HTTP request errors with an `http.response.status_code` of 400-499.	`1`
`error.http_5xx_count`	long	experimentalThe number of HTTP request errors with an `http.response.status_code` of 500-599.	`1`
`error.http_other_count`	long	experimentalThe number of HTTP request errors with an `http.response.status_code` of 0-99 or 600+ (undefined errors).	`1`

Page summary page fields

Attribute	Type	Description	Examples
`page.background_time`	duration	experimentalThe aggregated time that the page was in the background.	`0`
`page.foreground_time`	duration	experimentalThe aggregated time that the page was in the foreground.	`900000000`
`page.prerender_time`	duration	experimentalThe aggregated time that the page was prerendering.	`0`

Attribute	Type	Description	Examples
`navigation.type`	string	experimentalThe navigation type.	`hard`
`navigation.tab_state`	string	experimentalGives additional information about the browser tab.	`new`

navigation.type MUST be one of the following:

Value	Description
`hard`	A hard navigation reloads the entire page by fetching it from the server.
`soft`	A soft navigation only updates parts of the webpage dynamically without a full reload.

navigation.tab_state MUST be one of the following:

Value	Description
`duplicated`	Navigation through the browser's `Duplicate Tab` functionality.
`existing`	Navigation within an existing tab.
`existing_invalid`	Navigation within an existing tab but the available tab ID was invalid. This can happen if the RUM JavaScript's browser storage state is externally modified.
`new`	First navigation or navigation through the browser's `Open in New Tab` functionality.

Web vitals fields

The web vitals fields contain the web vitals attributes captured by Dynatrace RUM. Only available for user events sent by RUM JavaScript.

Attribute	Type	Description	Examples
`web_vitals.largest_contentful_paint`	duration	stableThe `Largest Contentful Paint` (LCP) value.	`880000000`
`web_vitals.first_contentful_paint`	duration	stableThe `First Contentful Paint` (FCP) value.	`92000000`
`web_vitals.first_input_delay`	duration	stableThe `First Input Delay` (FID) value.	`6000000`
`web_vitals.cumulative_layout_shift`	double	stableThe `Cumulative Layout Shift` (CLS) value.	`0.1279`
`web_vitals.interaction_to_next_paint`	duration	stableThe `Interaction to Next Paint` (INP) value.	`190000000`
`web_vitals.first_input`	duration	stableThe `First Input` value.	`6000000`
`web_vitals.first_paint`	duration	stableThe `First Paint` value.	`92451200`
`web_vitals.time_to_first_byte`	duration	stableThe `Time to First Byte` value.	`92000000`

Largest Contentful Paint (LCP) fields

The Largest Contentful Paint (LCP) attributes contain additional information about the captured web_vitals.largest_contentful_paint.

Attribute	Type	Description	Examples
`lcp.status`	string	experimentalThe status information for LCP.	`reported`
`lcp.update_count`	long	experimentalThe number of LCP updates during the entire lifespan.	`0`
`lcp.start_time`	double	experimentalThe value of the LCP object's `startTime` property. The unit is milliseconds.	`880.0`
`lcp.url`	string	experimentalIf the element is an image, the request URL of the image.	`https://www.foo.bar/images/image.png`
`lcp.load_time`	double	experimentalThe value of the LCP object's `loadTime` property (the time the element was loaded). The unit is milliseconds. In case the element finished to load but the browser did not render it yet, a negative value is reported.	`874.0`
`lcp.render_time`	double	experimentalThe value of the LCP object's `renderTime` property (the time that the element was rendered). The unit is milliseconds.	`880.0`
`lcp.size`	long	experimentalThe intrinsic size of the element representing its area on the screen. The value is equal to the element's width multiplied by its height, in pixels.	`53640`
`lcp.id`	string	experimentalThe element's ID.	`productLogo`
`lcp.ui_element.xpath`	string[]	experimentalThe element's xpath. Might be missing, for example, for element's that are inside a shadow DOM.	`['html[1]', 'body[1]', 'div[@id="elementId"]', 'section[1]', 'form[1]', 'div[5]', 'button[1]']`
`lcp.ui_element.tag_name`	string	experimentalThe element's tag name. Might be missing, for example, for element's that are inside a shadow DOM.	`BUTTON`
`lcp.ui_element.render_delay`	double	experimentalThe element's render delay, that is the time between when the element finishes loading and when it is fully rendered. The unit is milliseconds. Only available if a resource timing is available for the element.	`100.0`
`lcp.resource.load_delay`	double	experimentalThe resource's load delay, that is the time between `Time to First Byte` and when the browser starts loading the resource. The unit is milliseconds. Only available if a resource timing is available for the resource.	`400.0`
`lcp.resource.load_duration`	double	experimentalThe resource's load duration, that is the total time it takes to load the resource. The unit is milliseconds. Only available if a resource timing is available for the resource.	`300.0`

lcp.status MUST be one of the following:

Value	Description
`backgrounded`	LCP is not reported because the browser tab was loaded in the background.
`disabled`	LCP is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_supported`	LCP is not reported because the browser tab was in the background before the value could be reported.
`reported`	LCP is reported.

First Input Delay (FID) fields

The First Input Delay (FID) attributes contain additional information about the captured web_vitals.first_input_delay.

Attribute	Type	Description	Examples
`fid.status`	string	experimentalThe status information for FID.	`not_reported`
`fid.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the FID was captured.	`complete`
`fid.start_time`	double	experimentalThe value of the FID object's `startTime` property. The unit is milliseconds.	`13427.0`
`fid.duration`	double	experimentalThe value of the FID object's `duration` property. The unit is milliseconds.	`24.0`
`fid.name`	string	experimentalThe value of the FID object's `name` property (the user interaction event).	`click`
`fid.processing_start`	double	experimentalThe value of the FID object's `processingStart` property. The unit is milliseconds.	`13433.0`
`fid.processing_end`	double	experimentalThe value of the FID object's `processingEnd` property. The unit is milliseconds.	`13433.0`
`fid.processing_duration`	double	experimentalHow long it took for the event handler to execute. This is calculated as `fid.processing_end` minus `fid.processing_start`.	`0.0`
`fid.cancelable`	boolean	experimentalThe value of the FID object's `cancelable` property.	`true`
`fid.ui_element.xpath`	string[]	experimentalThe element's xpath. Might be missing, for example, for element's that are inside a shadow DOM.	`['html[1]', 'body[1]', 'div[@id="elementId"]', 'section[1]', 'form[1]', 'div[5]', 'button[1]']`
`fid.ui_element.tag_name`	string	experimentalThe element's tag name. Might be missing, for example, for element's that are inside a shadow DOM.	`BUTTON`

fid.status MUST be one of the following:

Value	Description
`disabled`	FID is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_reported`	FID is not reported because there was no user interaction.
`not_supported`	FID is not supported by the browser.
`reported`	FID is reported.

fid.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

Interaction to Next Paint (INP) fields

The Interaction to Next Paint (INP) attributes contain additional information about the captured web_vitals.interaction_to_next_paint.

Attribute	Type	Description	Examples
`inp.status`	string	experimentalThe status information for INP.	`reported`
`inp.update_count`	long	experimentalThe number of INP updates during the entire lifespan.	`0`
`inp.interaction_count`	long	experimentalThe number of interactions, during the entire lifespan, that exceed 40 milliseconds.	`0`
`inp.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the INP was captured.	`complete`
`inp.start_time`	double	experimentalThe value of the INP object's `startTime` property. The unit is milliseconds.	`13427.0`
`inp.duration`	double	experimentalThe value of the INP object's `duration` property. The unit is milliseconds.	`24.0`
`inp.name`	string	experimentalThe value of the INP object's `name` property (the user interaction event).	`click`
`inp.processing_start`	double	experimentalThe value of the INP object's `processingStart` property. The unit is milliseconds.	`13433.0`
`inp.processing_end`	double	experimentalThe value of the INP object's `processingEnd` property. The unit is milliseconds.	`13433.0`
`inp.processing_duration`	double	experimentalHow long it took for the event handler to execute. This is calculated as `inp.processing_end` minus `inp.processing_start`.	`0.0`
`inp.cancelable`	boolean	experimentalThe value of the INP object's `cancelable` property.	`true`
`inp.ui_element.xpath`	string[]	experimentalThe element's xpath. Might be missing, for example, for element's that are inside a shadow DOM.	`['html[1]', 'body[1]', 'div[@id="elementId"]', 'section[1]', 'form[1]', 'div[5]', 'button[1]']`
`inp.ui_element.tag_name`	string	experimentalThe element's tag name. Might be missing, for example, for element's that are inside a shadow DOM.	`BUTTON`

inp.status MUST be one of the following:

Value	Description
`below_threshold`	INP is not reported because the value is below the threshold of 40 milliseconds.
`disabled`	INP is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_reported`	INP is not reported because no relevant user interaction happened.
`not_supported`	INP is not supported by the browser.
`reported`	INP is reported.

inp.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

First Contentful Paint (FCP) fields

The First Contentful Paint (FCP) attributes contain additional information about the captured web_vitals.first_contentful_paint.

Attribute	Type	Description	Examples
`fcp.status`	string	experimentalThe status information for FCP.	`reported`
`fcp.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the FCP was captured.	`complete`
`fcp.value`	double	experimentalThe value of the FCP object's `startTime` property. The unit is milliseconds.	`92.0`

fcp.status MUST be one of the following:

Value	Description
`backgrounded`	FCP is not reported because the browser tab was in the background before the value could be reported.
`not_reported`	FCP is not reported because no content was rendered.
`not_supported`	FCP is not supported by the browser.
`reported`	FCP is reported.

fcp.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

Cumulative Layout Shift (CLS) fields

The Cumulative Layout Shift (CLS) attributes contain additional information about the captured web_vitals.cumulative_layout_shift.

Attribute	Type	Description	Examples
`cls.status`	string	experimentalThe status information for CLS.	`not_supported`
`cls.update_count`	long	experimentalThe number of CLS updates during the entire lifespan.	`0`
`cls.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the CLS was captured.	`complete`
`cls.value`	double	experimentalThe final CLS value.	`0.1279`
`cls.ui_element.xpath`	string[]	experimentalThe xpath of the element causing the largest layout shift. Might be missing, for example, for elements that are inside a shadow DOM.	`['html[1]', 'body[1]', 'div[@id="elementId"]', 'section[1]', 'form[1]', 'div[5]', 'button[1]']`
`cls.ui_element.tag_name`	string	experimentalThe tag name of the element causing the largest layout shift. Might be missing, for example, for elements that are inside a shadow DOM.	`BUTTON`
`cls.ui_element.shift_time`	double	experimentalThe time when the largest layout shift occurred. The value is relative to `start_time`. The unit is milliseconds.	`2066.9`
`cls.ui_element.shift_value`	double	experimentalThe layout shift score of the element causing the largest layout shift.	`0.11`

cls.status MUST be one of the following:

Value	Description
`backgrounded`	CLS is not reported because the page was loaded in the background or backgrounded before the browser painted any content.
`disabled`	CLS is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_supported`	CLS is not supported by the browser.
`reported`	CLS is reported.

cls.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

First Paint (FP) fields

The First Paint (FP) attributes contain additional information about the captured web_vitals.first_paint.

Attribute	Type	Description	Examples
`fp.status`	string	experimentalThe status information for FP.	`reported`
`fp.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the FP was captured.	`complete`
`fp.value`	double	experimentalThe value of the FP object's `startTime` property (the FP value). The unit is milliseconds.	`92.0`

fp.status MUST be one of the following:

Value	Description
`backgrounded`	FP is not reported because the browser tab was in the background before the value could be reported.
`not_reported`	FP is not reported because no content was rendered.
`not_supported`	FP is not supported by the browser.
`reported`	FP is reported.

fp.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

Time to First Byte (TTFB) fields

The Time to First Byte (TTFB) attributes contain additional information about the captured web_vitals.time_to_first_byte.

Attribute	Type	Description	Examples
`ttfb.status`	string	experimentalThe status information for TTFB.	`reported`
`ttfb.value`	double	experimentalThe `responseStart` value of the navigation timing. The unit is milliseconds.	`92.0`
`ttfb.waiting_duration`	double	experimentalThe total time from when the user initiates loading to when the navigation request is handled, that is the `workerStart` or `fetchStart` value of the navigation timing. Long waiting durations are usually caused by HTTP redirects. The unit is milliseconds.	`4.2`
`ttfb.cache_duration`	double	experimentalThe total time spent checking the HTTP cache for a match, that is the `domainLookupStart` value of the navigation timing minus `ttfb.waiting_duration`. The unit is milliseconds.	`10.12`
`ttfb.dns_duration`	double	experimentalThe total time to resolve the DNS for the requested domain, that is the `connectStart` value minus the `domainLookupStart` value of the navigation timing. The unit is milliseconds.	`3.3`
`ttfb.connection_duration`	double	experimentalThe total time to create the connection to the requested domain, that is the `connectEnd` value minus the `connectStart` value of the navigation timing. The unit is milliseconds.	`20.1`
`ttfb.request_duration`	double	experimentalThe total time from when the request was sent until the first byte of the response was received, that is the `responseStart` value minus the `connectEnd` value of the navigation timing. The value includes network time and server processing time. The unit is milliseconds.	`30.1`

ttfb.status MUST be one of the following:

Value	Description
`not_reported`	TTFB is not reported by the browser.
`reported`	TTFB is reported.

Long task fields

Attribute	Type	Description	Examples
`long_task.status`	string	experimentalThe status information for long task information.	`not_supported`
`long_task.all.count`	long	experimentalThe number of all long tasks observed during the entire lifespan.	`2`
`long_task.all.avg_duration`	long	experimentalThe average duration of all observed long tasks in milliseconds.	`60`
`long_task.all.slowest_occurrences`	record[]	experimentalThe start time and the duration of the slowest observed long tasks in milliseconds. The start time is relative to the user event's `start_time`.	`{'duration': 60, 'start_time': 1234}`; `{'duration': 58, 'start_time': 2999}`
`long_task.self.count`	long	experimentalThe number of long tasks from the same browser context or frame observed during the entire lifespan. Only long tasks with `long_task.name` set to `self` are considered.	`2`
`long_task.self.avg_duration`	long	experimentalThe average duration of the observed long tasks from the same browser context or frame in milliseconds. Only long tasks with `long_task.name` set to `self` are considered.	`60`
`long_task.self.slowest_occurrences`	record[]	experimentalThe start time and the duration of the slowest observed long tasks from the same browser context or frame in milliseconds. The start time is relative to the user event's `start_time`. Only long tasks with `long_task.name` set to `self` are considered.	`{'duration': 60, 'start_time': 1234}`; `{'duration': 58, 'start_time': 2999}`

long_task.status MUST be one of the following:

Value	Description
`disabled`	Long task information is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_reported`	Long task information is not reported because no long task was observed.
`not_supported`	Long tasks API is not supported by the browser.
`reported`	Long task information is reported.

Basic user event fields

The basic attributes for all user events are defined in the user event base model.

View summary

A view represents the content displayed to a user at a given time. On web, a new view instance begins with every navigation, whether it is a hard navigation (full page load) or a soft navigation (SPA route change). On mobile, a view corresponds to a distinct screen displayed to the user. A view summary event is emitted when the view instance ends and aggregates all captured data for that view instance. Supported by RUM JavaScript and OneAgent for Mobile.

Query

This query searches for all view summaries.

fetch user.events
| filter characteristics.has_view_summary == true

View summary characteristics fields

Attribute	Type	Description	Examples
`characteristics.classifier`	string	experimentalFixed value `view_summary`.	`view_summary`
`characteristics.has_view_summary`	boolean	stableFixed value `true`.	`true`

User action status fields

Attribute	Type	Description	Examples
`user_action.status`	string	experimentalIndicates why no corresponding user action was created for this event. Only supported by RUM JavaScript.	`not_initialized`

user_action.status MUST be one of the following:

Value	Description
`not_enabled`	The RUM JavaScript was enabled after the `onload` event fired.
`not_initialized`	The RUM JavaScript was initialized after the `onload` event fired.

View summary performance fields

Only available for user events sent by RUM JavaScript.

Attribute	Type	Description	Examples
`performance.activation_start`	duration	experimentalThe time when a prerendered document is activated. The value is relative to `performance.start_time`. This is an experimental feature that is only available in some browsers.	`0`
`performance.time_origin`	timestamp	experimentalThe timestamp of the beginning of the current page's lifetime in client time. The value is a UNIX Epoch time in nanoseconds.	`1667469141402000000`

Error fields

Attribute	Type	Description	Examples
`error.csp_violation_count`	long	experimentalThe number of CSP rule violations.	`1`
`error.dropped_exception_count`	long	experimentalThe number of exceptions that are observed, but which are not captured due to error capture limits.	`1`
`error.exception_count`	long	experimentalThe total number of exceptions that are observed, including exceptions that are not captured.	`1`
`error.http_4xx_count`	long	experimentalThe number of HTTP request errors with an `http.response.status_code` of 400-499.	`1`
`error.http_5xx_count`	long	experimentalThe number of HTTP request errors with an `http.response.status_code` of 500-599.	`1`
`error.http_other_count`	long	experimentalThe number of HTTP request errors with an `http.response.status_code` of 0-99 or 600+ (undefined errors).	`1`

View fields

Attribute	Type	Description	Examples
`view.background_time`	duration	experimentalAggregated time that the view was in the background.	`0`
`view.foreground_time`	duration	experimentalAggregated time that the view was in the foreground.	`900000000`
`view.prerender_time`	duration	experimentalAggregated time that the view was prerendering.	`0`
`view.sequence_number`	long	experimentalThe number of views throughout the page's entire lifespan.	`1`

Attribute	Type	Description	Examples
`navigation.type`	string	experimentalThe navigation type.	`hard`
`navigation.tab_state`	string	experimentalGives additional information about the browser tab.	`new`

navigation.type MUST be one of the following:

Value	Description
`hard`	A hard navigation reloads the entire page by fetching it from the server.
`soft`	A soft navigation only updates parts of the webpage dynamically without a full reload.

navigation.tab_state MUST be one of the following:

Value	Description
`duplicated`	Navigation through the browser's `Duplicate Tab` functionality.
`existing`	Navigation within an existing tab.
`existing_invalid`	Navigation within an existing tab but the available tab ID was invalid. This can happen if the RUM JavaScript's browser storage state is externally modified.
`new`	First navigation or navigation through the browser's `Open in New Tab` functionality.

Web vitals fields

The web vitals fields contain the web vitals attributes captured by Dynatrace RUM. Only available for user events sent by RUM JavaScript.

Attribute	Type	Description	Examples
`web_vitals.largest_contentful_paint`	duration	stableThe `Largest Contentful Paint` (LCP) value.	`880000000`
`web_vitals.first_contentful_paint`	duration	stableThe `First Contentful Paint` (FCP) value.	`92000000`
`web_vitals.first_input_delay`	duration	stableThe `First Input Delay` (FID) value.	`6000000`
`web_vitals.cumulative_layout_shift`	double	stableThe `Cumulative Layout Shift` (CLS) value.	`0.1279`
`web_vitals.interaction_to_next_paint`	duration	stableThe `Interaction to Next Paint` (INP) value.	`190000000`
`web_vitals.first_input`	duration	stableThe `First Input` value.	`6000000`
`web_vitals.first_paint`	duration	stableThe `First Paint` value.	`92451200`
`web_vitals.time_to_first_byte`	duration	stableThe `Time to First Byte` value.	`92000000`

Largest Contentful Paint (LCP) fields

The Largest Contentful Paint (LCP) attributes contain additional information about the captured web_vitals.largest_contentful_paint.

Attribute	Type	Description	Examples
`lcp.status`	string	experimentalThe status information for LCP.	`reported`
`lcp.update_count`	long	experimentalThe number of LCP updates during the entire lifespan.	`0`
`lcp.start_time`	double	experimentalThe value of the LCP object's `startTime` property. The unit is milliseconds.	`880.0`
`lcp.url`	string	experimentalIf the element is an image, the request URL of the image.	`https://www.foo.bar/images/image.png`
`lcp.load_time`	double	experimentalThe value of the LCP object's `loadTime` property (the time the element was loaded). The unit is milliseconds. In case the element finished to load but the browser did not render it yet, a negative value is reported.	`874.0`
`lcp.render_time`	double	experimentalThe value of the LCP object's `renderTime` property (the time that the element was rendered). The unit is milliseconds.	`880.0`
`lcp.size`	long	experimentalThe intrinsic size of the element representing its area on the screen. The value is equal to the element's width multiplied by its height, in pixels.	`53640`
`lcp.id`	string	experimentalThe element's ID.	`productLogo`
`lcp.ui_element.xpath`	string[]	experimentalThe element's xpath. Might be missing, for example, for element's that are inside a shadow DOM.	`['html[1]', 'body[1]', 'div[@id="elementId"]', 'section[1]', 'form[1]', 'div[5]', 'button[1]']`
`lcp.ui_element.tag_name`	string	experimentalThe element's tag name. Might be missing, for example, for element's that are inside a shadow DOM.	`BUTTON`
`lcp.ui_element.render_delay`	double	experimentalThe element's render delay, that is the time between when the element finishes loading and when it is fully rendered. The unit is milliseconds. Only available if a resource timing is available for the element.	`100.0`
`lcp.resource.load_delay`	double	experimentalThe resource's load delay, that is the time between `Time to First Byte` and when the browser starts loading the resource. The unit is milliseconds. Only available if a resource timing is available for the resource.	`400.0`
`lcp.resource.load_duration`	double	experimentalThe resource's load duration, that is the total time it takes to load the resource. The unit is milliseconds. Only available if a resource timing is available for the resource.	`300.0`

lcp.status MUST be one of the following:

Value	Description
`backgrounded`	LCP is not reported because the browser tab was loaded in the background.
`disabled`	LCP is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_supported`	LCP is not reported because the browser tab was in the background before the value could be reported.
`reported`	LCP is reported.

First Input Delay (FID) fields

The First Input Delay (FID) attributes contain additional information about the captured web_vitals.first_input_delay.

Attribute	Type	Description	Examples
`fid.status`	string	experimentalThe status information for FID.	`not_reported`
`fid.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the FID was captured.	`complete`
`fid.start_time`	double	experimentalThe value of the FID object's `startTime` property. The unit is milliseconds.	`13427.0`
`fid.duration`	double	experimentalThe value of the FID object's `duration` property. The unit is milliseconds.	`24.0`
`fid.name`	string	experimentalThe value of the FID object's `name` property (the user interaction event).	`click`
`fid.processing_start`	double	experimentalThe value of the FID object's `processingStart` property. The unit is milliseconds.	`13433.0`
`fid.processing_end`	double	experimentalThe value of the FID object's `processingEnd` property. The unit is milliseconds.	`13433.0`
`fid.processing_duration`	double	experimentalHow long it took for the event handler to execute. This is calculated as `fid.processing_end` minus `fid.processing_start`.	`0.0`
`fid.cancelable`	boolean	experimentalThe value of the FID object's `cancelable` property.	`true`
`fid.ui_element.xpath`	string[]	experimentalThe element's xpath. Might be missing, for example, for element's that are inside a shadow DOM.	`['html[1]', 'body[1]', 'div[@id="elementId"]', 'section[1]', 'form[1]', 'div[5]', 'button[1]']`
`fid.ui_element.tag_name`	string	experimentalThe element's tag name. Might be missing, for example, for element's that are inside a shadow DOM.	`BUTTON`

fid.status MUST be one of the following:

Value	Description
`disabled`	FID is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_reported`	FID is not reported because there was no user interaction.
`not_supported`	FID is not supported by the browser.
`reported`	FID is reported.

fid.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

Interaction to Next Paint (INP) fields

The Interaction to Next Paint (INP) attributes contain additional information about the captured web_vitals.interaction_to_next_paint.

Attribute	Type	Description	Examples
`inp.status`	string	experimentalThe status information for INP.	`reported`
`inp.update_count`	long	experimentalThe number of INP updates during the entire lifespan.	`0`
`inp.interaction_count`	long	experimentalThe number of interactions, during the entire lifespan, that exceed 40 milliseconds.	`0`
`inp.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the INP was captured.	`complete`
`inp.start_time`	double	experimentalThe value of the INP object's `startTime` property. The unit is milliseconds.	`13427.0`
`inp.duration`	double	experimentalThe value of the INP object's `duration` property. The unit is milliseconds.	`24.0`
`inp.name`	string	experimentalThe value of the INP object's `name` property (the user interaction event).	`click`
`inp.processing_start`	double	experimentalThe value of the INP object's `processingStart` property. The unit is milliseconds.	`13433.0`
`inp.processing_end`	double	experimentalThe value of the INP object's `processingEnd` property. The unit is milliseconds.	`13433.0`
`inp.processing_duration`	double	experimentalHow long it took for the event handler to execute. This is calculated as `inp.processing_end` minus `inp.processing_start`.	`0.0`
`inp.cancelable`	boolean	experimentalThe value of the INP object's `cancelable` property.	`true`
`inp.ui_element.xpath`	string[]	experimentalThe element's xpath. Might be missing, for example, for element's that are inside a shadow DOM.	`['html[1]', 'body[1]', 'div[@id="elementId"]', 'section[1]', 'form[1]', 'div[5]', 'button[1]']`
`inp.ui_element.tag_name`	string	experimentalThe element's tag name. Might be missing, for example, for element's that are inside a shadow DOM.	`BUTTON`

inp.status MUST be one of the following:

Value	Description
`below_threshold`	INP is not reported because the value is below the threshold of 40 milliseconds.
`disabled`	INP is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_reported`	INP is not reported because no relevant user interaction happened.
`not_supported`	INP is not supported by the browser.
`reported`	INP is reported.

inp.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

First Contentful Paint (FCP) fields

The First Contentful Paint (FCP) attributes contain additional information about the captured web_vitals.first_contentful_paint.

Attribute	Type	Description	Examples
`fcp.status`	string	experimentalThe status information for FCP.	`reported`
`fcp.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the FCP was captured.	`complete`
`fcp.value`	double	experimentalThe value of the FCP object's `startTime` property. The unit is milliseconds.	`92.0`

fcp.status MUST be one of the following:

Value	Description
`backgrounded`	FCP is not reported because the browser tab was in the background before the value could be reported.
`not_reported`	FCP is not reported because no content was rendered.
`not_supported`	FCP is not supported by the browser.
`reported`	FCP is reported.

fcp.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

Cumulative Layout Shift (CLS) fields

The Cumulative Layout Shift (CLS) attributes contain additional information about the captured web_vitals.cumulative_layout_shift.

Attribute	Type	Description	Examples
`cls.status`	string	experimentalThe status information for CLS.	`not_supported`
`cls.update_count`	long	experimentalThe number of CLS updates during the entire lifespan.	`0`
`cls.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the CLS was captured.	`complete`
`cls.value`	double	experimentalThe final CLS value.	`0.1279`
`cls.ui_element.xpath`	string[]	experimentalThe xpath of the element causing the largest layout shift. Might be missing, for example, for elements that are inside a shadow DOM.	`['html[1]', 'body[1]', 'div[@id="elementId"]', 'section[1]', 'form[1]', 'div[5]', 'button[1]']`
`cls.ui_element.tag_name`	string	experimentalThe tag name of the element causing the largest layout shift. Might be missing, for example, for elements that are inside a shadow DOM.	`BUTTON`
`cls.ui_element.shift_time`	double	experimentalThe time when the largest layout shift occurred. The value is relative to `start_time`. The unit is milliseconds.	`2066.9`
`cls.ui_element.shift_value`	double	experimentalThe layout shift score of the element causing the largest layout shift.	`0.11`

cls.status MUST be one of the following:

Value	Description
`backgrounded`	CLS is not reported because the page was loaded in the background or backgrounded before the browser painted any content.
`disabled`	CLS is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_supported`	CLS is not supported by the browser.
`reported`	CLS is reported.

cls.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

First Paint (FP) fields

The First Paint (FP) attributes contain additional information about the captured web_vitals.first_paint.

Attribute	Type	Description	Examples
`fp.status`	string	experimentalThe status information for FP.	`reported`
`fp.loading_state`	string	experimentalThe document's loading state recorded at the point in time when the FP was captured.	`complete`
`fp.value`	double	experimentalThe value of the FP object's `startTime` property (the FP value). The unit is milliseconds.	`92.0`

fp.status MUST be one of the following:

Value	Description
`backgrounded`	FP is not reported because the browser tab was in the background before the value could be reported.
`not_reported`	FP is not reported because no content was rendered.
`not_supported`	FP is not supported by the browser.
`reported`	FP is reported.

fp.loading_state MUST be one of the following:

Value	Description
`complete`	The document and all sub-resources have finished loading.
`dom_content_loaded`	The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading.
`dom_interactive`	The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading.
`loading`	The document is still loading.

The Time to First Byte (TTFB) attributes contain additional information about the captured web_vitals.time_to_first_byte.

Time to First Byte (TTFB) fields

The Time to First Byte (TTFB) attributes contain additional information about the captured web_vitals.time_to_first_byte.

Attribute	Type	Description	Examples
`ttfb.status`	string	experimentalThe status information for TTFB.	`reported`
`ttfb.value`	double	experimentalThe `responseStart` value of the navigation timing. The unit is milliseconds.	`92.0`
`ttfb.waiting_duration`	double	experimentalThe total time from when the user initiates loading to when the navigation request is handled, that is the `workerStart` or `fetchStart` value of the navigation timing. Long waiting durations are usually caused by HTTP redirects. The unit is milliseconds.	`4.2`
`ttfb.cache_duration`	double	experimentalThe total time spent checking the HTTP cache for a match, that is the `domainLookupStart` value of the navigation timing minus `ttfb.waiting_duration`. The unit is milliseconds.	`10.12`
`ttfb.dns_duration`	double	experimentalThe total time to resolve the DNS for the requested domain, that is the `connectStart` value minus the `domainLookupStart` value of the navigation timing. The unit is milliseconds.	`3.3`
`ttfb.connection_duration`	double	experimentalThe total time to create the connection to the requested domain, that is the `connectEnd` value minus the `connectStart` value of the navigation timing. The unit is milliseconds.	`20.1`
`ttfb.request_duration`	double	experimentalThe total time from when the request was sent until the first byte of the response was received, that is the `responseStart` value minus the `connectEnd` value of the navigation timing. The value includes network time and server processing time. The unit is milliseconds.	`30.1`

ttfb.status MUST be one of the following:

Value	Description
`not_reported`	TTFB is not reported by the browser.
`reported`	TTFB is reported.

Long task fields

Attribute	Type	Description	Examples
`long_task.status`	string	experimentalThe status information for long task information.	`not_supported`
`long_task.all.count`	long	experimentalThe number of all long tasks observed during the entire lifespan.	`2`
`long_task.all.avg_duration`	long	experimentalThe average duration of all observed long tasks in milliseconds.	`60`
`long_task.all.slowest_occurrences`	record[]	experimentalThe start time and the duration of the slowest observed long tasks in milliseconds. The start time is relative to the user event's `start_time`.	`{'duration': 60, 'start_time': 1234}`; `{'duration': 58, 'start_time': 2999}`
`long_task.self.count`	long	experimentalThe number of long tasks from the same browser context or frame observed during the entire lifespan. Only long tasks with `long_task.name` set to `self` are considered.	`2`
`long_task.self.avg_duration`	long	experimentalThe average duration of the observed long tasks from the same browser context or frame in milliseconds. Only long tasks with `long_task.name` set to `self` are considered.	`60`
`long_task.self.slowest_occurrences`	record[]	experimentalThe start time and the duration of the slowest observed long tasks from the same browser context or frame in milliseconds. The start time is relative to the user event's `start_time`. Only long tasks with `long_task.name` set to `self` are considered.	`{'duration': 60, 'start_time': 1234}`; `{'duration': 58, 'start_time': 2999}`

long_task.status MUST be one of the following:

Value	Description
`disabled`	Long task information is not reported because capturing of page and view summaries is disabled (only used for activity events).
`not_reported`	Long task information is not reported because no long task was observed.
`not_supported`	Long tasks API is not supported by the browser.
`reported`	Long task information is reported.

Basic user event fields

The basic attributes for all user events are defined in the user event base model.

Visibility change

A visibility change event is captured whenever the page transitions between foreground (visible) and background (hidden or minimized) states. Supported by RUM JavaScript. For OneAgent for Mobile, visibility state changes are captured as part of navigation events.

Query

This query searches for all visibility changes.

fetch user.events
| filter characteristics.has_visibility_change == true

Visibility change characteristics fields

Only available for user events sent by RUM JavaScript.

Attribute	Type	Description	Examples
`characteristics.classifier`	string	experimentalFixed value `visibility_change`.	`visibility_change`
`characteristics.has_visibility_change`	boolean	stableFixed value `true`.	`true`

Visibility fields

Visibility attributes are only available for user events sent by RUM JavaScript.

Attribute	Type	Description	Examples
`visibility.state`	string	experimentalThe visibility state.	`foreground`

visibility.state MUST be one of the following:

Value	Description
`background`	The application or browser tab is in the background and the content is not visible to the user.
`foreground`	The application or browser tab is in the foreground and the content is at least partially visible.
`prerendering`	The content is in the process of prerendering. Only supported by RUM JavaScript. Not applicable to visibility change events.
`unknown`	The visibility state of the user event cannot be determined. Only used by RUM JavaScript.

Visibility change performance fields

Only available for user events sent by RUM JavaScript.

Attribute	Type	Description	Examples
`performance.time_origin`	timestamp	experimentalThe timestamp of the beginning of the current page's lifetime in client time. The value is a UNIX Epoch time in nanoseconds.	`1667469141402000000`

Visibility change DOM event fields

Only available for user events sent by RUM JavaScript.

Attribute	Type	Description	Examples
`dom_event.is_trusted`	boolean	experimentalInteraction is genuine from real user and not a synthetic event.	`true`

Basic user event fields

The basic attributes for all user events are defined in the user event base model.

Navigation-related events

Application start

Query

Application start characteristic fields

Application start fields

Application start Android fields

Application start iOS fields

Application start Flutter fields

Application start React Native fields

Basic user event fields

Navigation

Query

Navigation characteristics fields

User action status fields

Navigation fields

Navigation view fields

Navigation source page fields

Basic user event fields

Page summary

Query

Page summary characteristics fields

User action status fields

Page summary performance fields

Error fields

Page summary page fields

Navigation fields

Web vitals fields

Largest Contentful Paint (LCP) fields

First Input Delay (FID) fields

Interaction to Next Paint (INP) fields

First Contentful Paint (FCP) fields

Cumulative Layout Shift (CLS) fields

First Paint (FP) fields

Time to First Byte (TTFB) fields

Long task fields

Basic user event fields

View summary

Query

View summary characteristics fields

User action status fields

View summary performance fields

Error fields

View fields

Navigation fields

Web vitals fields

Largest Contentful Paint (LCP) fields

First Input Delay (FID) fields

Interaction to Next Paint (INP) fields

First Contentful Paint (FCP) fields

Cumulative Layout Shift (CLS) fields

First Paint (FP) fields

Time to First Byte (TTFB) fields

Long task fields

Basic user event fields

Visibility change

Query

Visibility change characteristics fields

Visibility fields

Visibility change performance fields

Visibility change DOM event fields

Basic user event fields