Closed zem360 closed 5 months ago
@zem360 thanks for this! Heads up that variables are globally scoped, so can you rename your schema_name
, paid_sources
, extra_event_params
etc to be a bit more namespaced to this specific package? Otherwise you're likely to hit collisions with people's existing vars in their own project.
Hey @joellabes ,
Thanks for spotting this. We have prefixed the mentioned variables with the package name ga4_data
which should circumvent collisions with existing variables.
Description
Tell us about your new package! The Google Analytics 4 dbt package for analysis of events data. This versatile package processes GA4 events data across various databases.
Link to your package's repository: https://github.com/dlt-hub/dbt_ga4
Checklist
This checklist is a cut down version of the best practices that we have identified as the package hub has grown. Although meeting these checklist items is not a prerequisite to being added to the Hub, we have found that packages which don't conform provide a worse user experience.
First run experience
Customisability
Packages for data transformation (delete if not relevant):
Dependencies
Dependencies on dbt Core
require-dbt-version
range indbt_project.yml
. Example: A package which depends on functionality added in dbt Core 1.2 should set itsrequire-dbt-version
property to[">=1.2.0", "<2.0.0"]
.Dependencies on other packages defined in packages.yml:
Interoperability
{{ dbt.except() }}
and{{ dbt.type_string() }}
.users
.Versioning