Skip to main content
Custom events are explicit Corbado Observe events you emit from your own code, at the semantically correct points in your flows. You get exactly the granularity you define. Budget 1 to 3 days for a typical login flow, plus your own testing.
On web, most teams run Autocapture as the foundation and add custom events only where a step needs guaranteed semantics. On iOS and Android, custom events are the integration. See Integration paths.
Prefer an AI coding agent? See Use with AI agents and let it instrument the integration for you.

1. Prerequisites

2. Install the SDK

3. Initialize the tracker

Initialize as early as possible in your app startup.

4. Track your first event

When your login UI is rendered and visible, send flowStarted:
Use touchpoint consistently, for example account, checkout or modal, so you can compare funnel metrics across entry points.

5. Verify

Set debug: true in your init() call while developing and Observe logs every tracked event to the console:
Set debug: false in production. For the full verification workflow, including the Corbado Observe Debugger extension for Chrome DevTools, see Verify your integration.

6. Next steps

Tracking reference

Flows, decisions, subflows, users and tags.

Verify your integration

Confirm events arrive before you ship.