# What We Monitor

Cuoral collects and analyzes multiple streams of customer-interaction data, all linked to each session, customer, and organization.

Here’s what’s being monitored under the hood 👇

***

#### 1. Console Errors

**Purpose:** Detect client-side issues affecting customer experience — e.g., failing scripts, broken UI components, or unhandled exceptions.

* Error messages and stack traces
* URL where the error occurred
* Severity level (error, warn, info, debug)
* Associated session, customer, and organization
* Additional context (browser, environment metadata)

> “12% of active sessions encountered console errors — likely affecting checkout conversion.”

***

#### 2. API Response Logs

**Purpose:** Identify backend errors, failed integrations, and slow endpoints impacting customers.

* Request URL and HTTP method
* Response status codes and payloads
* Latency and metadata
* Associated customer and session context

> “Average response time increased by 45% for `/payment/initiate` endpoint — customers may be experiencing transaction delays.”

***

#### 3. Page Views & Navigation Events

**Purpose:** Measure engagement and pinpoint drop-off points or friction patterns.

* Page URLs and referrers
* User agents (browser/device info)
* Metadata such as time on page or scroll depth
* Customer, session, and organization linkage

> “45% of users drop off after visiting the pricing page — consider optimizing call-to-action.”

***

#### 4. Recorded Media (Session Replay & Artifacts)

**Purpose:** Provide visual context for reported issues or customer interactions, reducing time-to-resolution for support teams.

* Secure URLs for session replays or recordings
* Notes or annotations from support teams
* Context on customer, organization, and session

***

#### 5. Session Intelligence (Aggregated Metrics)

**Purpose:** Give organizations a summarized view of each customer’s journey quality and alert when attention is needed.

* Total error count
* API error rate
* Average response time
* Page view count / engagement activity
* Engagement score (based on interaction richness)
* Churn risk score (based on inactivity and issue frequency)

> “Session 34215 shows high churn risk — multiple API errors and zero engagement in the last 5 minutes.”

***

### 🧩 Integrated Relationships

Each record Cuoral captures is linked across your ecosystem, enabling full visibility and context.

| Entity                     | Linked To                            | Example Use                         |
| -------------------------- | ------------------------------------ | ----------------------------------- |
| **Organization**           | All events                           | Organization-wide health reports    |
| **Customer**               | Sessions, logs, views                | Individual experience analysis      |
| **Session (Conversation)** | API logs, console errors, page views | Complete interaction timeline       |
| **RecordMedia**            | Errors, APIs, Pages                  | Visual debugging & support evidence |
| **Tickets**                | Errors & API logs                    | Context-rich support automation     |

### 🔐 Privacy & Data Control

* All monitored data is linked via anonymized session and customer IDs.
* Sensitive payloads are redacted by default.
* Cuoral supports GDPR compliance and organization-level data retention policies.

***

### 🧭 Summary

| Category         | Description                                                                           |
| ---------------- | ------------------------------------------------------------------------------------- |
| **Focus**        | End-to-end customer experience monitoring                                             |
| **Core Modules** | Console Errors, API Logs, Page Views, Media Records, Session Intelligence             |
| **Output**       | Alerts, analytics dashboards, proactive insights                                      |
| **Goal**         | Empower Customer Success, Support, and Product teams to act before customers complain |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cuoral.com/guide/what-we-monitor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.