Skip to main content


Package Configuration Variablesโ€‹

This package utilizes a set of variables that are configured to recommended values for optimal performance of the models. Depending on your use case, you might want to override these values by adding to your dbt_project.yml file.

All variables in Snowplow packages start with `snowplow__` but we have removed these in the below tables for brevity.

Warehouse and Tracker

Operation and Logic

Contexts, Filters, and Logs

Warehouse Specific

Config Generatorโ€‹

You can use the below inputs to generate the code that you need to place into your dbt_project.yml file to configure the package as you require. Any values not specified will use their default values from the package.

Warehouse and Tracker
Database that contains your atomic events
Target name of your development environment as defined in your `profiles.yml` file
The name of the table that contains your atomic events
The name of the schema that contains your atomic events
Operation and Logic
The maximum numbers of days of new data to be processed since the latest event processed
Custom SQL for your base events this run table.
The maximum allowed number of days between the event creation and it being sent to the collector
The maximum allowed session length in days. For a session exceeding this length, all events after this limit will stop being processed
The name of the package you are running this macro under
Number of days to limit scan on `snowplow_web_base_sessions_lifecycle_manifest` manifest
Number of days to look back over the incremental derived tables during the upsert
Session Identifiers

> Click the plus sign to add a new entry
User Identifiers

> Click the plus sign to add a new entry
Contexts, Filters, and Logs
App IDs

> Click the plus sign to add a new entry
Warehouse Specific
(Redshift) Entities or SDEs

> Click the plus sign to add a new entry

Project Variables:

snowplow_utils: null

Output Schemasโ€‹

By default all scratch/staging tables will be created in the <target.schema>_scratch schema, the derived tables, will be created in <target.schema>_derived and all manifest tables in <target.schema>_snowplow_manifest. Some of these schemas are only used by specific packages, ensure you add the correct configurations for each packages you are using. To change, please add the following to your dbt_project.yml file:


If you want to use just your connection schema with no suffixes, set the +schema: values to null

+schema: my_scratch_schema
Was this page helpful?