Skip to main content

event_time

Available in the dbt Cloud "Latest" release track and dbt Core v1.9 and higher.

dbt_project.yml
models:
resource-path:
+event_time: my_time_field
models/properties.yml
models:
- name: model_name
config:
event_time: my_time_field
models/modelname.sql
{{ config(
event_time='my_time_field'
) }}

Definition

Set the event_time to the name of the field that represents the timestamp of the event -- "at what time did the row occur" -- as opposed to an event ingestion date. You can configure event_time for a model, seed, or source in your dbt_project.yml file, property YAML file, or config block.

Here are some examples of good and bad event_time columns:

  • ✅ Good:

    • account_created_at — This represents the specific time when an account was created, making it a fixed event in time.
    • session_began_at — This captures the exact timestamp when a user session started, which won’t change and directly ties to the event.
  • ❌ Bad:

    • _fivetran_synced — This isn't the time that the event happened, it's the time that the event was ingested.
    • last_updated_at — This isn't a good use case as this will keep changing over time.

event_time is required for Incremental microbatch and highly recommended for Advanced CI's compare changes in CI/CD workflows, where it ensures the same time-slice of data is correctly compared between your CI and production environments.

Examples

Here's an example in the dbt_project.yml file:

dbt_project.yml
models:
my_project:
user_sessions:
+event_time: session_start_time

Example in a properties YAML file:

models/properties.yml
models:
- name: user_sessions
config:
event_time: session_start_time

Example in sql model config block:

models/user_sessions.sql
{{ config(
event_time='session_start_time'
) }}

This setup sets session_start_time as the event_time for the user_sessions model.

0