dbt_app_reporting v0.4.0

PR #21 includes the following updates:

🚨 Breaking hanges 🚨

Identifier variables for the following packages have been updated for consistency with the source name and compatibility with the union schema feature. See the package's changelog for a full list of changes.
- dbt_apple_store
- dbt_google_play

Feature update 🎉

Unioning capability! This adds the ability to union source data from multiple app_reporting connectors. Refer to the README for more details.
Added a source_relation column in each upstream model for tracking the source of each record.
- The source_relation column is also persisted from the upstream models to the end models.

Under the hood

Included auto-releaser GitHub Actions workflow to automate future releases.

dbt_app_reporting v0.3.2

Bug Fixes

PR #19 includes the following update:

Shortened the field description for source_type in the upstream dbt_apple_store source package. This was causing an error if the persist docs config was enabled because the description size exceeded warehouse constraints.

dbt_app_reporting v0.3.1

Bug Fixes

PR #16 includes the following bug fix.

Included the country_long field in the unique combination of columns test for the app_reporting__country_report. It has been identified that Apple will sometimes provide records with different country_long names; however, they will be the same country_short. This is due to some countries having multiple country_long spelling variations.

dbt_app_reporting v0.3.0

Bug Fixes:

PR #14 includes the following changes:

This version of the transform package points to breaking changes in the upstream Google Play and Apple Store source packages in which the country code mapping tables were updated to align with Apple's format and inclusion list of country names.
- This is a 🚨breaking change🚨 as you will need to re-seed (dbt seed --full-refresh) the google_play__country_codes file and apple_store_country_codes file again.

Under the Hood:

PR #13 includes the following changes:

Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job.
Updated the pull request templates.

dbt_app_reporting v0.2.0

🚨 Breaking Changes 🚨:

PR #12 includes the following breaking changes:

Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically {{ dbt_utils.<macro> }} have been updated to {{ dbt.<macro> }} for the below macros:
- any_value
- bool_or
- cast_bool_to_text
- concat
- date_trunc
- dateadd
- datediff
- escape_single_quotes
- except
- hash
- intersect
- last_day
- length
- listagg
- position
- replace
- right
- safe_cast
- split_part
- string_literal
- type_bigint
- type_float
- type_int
- type_numeric
- type_string
- type_timestamp
- array_append
- array_concat
- array_construct
For current_timestamp and current_timestamp_in_utc macros, the dispatch AND the macro names have been updated to the below, respectively:
- dbt.current_timestamp_backcompat
- dbt.current_timestamp_in_utc_backcompat
packages.yml has been updated to reflect new default fivetran/fivetran_utils version, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

dbt_app_reporting v0.1.1-v0.1.2

Updates

README update to remove release badge as they are confusing in the current state of package/downstream tooling.

dbt_app_reporting v0.1.0

Initial Release

This is the initial release of this package.

What does this dbt package do?

Standardizes schemas from various app platform connectors and creates reporting models for all activity aggregated to the device, country, OS version, app version and traffic source
Currently supports the following Fivetran app platform connectors:
- Apple App Store
- Google Play
Generates a comprehensive data dictionary of your source and modeled App Reporting data via the dbt docs site

References

lukes/ISO-3166-Countries-with-Regional-Codes for the foundation of our country_codes mapping table

For more information refer to the README.