feature/update-decisionlog

CHANGELOG.md

@@ -1,3 +1,8 @@
+# dbt_tiktok_ads_source v0.5.1
+[PR #14](https://github.com/fivetran/dbt_tiktok_ads_source/pull/14) includes the following updates:
+## Under the Hood:
+- Updates the [DECISIONLOG](DECISIONLOG.md) to clarify why there exist differences among aggregations across different grains.
+
 # dbt_tiktok_ads_source v0.5.0
 [PR #12](https://github.com/fivetran/dbt_tiktok_ads_source/pull/12) includes the following updates:
 ## Breaking changes

DECISIONLOG.md

@@ -0,0 +1,4 @@
+## Why don't metrics add up across different grains (Ex. ad level vs campaign level)?
+Not all ads are served at the ad level. In other words, there are some ads that are served only at the ad group, campaign, etc. levels. The implications are that since not ads are included in the ad-level report, their associated spend, for example, won't be included at that grain. Therefore your spend totals may differ across the ad grain and another grain. 
+
+This is a reason why we have broken out the ad reporting packages into separate hierarchical end models (Ad, Ad Group, Campaign, and more). Because if we only used ad-level reports, we could be missing data.s

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'tiktok_ads_source'
-version: '0.5.0'
+version: '0.5.1'
 config-version: 2
 require-dbt-version: [">=1.3.0", "<2.0.0"]
 models:

integration_tests/dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'tiktok_ads_source_integration_tests'
-version: '0.5.0'
+version: '0.5.1'
 profile: 'integration_tests'
 config-version: 2