https://github.com/rudderlabs/dbt-events-registry
Using DBT for Creating Events Registry on RudderStack - an open-source, warehouse-first customer data pipeline and Segment alternative.
https://github.com/rudderlabs/dbt-events-registry
dbt rudderstack
Last synced: 2 months ago
JSON representation
Using DBT for Creating Events Registry on RudderStack - an open-source, warehouse-first customer data pipeline and Segment alternative.
- Host: GitHub
- URL: https://github.com/rudderlabs/dbt-events-registry
- Owner: rudderlabs
- License: mit
- Created: 2020-06-04T09:57:23.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2024-02-21T13:51:09.000Z (about 2 years ago)
- Last Synced: 2026-01-29T21:35:24.407Z (3 months ago)
- Topics: dbt, rudderstack
- Homepage: https://www.rudderstack.com
- Size: 13.7 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Events Registry using DBT and RudderStack
This repository contains a sample DBT project for RudderStack. It can be applied on the RudderStack data residing in Google BigQuery.
## Overview
This DBT project is built on top of the source table `tracks` which is created by default in all the RudderStack warehouse destinations.
The `Events Registry` table essentially contains information like `first triggered time`, `last triggered time` and aggregates `like
total count`, `total user count` and `daily average` corresponding to each type of event routed via the RudderStack SDK(s).
The `Events Registry Last N Days` table creates the same aggregates as above with the only difference being that it is for records up till
N days in the past. The value of N can be changed in the query. The resulting table will remain the same; there is an attribute
`window-width`which will show the value of N used to generate the record. Since the data in the N Days table is for a limited time
window and not for the entire lifecyle of the RudderStack installation - `first_triggered_time` and `last_triggered_time` are not
applicable in this case.
## How to Use This Repository
This project was created on the [**DBT Cloud**](https://cloud.getdbt.com). Hence, there is no `profiles.yml` file with the connection information.
Developers who want to execute the models on the Command Line Interface (CLI) mode will need to create additional configuration files
following the directions provided [**here**](https://docs.getdbt.com/docs/running-a-dbt-project/using-the-command-line-interface/)
There is only one model to be built - `dbt_event_registry`
**Important**: Please remember to change `schema` in `tracks.yml`, `dbt_event_registry.sql` and `dbt_event_registry_last_N_days` to your database schema.
# What is RudderStack?
[RudderStack](https://rudderstack.com/) is a **customer data pipeline** tool for collecting, routing and processing data from your websites, apps, cloud tools, and data warehouse.
More information on RudderStack can be found [here](https://github.com/rudderlabs/rudder-server).
## Contact us
If you come across any issues while configuring or using this project, please feel free to start a conversation on our [Slack](https://resources.rudderstack.com/join-rudderstack-slack) channel. We will be happy to help you.