Skip to main content
Corbado Observe Debugger is a Chrome DevTools extension: it adds a Corbado panel to Chrome DevTools showing exactly what Corbado Observe sends from the browser while you use your application. It is the fastest way to verify an integration, because it inspects the outgoing event traffic rather than your code, so it works for both Autocapture and custom events. This is a diagnostic tool, not part of your integration: it reads what your own browser sends on the page you have open and collects nothing itself. Nothing needs to be deployed for it, and because it inspects outgoing traffic, it works just as well on your production site as in development. It also runs independently of debug: true, so you can use both in parallel.
For a browser evaluation, verify delivery under Events in the management console. Observe requests sent through the extension transport may not appear in the page’s Network panel or the Observe Debugger.

​
1. What it shows

Observe Data gives you the tracking context of the page: the current session ID used to correlate one journey, with copy, refresh and reset actions and every user reference seen so far with first and last timestamps. Resetting the session starts a clean journey without clearing all browser state. The session ID shown here is Corbado Observe’s tracking session ID, used to correlate the events of one journey. It is not your application’s own session, and resetting it has no effect on your users’ authentication state. Observe Events is a live, filterable stream: Controls include a free-text filter across name, type and data, chips to show only events or only lows, a recording toggle and a clear action.

​
2. Requirements

​
3. Install

1

Get the extension

Install Corbado Observe Debugger from the Chrome Web Store.
2

Open the panel

Open DevTools on your application, with Command-Option-I on macOS or F12 on Windows and Linux, then switch to the Corbado tab.

​
4. Typical workflow

Clear the stream, walk one journey from start to finish without navigating away, then read the sequence: it should start with a flow event, contain the subflow steps you expect and end with a finish event. Gaps and duplicates are obvious in the stream. Then repeat with a deliberate failure, such as cancelling a passkey dialog. Silent cancellations produce no backend request at all, so this is the case worth checking explicitly.

​
5. Next steps

Verify your integration

The full verification workflow.

Tracking reference

What the event names and fields mean.