> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corbado.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Corbado Observe: Observability for Authentication and Passkeys
> Track authentication journeys, identify drop-offs and improve login conversion with Corbado Observe.
## 1. Introduction
**Corbado Observe** is an observability tool for authentication flows. It captures structured events from your web app and your native apps, maps them to a clear data model and shows you how users move through login, sign-up and recovery.
Whether you use passkeys, passwords, email OTP, social login or a combination, Observe gives you one view across all of them.
**Observe or Connect?** Use **Corbado Observe** to measure and debug the authentication you already have. Use [Corbado Connect](/corbado-connect/overview/welcome) to *add* passkeys to an existing identity provider.
## 2. Why use Corbado Observe?
Most teams have limited visibility into what happens between "user lands on login" and "user is authenticated". Observe closes that gap:
* **See what your backend cannot.** A user who never gets past the passkey dialog produces no backend event at all. Observe captures the client-side reality: system dialogs, credential managers, silent cancellations and device-specific failures.
* **Measure conversion end-to-end.** Track every step of login, sign-up and recovery so you can pinpoint where users drop off.
* **Compare authentication methods.** See how passkeys, passwords, email OTP and social login perform side by side.
* **Segment by channel and context.** Use [applications](/corbado-observe/tracking/applications) and [tags](/corbado-observe/tracking/tags) to compare web, iOS, Android or any custom dimension.
* **Trace individual journeys.** Link events to your [users](/corbado-observe/tracking/user) to follow retries and method switches for one person.
## 3. How it works
You add a lightweight SDK to your frontend. It observes the authentication journey on the client, sends structured events to Corbado and Corbado maps them onto flows, subflows and decisions that the [management console](https://app.corbado.com) turns into funnels, error analysis and per-user journeys.
Administrators access these insights in the Management Console. Enterprise customers can use their existing identity provider through [SAML 2.0 single sign-on](/corbado-observe/overview/management-console-access), including Okta and Microsoft Entra ID.
Observe is **client-side only** and never sits in the authentication path. See [How Observe works](/corbado-observe/overview/how-it-works) for the full pipeline and how Observe compares to the analytics and monitoring tools you already run.
## 4. Two ways to send data
| Path | Platforms | Effort | Summary |
| --------------------------------------------------------------------------- | ----------------- | ---------------- | --------------------------------------------------------------------------------------------------------------- |
| **[Autocapture](/corbado-observe/get-started/autocapture)** *(recommended)* | Web | One line of code | Corbado prepares the script and maps your journey from signals your frontend already emits. |
| **[Custom events](/corbado-observe/get-started/custom-events)** | Web, iOS, Android | 1 to 3 days | Emit explicit events where you need guaranteed semantics, and on native platforms where Autocapture cannot run. |
See [Integration paths](/corbado-observe/overview/integration-paths) to choose.
## 5. Next steps
The pipeline, what Observe is not and how it compares to existing tooling.
Platforms, data handling and known limitations.
The recommended path on web.
Flows, subflows, decisions, users and tags.