GA4 Export dbt Package (docs)

What does this dbt package do?

• Produces modeled tables that leverage GA4 Export data from Fivetran's connector in the format described by this ERD.

These tables are designed to replicate common GA4 reports. The following provides a list of all tables provided by this package along with their corresponding GA4 report.

TIP: See more details about these tables in the package's dbt docs site.

Table	GA4 Report	Description
ga4_export__traffic_acquisition_session_source_medium_report	traffic_acquisition_session_source_medium_report	Tracks sessions, events, and revenue by source and medium. Provides insights into traffic sources driving engagement.
ga4_export__user_acquisition_first_user_source_medium_report	user_acquisition_first_user_source_medium_report	Tracks how new users are acquired by first user medium and source. Includes engagement metrics and total revenue.
ga4_export__events_report	events_report	Summarizes event counts, revenue generated from events, and user engagement metrics across the app or website.
ga4_export__conversions_report	conversions_report	Tracks conversion events, key user actions, and total revenue, offering insights into conversion behavior.

How do I use the dbt package?

Step 1: Prerequisites

To use this dbt package, you must have the following:

• At least one Fivetran GA4 Export connector syncing data into your destination.
• A BigQuery, Snowflake, Redshift, PostgreSQL, or Databricks destination.

Databricks dispatch configuration

If you are using a Databricks destination with this package, you must add the following (or a variation of the following) dispatch configuration within your dbt_project.yml. This is required in order for the package to accurately search for macros within the dbt-labs/spark_utils then the dbt-labs/dbt_utils packages respectively.

dispatch:
  - macro_namespace: dbt_utils
    search_order: ['spark_utils', 'dbt_utils']

Database Incremental Strategies

Many of the models in this package are materialized incrementally, so we have configured our models to work with the different strategies available to each supported warehouse.

For BigQuery and Databricks All Purpose Cluster runtime destinations, we have chosen insert_overwrite as the default strategy, which benefits from the partitioning capability.

For Databricks SQL Warehouse destinations, models are materialized as tables without support for incremental runs.

For Snowflake, Redshift, and Postgres databases, we have chosen delete+insert as the default strategy.

Regardless of strategy, we recommend that users periodically run a --full-refresh to ensure a high level of data quality.

Step 2: Install the package

Include the following ga4_export package version in your packages.yml file:

TIP: Check dbt Hub for the latest installation instructions or read the dbt docs for more information on installing packages.

packages:
  - package: fivetran/ga4_export
    version: [">=0.1.0", "<0.2.0"] # we recommend using ranges to capture non-breaking changes automatically

Connector Restrictions

This package is built only for connectors using the default column sync mode. Additionally, it assumes the underlying schema for the connector version synced after July 24, 2023.

Intraday Events

To be completed

add notes about intraday events being synced

Syncing events from intraday tables https://fivetran.com/docs/connectors/applications/google-analytics-4-export#syncingeventsfromintradaytables

We sync data for intraday events.

We sync events from intraday tables throughout the day. Whereas, we sync daily tables at the end of the day. To differentiate the intraday events from the end-of-day events, you can filter the is_intraday column in the EVENT table.

Sampled Data

To be completed

add notes about the presence of sampled data and how that may cause different between prebuilt reports and exports

https://www.cardinalpath.com/blog/ga4-and-bigquery-why-might-data-not-match This indicator in the UI will confirm the presence of “estimated” (i.e., modeled) data, as well as the date on which this data began to be included in your UI reports.

If you have modeled data in your data, consider changing your GA4 reporting identity to “Observed” or “Device-Based.” This will remove the modeled data from your dataset, and give you results that better match against BigQuery. Keep in mind that you can switch between reporting identities at any time, without making a permanent change to your data. For example, you can disable modeled data, validate against BigQuery, and then return to included modeled data in the GA4 UI.

Key Events

According to Google Analytics, a key event is an event that's particularly important to the success of your company.

Because a key event may differ across companies, we require you specify your list of these events. This will be applied in the ga4_export__conversions_report model which filters the events_report to just key events. Additionally this will manifest in the key_events field in ga4_export__traffic_acquisition_session_source_medium_report and ga4_export__user_acquisition_first_user_source_medium_report.

To configure your key events, add the following variable to your dbt_project.yml file.

vars:
  ga4_export:
    key_events: ['click','trial_signup'] # example key events

Step 3: Define database and schema variables

By default, this package runs using your destination and the ga4_export schema. If this is not where your GA4 Export data is (for example, if your GA4 Export schema is named ga4_export_fivetran), add the following configuration to your root dbt_project.yml file:

vars:
    ga4_export_database: your_database_name
    ga4_export_schema: your_schema_name 

(Optional) Step 4: Additional configurations

Collapse/expand details

Event Date Range

Because of the typical volume of event data, you may want to limit this package's models to work with a recent date range of your GA4 Export data (however, note that all final models are materialized as incremental tables).

By default, the package looks at all events since January 1, 2024. To change this start date, add the following variable to your dbt_project.yml file:

vars:
  ga4_export:
    ga4_export_date_start: 'yyyy-mm-dd' 

Lookback Window

Events can sometimes arrive late. Since many of the models in this package are incremental, by default we look back 7 days to ensure late arrivals are captured while avoiding requiring a full refresh. To change the default lookback window, add the following variable to your dbt_project.yml file:

vars:
  ga4_export:
    lookback_window: number_of_days # default is 7

Changing the Build Schema

By default this package will build the GA4 Export staging models within a schema titled (<target_schema> + _stg_ga4_export) and GA4 Export final models within a schema titled (<target_schema> + ga4_export) in your target database. If this is not where you would like your modeled GA4 Export data to be written to, add the following configuration to your dbt_project.yml file:

models:
    ga4_export:
      +schema: my_new_schema_name # leave blank for just the target_schema
      staging:
        +schema: my_new_schema_name # leave blank for just the target_schema

Change the source table references

If an individual source table has a different name than the package expects, add the table name as it appears in your destination to the respective variable:

IMPORTANT: See this project's dbt_project.yml variable declarations to see the expected names.

vars:
    ga4_export_<default_source_table_name>_identifier: your_table_name 

Event De-Duplication

(Optional) Step 5: Orchestrate your models with Fivetran Transformations for dbt Core™

Expand for details

Fivetran offers the ability for you to orchestrate your dbt project through Fivetran Transformations for dbt Core™. Learn how to set up your project for orchestration through Fivetran in our Transformations for dbt Core setup guides.

Does this package have dependencies?

This dbt package is dependent on the following dbt packages. These dependencies are installed by default within this package. For more information on the following packages, refer to the dbt hub site.

IMPORTANT: If you have any of these dependent packages in your own packages.yml file, we highly recommend that you remove them from your root packages.yml to avoid package version conflicts.

packages:
    - package: fivetran/fivetran_utils
      version: [">=0.4.0", "<0.5.0"]

    - package: dbt-labs/dbt_utils
      version: [">=1.0.0", "<2.0.0"]

How is this package maintained and can I contribute?

Package Maintenance

The Fivetran team maintaining this package only maintains the latest version of the package. We highly recommend you stay consistent with the latest version of the package and refer to the CHANGELOG and release notes for more information on changes across versions.

Contributions

A small team of analytics engineers at Fivetran develops these dbt packages. However, the packages are made better by community contributions.

We highly encourage and welcome contributions to this package. Check out this dbt Discourse article on the best workflow for contributing to a package.

Are there any resources available?

• If you have questions or want to reach out for help, see the GitHub Issue section to find the right avenue of support for you.
• If you would like to provide feedback to the dbt package team at Fivetran or would like to request a new dbt package, fill out our Feedback Form.