Fivetran's ad reporting dbt package. Combine your Facebook, Google, Pinterest, LinkedIn, Twitter, Snapchat, Microsoft, TikTok, Reddit, Amazon, and Apple Search advertising metrics using this package.
The keyword_id field has been added to the ad_reporting__keyword_report model for the Twitter Ads platform.
Bugfixes
The not_null test on the ad_reporting__keyword_report has been adjusted to be tested on the keyword_id as opposed to the keyword_text. This is needed as there may be times where keyword historical records may be removed and lose reference in an upstream join. As such, the text may be lost and the null test should be applied to the ID instead.
Contributors
@clay-walker for being instrumental in understanding and addressing this issue. (#63)
Did you update the CHANGELOG?
[X] Yes
Does this PR introduce a breaking change?
[ ] Yes (please provide breaking change details below.)
[X] No (please provide an explanation as to how the change is non-breaking below.)
Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)
[X] Yes
Is this PR in response to a previously created Bug or Feature Request
[X] Local (please provide additional testing details below)
Select which warehouse(s) were used to test the PR
[X] BigQuery
[X] Redshift
[X] Snowflake
[X] Postgres
[X] Databricks
[ ] Other (provide details below)
Provide an emoji that best describes your current mood
👨🚀
**Feedback**
We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your [feedback](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.
Are you a current Fivetran customer?
Fivetran created PR
What change(s) does this PR introduce?
Feature Enhancement
keyword_id
field has been added to thead_reporting__keyword_report
model for the Twitter Ads platform.Bugfixes
not_null
test on thead_reporting__keyword_report
has been adjusted to be tested on thekeyword_id
as opposed to thekeyword_text
. This is needed as there may be times where keyword historical records may be removed and lose reference in an upstream join. As such, the text may be lost and the null test should be applied to the ID instead.Contributors
Did you update the CHANGELOG?
Does this PR introduce a breaking change?
Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)
Is this PR in response to a previously created Bug or Feature Request
How did you test the PR changes?
Select which warehouse(s) were used to test the PR
Provide an emoji that best describes your current mood
👨🚀 **Feedback** We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your [feedback](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.