6.1.0

What's Changed

• feature: add property_id as column by @FloDevelops in #321
• Fix invalid generated column names in conversion events by @jerome-laurent-pro in #327
• Query string all by @dgitis in #338
• Issue #340 fill null event key by @EvavW in #341

Additional Notes

Note that #338 introduces new behavior for the query_parameter_exclusions variable:

The query_parameter_exclusions variable now removes fragments, hash # parameters, from page_location and page_referrer. In most cases this will be an improvement in functionality. However, if you have query parameter keys using question mark, ?, or ampersand, &, that you want to remove and fragments that you don't want to remove, then you will need to override the remove_query_parameters macro.

New Contributors

• @FloDevelops made their first contribution in #321
• @jerome-laurent-pro made their first contribution in #327
• @EvavW made their first contribution in #341

Full Changelog: 6.0.2...6.0.3

6.0.2

What's Changed

• Fix uniqueness test for fct_ga4__pages by @yamotech in #305
• fix cpc classification and add test by @dgitis in #306
• Update stg_ga4__events.sql to consider campaign name (organic) by @cfrye2 in #315
• Fix error when setting a large number of properties by @yamotech in #312

New Contributors

• @cfrye2 made their first contribution in #315

Full Changelog: 6.0.1...6.0.2

6.0.1 Minor fixes

What's Changed

• Fix to filter based on dates equal to or later than the start_date by @yamotech in #304
• Update default channel grouping label to Direct by @adamribaudo-velir in #301

New Contributors

• @yamotech made their first contribution in #304

Full Changelog: 6.0.0...6.0.1

v6.0

This release includes breaking changes! Please see the details below.

What's Changed

• Allow distinct source and target projects by @adamribaudo-velir in #294

At a minimum, all users will need replace the project variable with the source_project variable and the dataset variable with the property_ids variable. Users with data across multiple projects will need to use the combined_dataset variable.

Details

Previously, the project variable was used to determine the source and target project for copying data from multiple GA4 properties. In this release, certain behaviors and variables are changed to allow for more flexible configurations. In particular, these changes allow for the scenario where the project storing raw data is read-only and cannot be written to.

• Previous variable name: project

• New variable name: source_project

  • Defines the project where the raw GA4 data is held

• Previous variable name: dataset

• New variable name: property_ids

  • An array containing a list of all GA4 property IDs to process

• New variable: combined_dataset

  • Defines the name to use when combining multiple property datasets into a single dataset

• New Behavior: The combined_dataset dataset will be written to your profile's target project, rather than the source project.

Full Changelog: 5.1.1...6.0.0

5.1.1

This release captures a few small documentation updates and 1 small acquisition label change in advance of an upcoming release containing breaking changes.

What's Changed

• fix typo by @dgitis in #287
• Bump version number in README.md for new 5.1.x versions by @rbarreca in #288
• Set "Direct" instead "(none)" as default value by @clemens7haar in #265
• Update README.md by @shreveasaurus in #293

New Contributors

• @rbarreca made their first contribution in #288
• @shreveasaurus made their first contribution in #293

Full Changelog: 5.1.0...5.1.1

5.1.0

What's Changed

• Add adapter dispatch pattern for path extraction by @adamribaudo-velir in #272
• Dedup transactions by @dgitis in #277
• Align default channel groupings with GA4 docs by @erikverheij in #282
• Explicit Item and Ecommerce field selection by @dgitis in #283

Items Fields

Since the release of version 5.0.0, Google changed format of the items record which caused the base_ga4__events model to fail. This was fixed with a simple full refresh, but that cost extra processing.

Version 5.1.0 explicitly unnests and re-nests the items and ecommerce records in the base_ga4__events model so that future changes will not break the model.

Every effort has been made to re-nest the contents of those records into the same slots which should ensure that you can upgrade without rebuilding your base_ga4__events table. However, if you run in to an error with the base_ga4__events model on upgrading, you will either need to run a full refresh to fix the error or over-ride the base_select macro with your own version where the order of the items and ecommerce fields matches that seen in your existing base_ga4__events table.

New Contributors

• @erikverheij made their first contribution in #282

Full Changelog: 5.0.0...5.1.0

5.0.0

Welcome to a post-UA world. There's no turning back now!

In this release, the major change is that we've removed support for 'dynamic' incremental loads. Instead the static_incremental_days variable is now required and is the only mechanism for incrementally loading data. The recommended setting is 3 days to allow for re-processing of 72 hours of data which is the time window in which Google may modify past events.

Other improvements include an improved dedupe process, better cleanup of tables in multi-property configurations, and improvements to channel mapping.

What's Changed

• fix code getting accidentally commented out by @dgitis in #228
• Refactor daily & streaming support by @adamribaudo-velir in #188
• Remove all references to dynamic incremental load strategy by @adamribaudo-velir in #240
• Allow range of dbt_utils versions by @Stephen986 in #242
• Improvements to channel mapping based on Google's definitions by @adamribaudo-velir in #245
• check for intraday table before processing union operation by @adamribaudo-velir in #250
• Query param extraction variable (can be used to pull out click IDs) by @adamribaudo-velir in #252
• fix combine property data to drop old intraday tables by @FlorianASchroeder in #256
• fix deduplication by defining order in event_params by @FlorianASchroeder in #259
• Fix streaming support for multi property configurations by @adamribaudo-velir in #257

New Contributors

• @Stephen986 made their first contribution in #242
• @FlorianASchroeder made their first contribution in #256

Full Changelog: 4.0.0...5.0.0

4.0.0

In version 4, there was at least one breaking change and several improvements.

#181 introduced the idea of a client_key to replace the user_pseudo_id. client_key includes the stream ID in the identifier which makes it more unique than user_pseudo_id alone. This will column name may break existing assets that depend on the mart tables.

#196 introduces last non-direct session attribution (similar to how GA3 calculated session attribution by default)

What's Changed

• Update .gitattributes by @ivan-toriya in #180
• Update user_pseudo_id to client_key by @TannerHopkins in #181
• Refactor combined_property_data macro by @adamribaudo-velir in #183
• fix-documentation-error-in-yml-base_ga4__events by @xhulianpapa in #184
• multi-site support for streaming frequency by @dgitis in #187
• add user_id and session_number to session tables by @dgitis in #189
• add stream_id to stg_ga4__event_items by @dgitis in #190
• update package hub install instructions by @dgitis in #194
• Last non-direct session attribution by @adamribaudo-velir in #196
• partition pruning fct_ga4__pages by @dgitis in #197
• Fix test on user_id_or_client_key in fct_ga4__user_ids model by @adamribaudo-velir in #195
• add view_item to event_items staging model by @dgitis in #202
• update standard ecommerce params by @dgitis in #200
• Correct README notes on derived session properties location. by @elyobo in #227
• remove default purchase aggregations by @adamribaudo-velir in #206

New Contributors

• @ivan-toriya made their first contribution in #180
• @TannerHopkins made their first contribution in #181
• @xhulianpapa made their first contribution in #184

Full Changelog: 3.2.1...3.2.2

3.2.1

What's Changed

• Hotfix: restore create_custom_event macro by @dgitis in #179

Full Changelog: 3.2.0...3.2.1

3.2.0

Overview

Some new features have been added:

• Calculating time on page (details in #127)
• Incremental, partitioned session dim & fact tables to support large installs (#175)

Along with some general refactoring and fixes.

What's Changed

• Time on page by @dgitis in #127
• base_select macro and combine property enhancement by @dgitis in #166
• fix typo in base_ga4__events.yml by @eliesg in #172
• add session start date/timestamp to session dim model by @adamribaudo-velir in #168
• Warn instead of error when null page location by @adamribaudo-velir in #177
• Fix: Multi property sources from source database, not target database by @adamribaudo-velir in #176
• Incremental, partitioned session dim and fact tables. Allows for dimensional modeling on very large installs by @adamribaudo-velir in #175

New Contributors

• @eliesg made their first contribution in #172

Full Changelog: 3.1.0...3.2.0