# Snowplow CDI overview
> Snowplow CDI tracks behavioral data from your apps, validates and enriches it, and loads it into your warehouse, lake, or stream. Find the docs for each stage.
> Source: https://docs.snowplow.io/docs/cdi/
> Documentation index: https://docs.snowplow.io/llms.txt

Snowplow Customer Data Infrastructure (CDI) is a pipeline for behavioral data. You define the [events](/docs/fundamentals/events/) and [entities](/docs/fundamentals/entities/) you want, trackers in your apps send them to a Collector, and the pipeline checks each event against its [schema](/docs/fundamentals/schemas/), enriches it, and loads it into your warehouse, lake, or stream. Events that don't match their schema become [failed events](/docs/fundamentals/failed-events/), so they aren't loaded and aren't lost.

Use CDI when you need event-level data you control: for product and marketing analytics, for a composable CDP, or as the source for [Signals](/docs/signals/introduction/).

## Start here

You can start on a hosted environment that Snowplow provisions for you, with no infrastructure to deploy. The [free trial](/docs/get-started/free-trial/) is 14 days of Snowplow CDI Cloud, and you usually receive access instructions within moments of verifying your email address. Once the environment exists, either hand the setup to your coding agent with the quickstart, or follow the steps yourself to track your first events and query them. When you're ready for production, see [Choose a Snowplow deployment](/docs/get-started/deployment-options/).

Quickstart30 min

### [Quickstart with your coding agent](/docs/get-started/quickstart/)

Get a hosted environment and send validated events from your app.

### [Step by step](/docs/get-started/free-trial/)

Get access to Console, track your first events, and query them.

### [Already have data in your warehouse?](/docs/destinations/warehouses-lakes/querying-data/)

Query the atomic events table, then build sessions and users tables with Unified Digital.

### [Core concepts](/docs/fundamentals/)

Events, entities, schemas, and how the pipeline processes them.

Coming from Segment, Google Analytics, Adobe Analytics, or Mixpanel? See [Migrate from another tool](/docs/migration-guides/).

## Explore by stage

The CDI sidebar follows the path an event takes, from design to data model. Each card opens the first page of a sidebar group.

### [Design tracking](/docs/event-studio/)

Plan events and entities in Event Studio, and generate tracking code with Snowtype.

- [Tracking plans](/docs/event-studio/tracking-plans/)
- [Data structures](/docs/event-studio/data-structures/)
- [Snowtype](/docs/event-studio/implement-tracking/)

### [Collect events](/docs/sources/)

Trackers for web, mobile, server, and games, and webhooks for third-party tools.

- [Compare trackers](/docs/sources/#compare-trackers)
- [Web trackers](/docs/sources/web-trackers/)
- [Built-in events and entities](/docs/events/)

### [Test your tracking](/docs/testing/)

Check the events your tracking sends before they reach production.

- [Snowplow Inspector](/docs/testing/snowplow-inspector/)
- [Snowplow Micro](/docs/testing/snowplow-micro/)

### [Enrich events](/docs/pipeline/enrichments/)

Add data to events in the pipeline, such as location, parsed user agents, and campaign details, or mask personal data.

- [Available enrichments](/docs/pipeline/enrichments/available-enrichments/)
- [IP anonymization](/docs/pipeline/enrichments/available-enrichments/ip-anonymization-enrichment/)

### [Identities](/docs/identities/)

Stitch a user's identifiers into one Snowplow ID in real time, across devices and logins.

- [How merges work](/docs/identities/concepts/merges/)
- [Choose identifiers](/docs/identities/configuration/choosing-identifiers/)
- [Erase identity data](/docs/identities/erasure/)

### [Load and forward](/docs/destinations/)

Load into warehouses and lakes, forward events to other tools, or stream them to your own targets.

- [Destinations catalog](/docs/destinations/#destinations-catalog)
- [Warehouses and lakes](/docs/destinations/warehouses-lakes/)
- [Event forwarding](/docs/destinations/forwarding-events/)

### [Query and model data](/docs/destinations/warehouses-lakes/querying-data/)

Query the atomic events table, and build sessions, users, and attribution tables with dbt packages.

- [Atomic event fields](/docs/fundamentals/canonical-event/)
- [dbt packages](/docs/modeling-your-data/modeling-your-data-with-dbt/)

### [Monitor data quality](/docs/failed-events/)

Find and fix failed events, and set up data quality alerts.

- [See failed events in Console](/docs/monitoring/)
- [Alerts](/docs/monitoring/alerts/)

## Reference

Configuration options, API references, and component versions are in the Reference section, shared with Signals.

- [Tracker API reference](/docs/api-reference/trackers/)
- [Component configuration](/docs/api-reference/)
- [Versions and compatibility](/docs/api-reference/versions/)
- [Tracker versions](/docs/api-reference/versions/#trackers)