# Introduction to Snowplow Identities
> Snowplow Identities provides real-time identity resolution, stitching user identifiers together to create unified Snowplow IDs.
> Source: https://docs.snowplow.io/docs/identities/
> Documentation index: https://docs.snowplow.io/llms.txt

- Cloud: available
- Private Managed Cloud: available
- Self-Hosted: not available
- Add-on: available

Identities is a paid addon for Snowplow CDI.

Find out more about [Snowplow CDI](/docs/cdi/) and [product availability](/docs/get-started/feature-comparison/), or contact [Support](https://support.snowplow.io) to upgrade.

Snowplow Identities provides real-time identity resolution. It stitches together user identifiers to create a unified view of each user, and adds a unified `snowplow_id` to each event.

Identities allows you to:

- Attribute anonymous events to authenticated users, both within the same session and across sessions and devices
- Connect behavior across web, iOS, and Android apps, when users authenticate with the same credentials on different platforms
- Build on [cross-navigation tracking](/docs/events/cross-navigation/) to identify users across domains
- Distinguish between separate users sharing the same device

Use the provided Identities data models to build identifier mapping tables. These tables help with key use cases such as marketing attribution, conversion funnel analysis, multi-touchpoint reporting, audience targeting, feature engineering, and personalization.

> **Note: Deployment support**
>
> Identities is available on Cloud, and on AWS and GCP via [Private Managed Cloud](/docs/get-started/private-managed-cloud/). Azure isn't supported.

## How Identities fits into the Snowplow pipeline

Identity resolution happens in real time as part of the [event enrichment process](/docs/fundamentals/).

![Diagram showing where Identities fits into the Snowplow pipeline](/assets/images/identities-pipeline-c9e6367cc110e4e7608f60c3f58641e3.png)

After all other configured enrichments run, the pipeline sends user identifiers in the event payload to the Identities service. It either links the identifiers to an existing Snowplow ID, or creates a new one. Enrich then adds the resolved Snowplow ID to the event in an [identity entity](/docs/identities/concepts/#identity-entity).

Some incoming identifiers will reveal that two previously separate Snowplow IDs actually belong to the same user. Identities will merge them in its graph database, and emit a [merge event](/docs/identities/concepts/#merge-events) directly into your enriched event stream.

Your Identities infrastructure is deployed into the same cloud as your pipeline. The core components are:

- **Identities API**: used for identity operations
- **Managed Postgres database**: persists the identity graph and performs graph operations. Snowplow uses [Aurora](https://aws.amazon.com/rds/aurora/) on AWS and [AlloyDB](https://cloud.google.com/products/alloydb) on GCP.

## Get started with Identities

Identities is self-serviceable from [Console](/docs/identities/configuration/) within its [supported scale](/docs/identities/configuration/#supported-scale).

To use Identities, start by deciding which user identifiers are most relevant to your use cases. Identities supports standard Snowplow identifiers such as `user_id` and `domain_userid`, as well as custom identifiers derived from any field in the event payload. Because your choice of identifiers affects both resolution quality and cost, follow the guidance in [choosing identifiers](/docs/identities/configuration/choosing-identifiers/) before you configure them.

After configuring Identities, set up the [Identities dbt package](/docs/identities/data-models/) to create your identity tables. To check how your identity graph is developing, see [Monitor your identity graph](/docs/identities/monitoring/).

## Fulfill GDPR erasure requests

Identities exposes an API to remove a user's entries from the identity graph. See [Erasure](/docs/identities/erasure/) for what it does and how to call it.
