The HubSpot dbt package offers data models to help you transform and analyze HubSpot data. It's designed to integrate seamlessly with the dlt HubSpot pipeline, which extracts and loads HubSpot data into your data warehouse.
This package is perfect for dbt users who want to integrate HubSpot data into their analytics workflows without building models from scratch.
- Staging Models: Clean and prepare raw HubSpot data for downstream analysis.
- Mart Models: Pre-built dimension and fact tables for key HubSpot entities like contacts, deals, companies, and tickets.
- Incremental Loading: Supports incremental data processing to optimize performance.
- Easy Integration: Designed to work out-of-the-box with the dlt HubSpot pipeline.
- dbt Core installed in your environment.
- Access to a supported data warehouse: BigQuery, Snowflake, Redshift, Athena, or PostgreSQL.
- The dlt HubSpot pipeline is set up and running.
-
Install dlt:
pip install dlt
-
Configure the Pipeline: Follow the dlt HubSpot pipeline documentation to set up your pipeline. Ensure you have your HubSpot API key and destination credentials configured.
-
Run the Pipeline: Extract and load data from HubSpot into your data warehouse by running the pipeline.
- Install the HubSpot dbt package into your dbt environment.
- Configure your 'dbt_project.yml' file with the appropriate connection details for your data warehouse.
- Ensure the data from your dlt HubSpot pipeline is available in your warehouse.
This is how the tables in dbt package look like:
dbt_<pipeline-name>/
├── analysis/
├── macros/
├── models/
│ ├── marts/
│ │ ├── dim_<pipeline-name>__dlt_loads.sql
│ │ ├── dim_<pipeline-name>__companies.sql
│ │ └── dim_<pipeline-name>__contacts__deals.sql
│ │ └── dim_<pipeline-name>__contacts__tickets.sql
│ │ └── dim_<pipeline-name>__contacts.sql
| | └── fact_<pipeline-name>__deals.sql
| | └── fact_<pipeline-name>__tickets.sql
│ ├── staging/
│ │ ├── sources.yml
│ │ ├── stg_<pipeline-name>__dlt_loads.sql
│ │ ├── stg_<pipeline-name>__companies.sql
│ │ └── stg_<pipeline-name>__contacts__deals.sql
│ │ └── stg_<pipeline-name>__contacts__tickets.sql
│ │ └── stg_<pipeline-name>__contacts.sql
| | └── stg_<pipeline-name>__deals.sql
| | └── stg_<pipeline-name>__tickets.sql
│ ├── <pipeline-name>_dlt_active_load_ids.sql # Used for incremental processing of data
│ └── <pipeline-name>_dlt_processed_load.sql # Used for incremental processing of data
├── tests/
├── dbt_project.yml
└── requirements.txt
Execute the dbt models to transform the raw HubSpot data into useful tables:
dbt run
You can use the 'run_hubspot_dbt.py' script to execute your dbt transformations and load the results into a new dataset named
<original-dataset>_transformed
and runs the dbt tests.To use, please ensure you configure your dlt pipeline name and destination correctly.
To check for issues, run the dbt tests:
dbt test
While this package provides a solid foundation, you can customize it to suit your specific needs:
- Modify the models to align with your business logic.
- Add relationships between tables by modifying your dlt pipeline schema.
The dimensional modelling part of the package was created with a declarative code generator and suffers from limitations inherent to modelling raw data directly. We advise you consider the raw data tables and adjust the modelled layer as needed.
The dbt model above can be further customized according to the requirements. Using this package you'll get a basic template for data model which can be further modified as required.
Please note that this is a starting template for your data model and is not the final product. It is advised to customize the data model as per your needs.
Here's the link to the DB diagram: link.
This package was created using the dlt-dbt-generator by dlt-plus. For more information about dlt-plus, refer to the dlt-plus documentation. To learn more about the dlt-dbt-generator, consult the dlt-dbt-generator documentation.
The dimensional modelling part of the package was created with a declarative code generator and suffers from limitations inherent to modelling raw data directly. We advise you consider the raw data tables and adjust the modelled layer as needed