View guest events

You use the Guest Event Explorer screen to view and debug specific events and monitor general platform health. The screen shows a table of recent events for a selected guest, and the details of each event. Events are shown for the past hour.

Team members with a User, Developer, Admin, or Read only role in Sitecore Cloud Portal can view guest events.

To use the Guest Event Explorer screen:

On the navigation menu, click Developer center > Event viewer.
You can choose to show the screen for a random guest or select a guest of your choice. The former option is useful for checking general platform health, and the latter is used to check recent events of a specific guest.
- To select a random guest, click Quick Select Customer or Quick Select Visitor. The system selects a guest who was recently active.
- To select a specific guest, enter their identifier into the search box.
By default, all events that were recorded for this guest in the past hour are shown. To view only failed events, click Failed. To view only successful events, click Success.
If the event is an experience, you can click the experience name to open it.
To view all events captured for a particular session, click the session name.

To open the event details in a key-value table format, click the eye icon.

The following details appear for most events:

Attribute	Description
Browser Ref	An identifier of the browser used in this event.
Channel	The channel captured during this event.
Client Key	Your organization's client key.
Created At	The time at which the event was first ingested into Sitecore CDP.
Modified At	The time at which the event was fully processed.
Point of Sale	The point of sale (storefront) at which the event occurred.
Ref	An identifier of this event.
Session Ref	An identifier of the session during which this event occurred.
Status	The status of the event processing. For most events, even failed ones, the status is PROCESSED.
Type	The event type.

To view the details as a JSON object, click Show as JSON in the event details screen. The following is an example JSON structure of an event:

RequestResponse

{
  "ref": "cc123-123-***-***-***",
  "clientKey": "***",
  "createdAt": "2022-03-31T08:15:05.199Z",
  "modifiedAt": "2022-03-31T08:15:05.220Z",
  "type": "TRACKING",
  "status": "PROCESSED",
  "channel": "WEB",
  "pointOfSale": "retailsite.com",
  "browserRef": "***-***-***-***-***",
  "sessionRef": "***-***-***-***-***",
  "flowExecutionRef": "***-***-***-***-***",
  "arbitraryData": {
    "flowExecution": {
      "ref": "***-***-***-***-***",
      "occurredAt": 1648714504380,
      "flowRef": "***-***-***-***-***",
      "flowFriendlyId": "modal_pop_up",
      "flowVariantRef": "***-***-***-***-***",
      "guestRef": "***-***-***-***-***",
      "flowExecutionTimeMs": 2381,
      "status": "SUCCESS",
      "decision": {
        "decisionModelRef": "***-***-***-***-***",
        "decisionModelVariantRef": "***-***-***-***-***",
        "decisionModelExecutionTimeMs": 2306,
        "results": [
          "{\"ruleId\":\"NBO_2\",\"search1\":\"discount\",\"search2\":\"shoes\",\"search3\":\"bag\",\"search4\":\"accessories\"}"
        ]
      }
    },
    "category": "EXECUTED"
  },
  "flowExecution": {}
}

To view new data, you can click the refresh button at the top right.

Do you have some feedback for us?

If you have suggestions for improving this article,