Lightning Page View Event Type

Lightning Page View events represent information about the page on which the event occurred in Lightning Experience and the Salesforce mobile app, such as the page’s load time. This event type is available in the EventLogFile object in API version 39.0 and later.

For details about event monitoring, see the Trailhead Event Monitoring module or REST API Developer’s Guide.

Event Monitoring logs are a source of truth but are not durable. Data loss can occur during Salesforce site switches, instance refreshes, or unplanned outages. For more information, see Using Event Monitoring.
  • Type: String
  • Description: The name of the application that the user accessed.
  • Type: String
  • Description: The name of the browser that the user accessed.
  • Examples: Chrome, Safari
  • Type: String
  • Description: The version of the browser that the user accessed in major.minor version format. Some browsers don’t provide a minor version.
  • Type: String
  • Description: The geolocation of the client in the form of <Country>/<State|Province>.
  • Example: United States/California
  • Type: String
  • Description: The API client ID.
  • Type: String
  • Description: The IP address of the client that’s using Salesforce services. A Salesforce internal IP (such as a login from AppExchange) is shown as Salesforce.com IP.
  • Example: 96.43.144.26

  • Type: String

  • Description: The type of connection.

  • Possible values:

    • CDMA1x
    • CDMA
    • EDGE
    • EVDO0
    • EVDOA
    • EVDOB
    • GPRS
    • HRPD
    • HSDPA
    • HSUPA
    • LTE
    • WIFI
  • Type: String
  • Description: The unique identifier used to identify a device when tracking events. DEVICE_ID is a generated value that’s created when the mobile app is initially run after installation.
  • Type: String
  • Description: The name of the device model.
  • Examples: iPad, iPhone

  • Type: String

  • Description: The type of application experience in name:experience:form format.

  • Possible values:

    • name - APP_BUILDER, CUSTOM, S1, SFX
    • experience - BROWSER, HYBRID
    • form - DESKTOP, PHONE, TABLET
  • Type: Id
  • Description: The unique identifier of the user’s session based on page load time. When the user reloads a page, a new session is started.
  • Example: 321a1ddfaf924803a075f1e69fc87bc06f53ccd0

  • Type: Number

  • Description: If the page completes loading, then DURATION indicates the duration of time in milliseconds between PAGE_START_TIME and when the loading completes. In this case, DURATION corresponds to EFFECTIVE_PAGE_TIME.

    If the page doesn’t complete loading, then DURATION indicates the duration of time in milliseconds between PAGE_START_TIME and when the user navigates to another page.

  • Type: Double
  • Description: Indicates how many milliseconds it takes for the page to load before a user can interact with the page. Multiple factors can affect effective page time (EPT), such as network speed, hardware performance, or page complexity.
  • Type: Boolean
  • Description: When a deviation is detected, EFFECTIVE_PAGE_TIME_DEVIATION records true. The default value is false.

  • Type: String

  • Description: Indicates the origin of an error. This field is populated when EFFECTIVE_PAGE_TIME_DEVIATION_REASON contains the PAGE_HAS_ERROR value.

  • Possible values:

    • CUSTOM - An error originating from the customer’s system or network.
    • SYSTEM - An error originating in Salesforce.

  • Type: String

  • Description: The reason for deviation in page loading time.

  • Possible values:

    • PageHasError - An undefined page loading error occurred.
    • PageNotLoaded - If a customer navigates away from a page while loading processes are in progress, the page doesn’t finish loading.
    • PreviousPageNotLoaded - When navigating to a new page, and the previous page hasn’t completed loading, the next page is considered to have a deviation. Incomplete loading processes on a previous page can affect how the next page loads.
    • InteractionsBeforePageLoaded - A user interacts with a page element before the page is fully loaded.
    • PageInBackgroundBeforeLoaded - A background loading process runs on a page. Background processes run when a user navigates away from a page to another browser tab. The browser deprioritizes the page in the background until the user activates the page’s tab. Because a user can leave a page in the background for a long time, the page is expected to have a high Effective Page Time (EPT).
  • Type: String
  • Description: The type of event. The value is always LightningPageView.
  • Type: String
  • Description: The grandparent scope of the page element where the event occurred.
  • Type: String
  • Description: The string that ties together all events in a user’s login session. It starts with a login event and ends with either a logout event or the user session expiring.
  • Example: GeJCsym5eyvtEK2I
  • Type: String
  • Description: The 15-character ID of the org.
  • Example: 00D000000000123
  • Type: String
  • Description: The operating system name, derived from USER_AGENT.
  • Examples: Android, iOS, OSX, Windows
  • Type: String
  • Description: The operating system version, derived from USER_AGENT.
  • Type: String
  • Description: The internal name of the application that the user accessed from the App Launcher.
  • Example: LightningSales
  • Type: String
  • Description: The name of the component hosting the main content of the page.
  • Example: clients:cardsContainer
  • Type: Id
  • Description: The ID of the record that the user accessed which triggered the event on the page.
  • Example: 0013000000I3zJAAAZ
  • Type: String
  • Description: The entity type of the event.
  • Examples: Task, contacts
  • Type: String
  • Description: The page name or identifier.
  • Example: runtime_sales_seller_home__SellerHome_L
  • Type: String
  • Description: The page type.
  • Example: HomePage
  • Type: Number
  • Description: The time when the page starts loading, measured in milliseconds.
  • Example: 1471564788642
  • Type: String
  • Description: Relative URL of the top-level Lightning Experience or Salesforce mobile app page that the user opened. The page can contain one or more Lightning components. Multiple record IDs can be associated with PAGE_URL.
  • Example: /sObject/0064100000JXITSAA5/view
  • Type: String
  • Description: The parent scope of the page element where the event occurred.
  • Type: String
  • Description: The internal name of the previous application that the user accessed from the App Launcher.
  • Example: LightningSales
  • Type: String
  • Description: The context of the previous page where the event occurred.
  • Example: clients:cardsContainer
  • Type: Id
  • Description: The unique previous page entity identifier of the event.
  • Type: String
  • Description: The previous page entity type of the event.
  • Examples: Task, contacts
  • Type: String
  • Description: The relative URL of the previous Lightning Experience or Salesforce mobile app page that the user opened.
  • Example: /sObject/006410000
  • Type: String
  • Description: The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID.
  • Example: 3nWgxWbDKWWDIk0FKfF5DV

  • Type: String

  • Description: The mobile SDK application type.

  • Possible values:

    • HYBRID
    • HYBRIDLOCAL
    • HYBRIDREMOTE
    • NATIVE
    • REACTNATIVE
  • Type: String
  • Description: The mobile SDK application version number.
  • Example: 5.0
  • Type: String
  • Description: The mobile SDK version number.
  • Example: 2.1.0
  • Type: String
  • Description: The user’s unique session ID. You can use this value to identify all events in Lightning Experience within a session. When the user logs out and logs in again, a new session is started.
  • Example: cdd09305cb6babf34059e27f70e47f1b11dec868
  • Type: String
  • Description: The target page element where the event occurred.
  • Example: tabitem-link
  • Type: String
  • Description: The access time of Salesforce services in GMT.
  • Example: 20130715233322.670
  • Type: DateTime
  • Description: The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). The timezone is GMT.
  • Example: 2015-07-27T11:32:59.555Z

  • Type: String

  • Description: Id of the Lightning event type.

  • Possible values:

    • ltng:error
    • ltng:interaction
    • ltng:pageView
    • ltng:performance
  • Type: Number
  • Description: An auto-incremented sequence number of the current event since the session started.
  • Type: String
  • Description: This field is being deprecated and is mostly null, except in mobile app views where it indicates the page type of views where the context is “native.”
  • Type: Number
  • Description: The time at which this event occurred, measured in milliseconds.
  • Example: 1479769912796
  • Type: String
  • Description: The type of client used to make the request (for example, the browser, application, or API) as a string.
  • Type: String
  • Description: The 15-character ID of the user accessing Salesforce services through the UI or API.
  • Example: 00530000009M943
  • Type: Id
  • Description: The 18-character case-insensitive ID of the user who’s using Salesforce services through the UI or the API.
  • Example: 00590000000I1SNIA0

  • Type: String

  • Description: The category of user license of the user accessing Salesforce services through the UI or API.

  • Possible values:

    • A - Automated Process
    • b - High Volume Portal
    • C - Customer Portal User
    • D - External Who
    • F - Self Service
    • G - Guest
    • L - Package License Manager
    • N - Salesforce to Salesforce
    • n - CSN Only
    • O - Power Custom
    • o - Custom
    • P - Partner
    • p - Customer Portal Manager
    • S - Standard
    • X - Salesforce Administrator