# Configure the Identities data model
> Configure the Snowplow Identities dbt package for identity resolution and identifier mapping.
> Source: https://docs.snowplow.io/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-configuration/identities/
> Documentation index: https://docs.snowplow.io/llms.txt

This page helps you configure the Snowplow Identities dbt package. You can customize variables, generate configuration code, and set output schemas.

## Package configuration variables (v0.1.0)

This package sets variables to recommended defaults for optimal model performance. Depending on your use case, you might want to override these values by adding to your `dbt_project.yml` file.

> **Note: Variable name prefix**
>
> All variables in Snowplow packages start with `snowplow__` but we have removed these in the below tables for brevity.

### Warehouse and tracker

| Variable | Description | Default | Warehouse |
| --- | --- | --- | --- |
| `database` | The database that contains your atomic events table. Ignored on Databricks; use `snowplow__databricks_catalog` instead. | `target.database` | All |
| `databricks_catalog` | The Databricks catalog containing your source events. Set the source schema with `snowplow__atomic_schema`. Configure the destination catalog and schema in your dbt profile. | `hive_metastore` | Databricks |
| `atomic_schema` | The schema (dataset for BigQuery) that contains your atomic events table. | `atomic` | All |
| `events_table` | The name of the events table within your configured source database or catalog and schema. | `events` | All |
| `dev_target_name` | The [target name](https://docs.getdbt.com/docs/core/connect-data-platform/profiles.yml) of your development environment as defined in your `profiles.yml` file. See the [Manifest Tables](/docs/modeling-your-data/modeling-your-data-with-dbt/package-mechanics/manifest-tables/) section for more details. | `dev` | All |
| `events` | This is used internally by the package to reference your events table based on other variable values and should not be changed. | `{{ source('atomic', 'events') }}` | All |

### Operation and logic

| Variable | Description | Default |
| --- | --- | --- |
| `start_date` | The date to start processing events from on first run or a full refresh, based on `derived_tstamp`. | `2026-01-01` |
| `identifiers` | The list of identifiers to extract from events and link to each `snowplow_id`. Each entry has a `reference` (the column name in your events table) and an `alias` (the name used in the output tables). Add any event-level fields you want to track as identifiers, such as `email` or `phone`. | `[{'reference': 'domain_userid', 'alias': 'domain_userid'}...` |
| `hash_identifiers` | When set to `true`, all identifier values stored in `snowplow_identities_identifier_mapping` are hashed using SHA-256 before being written to the table. Recommended when identifiers contain PII. | `false` |
| `merge_limit_collapse` | Enable only when no identifier is configured as unique in the Identities service. When enabled, the model collapses eligible duplicate mappings as each identifier next appears in a batch; it does not update all historical mappings immediately. A full refresh from `snowplow__start_date` applies the logic to all reprocessed data. Mappings that could represent identifier TTL eviction are left unchanged. | `false` |
| `allow_refresh` | Used as the default value to return from the `allow_refresh()` macro. This macro determines whether the manifest tables can be refreshed or not, depending on your environment. See the [Manifest Tables](/docs/modeling-your-data/modeling-your-data-with-dbt/package-mechanics/manifest-tables/) section for more details. | `false` |
| `backfill_limit_days` | The maximum number of days of new data to be processed since the latest event processed. | `30` |
| `license_accepted` | Use this field to accept the Snowplow Personal and Academic License or specify that you have a commercial agreement with Snowplow. | `false` |

### Contexts, filters, and logs



