> ## 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 for web

> Integrate Autocapture through a lightweight loader and add custom events where needed.

Start with **Autocapture** to bring your existing authentication journeys into Observe. For enterprise projects, Corbado configures the capture bundle for your login and provides its integration snippet through the [Management Console](https://app.corbado.com).

## Integrate with the lightweight loader

Your application includes a small wrapper that loads the configured bundle from Corbado. The bundle already contains the Observe SDK and capture rules, so your frontend does not need an npm SDK dependency or event calls for every interaction.

<Steps>
  <Step title="Get your configured snippet">
    Use the loader URL and project settings provided for your enterprise integration in the Management Console.
  </Step>

  <Step title="Add the loader to your frontend">
    Add the supplied wrapper once, then initialize capture as soon as your authentication frontend starts, under your established collection policy. The wrapper queues lifecycle calls while the bundle loads asynchronously.
  </Step>

  <Step title="Verify the captured journeys">
    Walk the configured login methods, including failures, retries and method switches. Confirm that the resulting journeys match the application.
  </Step>
</Steps>

[Integrate Autocapture](/corbado-observe/get-started/autocapture) contains the loader example, lifecycle calls and CSP requirements.

## Corbado-managed updates

The loader URL stays the same while Corbado publishes updated capture bundles. Subsequent page loads receive the updates under the applicable browser and CDN caching rules. You do not need an application release for each capture-configuration update.

Corbado maintains the capture rules as authentication flows and browser behavior evolve. Share planned login changes so coverage can be verified. See [configuration updates](/corbado-observe/get-started/autocapture#configuration-updates) for hosting and release considerations.

## Add custom events when needed

For outcomes or context that Autocapture cannot observe, see [custom-event setup](/corbado-observe/get-started/custom-events). The JavaScript SDK supports this explicit instrumentation; it is already included in your Autocapture bundle.

When combining custom events with Autocapture, [coordinate the shared tracker and session](/corbado-observe/overview/integration-paths#4-combining-both-on-web) with Corbado. Avoid independently initializing another tracker for the same journey.

## Resources

* **Autocapture:** [Loader setup and lifecycle calls](/corbado-observe/get-started/autocapture).
* **Verification:** [Check the integration](/corbado-observe/get-started/verify).
* **Privacy:** [Built-in protections and data policies](/corbado-observe/security/privacy).
* **Explicit instrumentation:** [Custom events](/corbado-observe/get-started/custom-events) and [AI-assisted instrumentation](/corbado-observe/get-started/use-with-ai-agents).
