Skip to main content
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.
Autocapture is web only. On iOS and Android, use custom events with the native SDKs.

​
1. Prerequisites

​
2. How the setup works

Autocapture combines the capture library @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.

You — share your authentication surface

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.

Corbado — we build the mapping

Corbado produces the capture configuration and validates it against real journeys.

You — deploy one script

A single tag in your frontend.

Corbado — data appears

Journeys show up in the console within minutes. Confirm with the integration checks.
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.
Start with a single flow. If you want to evaluate Observe before committing to a full integration, tell us which flow to cover, 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.
If you would rather instrument your flows yourself right now, custom events are available self-serve and take 1 to 3 days for a typical login flow.

​
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.
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.
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 to set this up.
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.

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

​
5. Next steps

Verify your integration

Confirm events arrive with the expected payload.

Combine with custom events

Add events for facts that never reach the browser.