Verify Your Corbado Observe Integration

After deploying Autocapture or adding custom events, confirm that the agreed journeys arrive with the expected steps and outcomes.

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. The three tools

Tool	Use it for
Debug mode	Set `debug: true` at initialization and Observe logs every tracked event to the console. Fastest check that a call site fires at all.
Corbado Observe Debugger	A Chrome DevTools extension with a filterable live stream of what actually leaves the browser, plus the current session ID and user references. Works for both Autocapture and custom events.
Management console	Confirms events were accepted and modeled correctly. Use the events view for the raw stream and user search to reconstruct one journey end to end.

For Autocapture, Observe → Settings → Autocapture also shows whether events from your pages are arriving.

2. Walkthrough

Walk each journey

Walk the journeys included in your integration scope, such as login, sign-up, recovery or enrollment. For Autocapture, confirm this scope with Corbado.

Confirm the events

With debug mode or the Observe Debugger extension open, check that each completed journey produces the expected flow boundaries, decisions, steps and outcome. For Autocapture, review these with Corbado; for custom events, compare them against your event calls. Duplicates from re-renders and a missing finish before a redirect are the two most common defects. Compare against the journey catalog.

Check one journey in the console

Find a test journey via user search and confirm the flow, subflows and decisions look the way you expect.

Check a failure

Test a failure or cancellation in scope, such as an incorrect password or a cancelled passkey dialog. Confirm that the recorded steps and outcome reflect what happened, including attempts that ended before a backend request.

Check identifier attribution when enabled

Submit the same test identifier from two devices and fail both logins. Confirm that User Search with id: finds both attempts without treating them as authenticated activity. Then test changing the identifier or authenticating as a different test user. Check that submissions remain visible and only supported identifier-to-user links are created. See the visual scenarios.

3. When data appears

Data appears in stages. Raw events are visible in the console’s events view right after ingestion. Flows, decisions and subflows appear after the next classification run, which happens about a minute later. Funnels and charts use the next pre-calculation run. Newly discovered hourly series default to a ten-minute cadence and daily series to thirty minutes; existing projects keep their configured cadence and disabled intervals. Analytics pages retain loaded results until you refresh them. If a journey is present in events but missing from a chart, check classification and pre-calculation before refreshing. User Search can prepare recent linked sessions on demand and reports unavailable or failed preparation. This does not backfill historical charts. A device-only anonymous session may still need background classification or an explicit session-ID investigation.

Inspect the recorded evidence

In Debugging → Integration, start with the last 24 hours. The Errors tab defaults to errors; include warnings with the level filter when investigating incomplete coverage. User Search separates the journey from its technical timeline: expand an event for its full payload or copy the JSON. An event’s user reference shows what was supplied on that exact event, separately from the classified flow’s user. User Search shows observed password managers beside a client environment and in its inspector, with first and last seen times in the tooltip. A sighting can come from browser-extension detection or a recognized passkey. Missing icons do not establish that no manager is installed; see password-manager evidence. Sessions that contain only diagnostics or device information, with no tracking events, do not appear as classification errors after classification. Sessions with tracking events but no resulting flow remain issues to investigate. Older error markers can remain until reclassification or retention removes them. A user drawer includes their own flows and anonymous activity on their attributed devices. Other users on these devices explicitly adds other signed-in users’ flows. Keep these labels when interpreting shared-device activity; sharing a device does not establish account ownership. See users and identifiers for identifier evidence.

4. Common issues

Symptom	Likely cause
No events at all	Script not loaded, wrong `Project ID` or `API Base URL`, an unauthorized origin or a Content Security Policy blocking the script or the API endpoint. After an origin change, allow up to ten seconds for authorization to refresh
A console request fails	Check the displayed permissions or IP restriction error and retry after fixing access. A failed query is not evidence of zero activity
Events arrive but no WebAuthn detail	The SDK is not running in the frame that performs the ceremony. See Iframes and RP IDs
Journeys break in the middle	The SDK initializes too late, pages use different project IDs, or a reload starts a new session after inactivity. Check session lifetime and the project’s continuity configuration
Journeys from different environments mixed	Production and staging share a project. Use separate projects per environment
Events arrive, but the whole session has no flows	A `flowFinished()` or `flowDecided()` fired without an open flow. That invalidates the session’s classification. See ordering
A nested sign-up or recovery shows as incomplete although the user finished it	The outer flow’s `flowStarted()` fired again while the nested flow was open, for example from a remounted route. See flows
A decision is missing although both events fired	The `explicitDecisionValue` is not one of the declared `options`, or `finished` carried a different options array. See decisions
A passkey attempt is missing	No `explicitSpecType` arrived on any of its events. See spec types

Overview

Get started

Custom events

Developer tools

Monitoring & alerting

Passkey Intelligence

Data access

Security & compliance

Event model

Verify Your Corbado Observe Integration

1. The three tools

2. Walkthrough

3. When data appears

Inspect the recorded evidence

4. Common issues

5. Next steps

Corbado Observe Debugger

Event model

​1. The three tools

​2. Walkthrough

​3. When data appears

​Inspect the recorded evidence

​4. Common issues

​5. Next steps

Corbado Observe Debugger

Event model

1. The three tools

2. Walkthrough

3. When data appears

Inspect the recorded evidence

4. Common issues

5. Next steps