v19 release: some structural changes in Community, Core and Premium

We recently released new versions for GA4Dataform Premium, Core and Community which contain small additions, and some renaming..

Small changes

New columns added

• • the ga4_sessions now has the first_user_traffic_source column (Premium only) 

• • the ga4_transactions table has a new property_id column

• • unique_search_term, gad_campaingid, gad_source added to the standard event_params

SQL style: THE CODE NOW SHOUTS AT YOU

We all have our preferences in coding style. Personally, I like my SQL lowercase, but only because I’m a lazy typist. I actually think upper case SQL is nice to look at.

This change is purely cosmetic, and with our new linter, we are making sure the code is consistent, more readable, and less prone to errors-by-sloppyness.

Potential breaking changes: new file locations and table names

We re-architectured our model a bit, the main changes being: everything is now a module.
Also, we renamed some modules to have better names and consistent output table names.

Biggest change for users of Community and Core: the main config file can now be found in includes/core/modules/ga4/config.js

All modules can be enabled/disabled now, even the GA4 one! So you can run our model for only Ads and GCP cost monitoring, for example.

The new structure:

GA4Dataform Core customers: your output will be 100% the same.

GA4Dataform Premium customers: it could be that some downstream custom tables need adjusting, and old table names need deleting/moving. Contact support so we can guide you through the process if needed.

Rest assured: with this new table naming and module structure, everything is now future proof and stable, and table names will not change again in the future 🙂