> ## 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.

# Try Observe on Your Login

> Explore your own authentication journeys in Corbado Observe before involving engineering in a deployment.

Explore your own login journeys in **Corbado Observe** before a website deployment. Observe includes Autocapture, which Corbado configures for your login. You enable it in your own browser using the setup we provide, walk through your login and explore the results in the Observe console.

This gives product managers a practical way to assess the data, build a case for their team and give engineering a clear next step. You can evaluate your existing login before a passkey rollout or alongside the authentication methods you already offer.

## 1. Two ways to try Observe

Choose the starting point that suits your team. Both use Autocapture configured for your authentication flows.

|                     | Try it in your browser                                                          | Integrate into staging                                       |
| ------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| Who gets started    | A product manager or anyone evaluating the login experience                     | Your engineering team                                        |
| What you do         | Follow the browser setup supplied by Corbado and walk through your login        | Add the supplied script to your staging frontend             |
| Website changes     | None                                                                            | One script tag and, where needed, CSP allowlist additions    |
| Data you see        | Journeys you test in the configured browser                                     | Journeys from users of the instrumented staging pages        |
| What you can assess | How your journeys appear, which insights are useful and what to show internally | How Observe works in your environment before a wider rollout |

You can start directly with [staging integration](/corbado-observe/get-started/autocapture) if engineering is ready. Browser evaluation is an optional first step.

## 2. Get your evaluation setup

<Steps titleSize="h3">
  <Step title="Choose a journey and a question">
    Send Corbado your login URL and one question you want to explore, such as where a password login fails or what happens when a user cancels a passkey prompt. We agree which journey to capture first. For a public login, we can often configure Autocapture using our own test accounts. For restricted journeys, we agree on a walkthrough or suitable test access.
  </Step>

  <Step title="Corbado configures your evaluation">
    Corbado adjusts the capture rules for your login, confirms which journeys are included and gives you access to an evaluation project. You receive a browser setup link with instructions for your environment.
  </Step>

  <Step title="Add Observe to your browser">
    Follow the supplied instructions to install the browser extension and enable Observe with your project configuration. Corbado can walk you through this. The setup applies to the specified authentication pages in your own browser; your website deployment and other users are unaffected.
  </Step>

  <Step title="Try your login and view the results">
    Complete one of the agreed journeys, then open your evaluation project in the [Observe console](https://app.corbado.com). Follow the recorded steps and choices to the outcome. Repeat with a failure or cancellation included in your scope so you can compare the two experiences.
  </Step>

  <Step title="Show your team and agree the next step">
    Use the recorded journeys to show colleagues what you can see and which questions you want to investigate with more data. Share the [integration guide](/corbado-observe/get-started/autocapture) with engineering when you are ready to test in staging.
  </Step>
</Steps>

<Note>
  The browser setup sends captured telemetry to your Corbado Observe evaluation project. It does not require changes to your website's Content Security Policy. If your organization restricts browser extensions, use staging integration or arrange a walkthrough with Corbado.
</Note>

## 3. What to explore

Start with a few questions you want to answer about your login:

* Can you follow a journey from identifier entry to the login outcome?
* Can you see which authentication options were offered and which one you selected?
* What appears when you retry a step, cancel or leave the journey?
* Which views would help your team investigate friction or explain the experience to colleagues?

Corbado confirms the scope of the initial configuration with you. Start with the included journeys and extend coverage as needed. Password, passkey, social login and MFA may each require additional configuration and validation.

Test sessions let you assess the journey detail and the console. Production conversion and abandonment rates require data from a deployed integration with validated coverage.

<Tip>
  **Preparing an internal discussion?** Walk one successful journey and one failure or cancellation in scope. Use the resulting views to show your team what Observe captures, then share the [integration guide](/corbado-observe/get-started/autocapture) with engineering.
</Tip>

## 4. Move to integration

Once you want to collect data across users, your engineering team adds the Observe snippet supplied for your project to staging or production. Where a Content Security Policy is in place, they allow the script and API origins, as they would for other analytics tools.

Corbado reuses the capture configuration where the flows match and adjusts it for differences between environments. Your team then verifies the deployed integration. Browser evaluation demonstrates the configured journeys; staging also validates script loading, event delivery and your website's policy configuration.

See [Integrate Autocapture](/corbado-observe/get-started/autocapture) for the engineering steps.

## 5. Help during your evaluation

If a journey is missing, confirm that it is included in your evaluation scope and that the browser setup is enabled on the authentication page. Check the correct evaluation project and allow time for processing; see [when data appears](/corbado-observe/get-started/verify#3-when-data-appears).

Use the management console to review captured events. Depending on the supplied browser setup, requests may not appear in the page's Network panel or the separate Observe Debugger extension.

To stop recording, disable the supplied script in your browser setup and reload the authentication pages. This stops future capture through that setup; data already sent remains in the evaluation project.

[Contact Corbado](mailto:support@corbado.com) to prepare an evaluation or review your first results together.