1. Data model entities
| Entity | Description |
|---|---|
| Projects | Projects are the top-level container in the data model. Each project stores its own tracking data and events, and projects are fully isolated from each other. |
| Applications | Applications represent the channels of your product (for example, web and native app). In most cases, you keep them in one project and model them as separate applications. Read our section on Applications for more details. |
| Flows | Flows describe larger user journeys, such as sign-up, login, or account recovery. A flow is composed of decisions and subflows. Read our section on Flows for more details. |
| Decisions | Decisions capture system and user choices, such as selecting a login method (password, email OTP, or social login). In funnel analysis, decisions create explicit nodes and can be used as filters. Decisions are created by sending specific events. Read our section on Decisions for more details. |
| Subflows | Subflows are smaller building blocks within a flow. They group related events into a logical unit, such as a passkey login or password enrollment. Read our section on Subflows for more details. |
| Events | Events are the foundation of tracking in Corbado Observe. Generic event types (such as subflow_trigger, subflow_step_started, subflow_step_finished, and subflow_step_error) are used together with a subflow type and step name to model subflows. Other event types model flows and decisions. |
| Users | Users in Corbado Observe mirror your own user entities. User references are used to group multiple flows for one user and enable a per-user view on authentication behavior. Read our section on Users for more details. |
| Tags | Tags are key-value pairs that can be used to add additional metadata to events. Read our section on Tags for more details. |