10. Tags for Grouping and Selecting Models
Tags for Grouping and Selecting Models
As the beems_techne_ecomm_dbt project grows, tags let us group and select models without listing every model manually.
RAW -> BRONZE -> SILVER -> GOLD -> MART
A tag is metadata attached to a dbt resource for grouping, selection, and orchestration.
Learning Objectives
- Apply tags in a model's
config()block. - Apply layer tags in
dbt_project.yml. - Select models with
tag:selectors. - Include upstream or downstream dependencies with
+. - Distinguish dbt tags from Snowflake query tags.
1. Useful Project Tags
| Tag | Purpose |
|---|---|
customer | Customer-related models |
sales | Sales and order models |
product | Product-related models |
hourly | Frequently refreshed models |
daily | Daily analytical models |
dashboard | Dashboard-facing models |
core | Critical business models |
temporary | Experimental models |
Example assignments:
stg_customers -> customer, hourly
stg_orders -> sales, hourly
fct_orders -> sales, core, dashboard
customer_360 -> customer, dashboard
2. Applying Tags to a Model
Example: models/bronze/customers/stg_customers.sql
{{ config(
materialized='view',
tags=['customer', 'hourly']
) }}
SELECT
CUSTOMER_ID,
FIRST_NAME,
LAST_NAME,
EMAIL,
COUNTRY,
CUSTOMER_STATUS
FROM {{ source('ecommerce_raw', 'customers') }}
Example: models/bronze/orders/stg_orders.sql
{{ config(
materialized='view',
tags=['sales', 'hourly']
) }}
SELECT
ORDER_ID,
CUSTOMER_ID,
ORDER_DATE,
ORDER_STATUS,
CURRENCY
FROM {{ source('ecommerce_raw', 'orders') }}
3. Tagging Gold Models
Example: models/gold/facts/fct_orders.sql
{{ config(
materialized='table',
tags=['sales', 'core', 'dashboard']
) }}
SELECT
ORDER_ID,
CUSTOMER_ID,
ORDER_DATE,
ORDER_STATUS,
FINAL_AMOUNT
FROM {{ ref('int_customer_orders') }}
4. Tags in dbt_project.yml
models:
beems_techne_ecomm_dbt:
bronze:
+tags:
- bronze
silver:
+tags:
- silver
gold:
+tags:
- gold
mart:
+tags:
- mart
Folder tags can be combined with model-specific tags such as sales, core, or dashboard.
5. Selecting Models with Tags
# One tag
dbt run --select tag:hourly
# Multiple groups: sales OR customer
dbt run --select tag:sales tag:customer
# Models with both tags
dbt run --select "tag:sales,tag:hourly"
# Exclude temporary models
dbt run --exclude tag:temporary
6. Include Dependencies with +
# Tagged models and downstream models
dbt run --select "tag:sales+"
# fct_orders and upstream dependencies
dbt run --select "+fct_orders"
# Complete path in both directions
dbt run --select "+fct_orders+"
7. Hands-On: Run Tagged Models
dbt run --select tag:hourly
Verify the tagged customer model in Snowflake:
SELECT
CUSTOMER_ID,
FIRST_NAME,
LAST_NAME,
EMAIL,
COUNTRY,
CUSTOMER_STATUS
FROM BEEMS_TECHNE_ECOMM.BRONZE.STG_CUSTOMERS
ORDER BY CUSTOMER_ID
LIMIT 5;
Expected output:
| CUSTOMER_ID | FIRST_NAME | LAST_NAME | COUNTRY | CUSTOMER_STATUS | |
|---|---|---|---|---|---|
| 10001 | Asha | Sharma | asha@example.com | INDIA | ACTIVE |
| 10002 | Daniel | Lee | daniel@example.com | SINGAPORE | ACTIVE |
| 10003 | Maya | Patel | maya@example.com | INDIA | ACTIVE |
| 10004 | Ravi | Kumar | ravi@example.com | INDIA | ACTIVE |
| 10006 | Nora | Tan | nora@example.com | SINGAPORE | ACTIVE |
Verify the tagged orders model:
SELECT
ORDER_ID,
CUSTOMER_ID,
ORDER_DATE,
ORDER_STATUS,
CURRENCY
FROM BEEMS_TECHNE_ECOMM.BRONZE.STG_ORDERS
ORDER BY ORDER_ID
LIMIT 5;
Expected output:
| ORDER_ID | CUSTOMER_ID | ORDER_DATE | ORDER_STATUS | CURRENCY |
|---|---|---|---|---|
| 50001 | 10001 | 2025-02-01 | DELIVERED | INR |
| 50002 | 10002 | 2025-02-02 | DELIVERED | SGD |
| 50003 | 10003 | 2025-02-03 | SHIPPED | INR |
| 50004 | 10004 | 2025-02-04 | CANCELLED | INR |
| 50005 | 10006 | 2025-02-05 | DELIVERED | SGD |
8. Tags and Orchestration
Tags group models; they do not schedule them. A scheduler such as cron, Airflow, or dbt Cloud executes the selected command.
Hourly -> dbt build --select tag:hourly
Daily -> dbt build --select tag:daily
Dashboard -> dbt build --select tag:dashboard+
9. dbt Tags versus Snowflake Query Tags
| Feature | Purpose | Example |
|---|---|---|
| dbt tag | Group and select dbt resources | tag:sales |
| Snowflake query tag | Identify queries in query history | dbt_beems_ecomm_gold |
## 10. Hands-On Exercise
Add these tags to the project models:
```sql
-- models/bronze/customers/stg_customers.sql
{{ config(tags=['customer', 'hourly']) }}
-- models/bronze/orders/stg_orders.sql
{{ config(tags=['sales', 'hourly']) }}
-- models/gold/facts/fct_orders.sql
{{ config(tags=['sales', 'core', 'dashboard']) }}
-- models/mart/customer_360.sql
{{ config(tags=['customer', 'dashboard']) }}
Run the customer group:
dbt run --select tag:customer
Summary
Tags make large dbt projects easier to organize, select, and operate. Use tag: to select a group and + to include related dependencies.
| Exclude | --exclude tag:temporary | Exclude tagged models |
| Downstream | tag:sales+ | Include downstream dependencies |
| Folder tag | +tags: [gold] | Tag an entire layer/folder |
| Orchestration | dbt build --select tag:hourly | Let scheduler run a group |
| Snowflake query tag | query_tag | Identify queries in Snowflake |
The key takeaway
Tags don't transform data. Tags organize dbt resources so that we can selectively execute, test, build, and orchestrate groups of models.
For your training progression, this lesson fits nicely after Aliases:
08. Aliases
↓
09. Tags
↓
10. Variables
↓
11. Jinja
↓
12. Macros
↓
13. Sources
↓
14. Tests
↓
15. Snapshots
↓
16. Incremental Models