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

# Get Started with Autocapture

> Deploy Corbado Observe Autocapture: one script in your web frontend, no event tagging and a login journey that maps itself.

**Autocapture** is the recommended way to run **Corbado Observe** on web. Corbado prepares the script for your flows, so your side of the integration is **one line of code**. No event tagging, no changes to your login flows and nothing for your team to maintain.

<Info>
  Autocapture is web only. On iOS and Android, use [custom events](/corbado-observe/get-started/custom-events) with the native SDKs.
</Info>

## 1. Prerequisites

* An active project in the [Corbado management console](https://app.corbado.com)
* Your `Project ID` and `API Base URL` from [settings](https://app.corbado.com/observe/settings/general)
* Your authentication origins registered under [origins](https://app.corbado.com/observe/settings/origins)

## 2. How the setup works

Autocapture combines the capture library [`@corbado/autocapture`](https://www.npmjs.com/package/@corbado/autocapture) with a mapping for your flows. Corbado builds and maintains that mapping and keeps it current as your login evolves, which is what removes the instrumentation work from your team. It is therefore set up together with us rather than fully self-serve.

<Steps>
  <Step title="You — share your authentication surface" icon="user">
    Tell us which login, sign-up, recovery and enrollment entry points exist and which methods each offers. A walkthrough of the live flows is usually enough.
  </Step>

  <Step title="Corbado — we build the mapping" icon="building">
    Corbado produces the capture configuration and validates it against real journeys.
  </Step>

  <Step title="You — deploy one script" icon="user">
    A single tag in your frontend.
  </Step>

  <Step title="Corbado — data appears" icon="building">
    Journeys show up in the console within minutes. Confirm with the [integration checks](/corbado-observe/get-started/verify).
  </Step>
</Steps>

Your only real effort is step 3: adding one line. The walkthrough in step 1 takes minutes, and steps 2 and 4 are entirely ours.

<Tip>
  **Start with a single flow.** If you want to evaluate Observe before committing to a full integration, [tell us which flow to cover](mailto:support@corbado.com), for example passkey login on your login page. We prepare an Autocapture script for exactly that flow, you add one line and walk it, then you see real data from your own application.
</Tip>

<Note>
  If you would rather instrument your flows yourself right now, [custom events](/corbado-observe/get-started/custom-events) are available self-serve and take 1 to 3 days for a typical login flow.
</Note>

## 3. Deploy the script

Place the script as early as possible, ideally right before your closing `</head>` tag, so no part of the journey is missed.

```html theme={null}
<script src="https://cdn.cloud.corbado.io/observe/autocapture-latest.min.js" crossorigin="anonymous"></script>
```

The Autocapture script is served from Corbado's CDN. Because Corbado hosts both the script and your mapping, updates to your flows reach production without a deployment on your side.

<Info>
  If you need more control over updates and changes, the Autocapture mapping script can also be hosted on your own platform or CDN. You then decide when a new version goes live, at the cost of pulling in mapping updates yourself. [Talk to us](mailto:support@corbado.com) to set this up.
</Info>

<Warning>
  Use the exact snippet issued for your project rather than copying this illustrative example verbatim. It carries your `Project ID` and `API Base URL` as shown in the [management console](https://app.corbado.com/observe/settings/general).
</Warning>

| Property        | Value                                                             |
| --------------- | ----------------------------------------------------------------- |
| Size            | Approximately 40 KB gzipped                                       |
| Failure mode    | Fails closed: telemetry is lost, authentication is never affected |
| Backend changes | None                                                              |

## 4. Content Security Policy

If you run a CSP, allow the Corbado script origin and your API endpoint. Both values are shown in your project settings.

```
script-src  https://cdn.cloud.corbado.io;
connect-src <your-api-base-url>;
```

## 5. Next steps

<CardGroup cols={2}>
  <Card title="Verify your integration" icon="circle-check" href="/corbado-observe/get-started/verify">
    Confirm events arrive with the expected payload.
  </Card>

  <Card title="Combine with custom events" icon="code" href="/corbado-observe/overview/integration-paths#4-combining-both-on-web">
    Add events for facts that never reach the browser.
  </Card>
</CardGroup>