fivetran / dbt_ad_reporting

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.
https://fivetran.github.io/dbt_ad_reporting/#!/overview
Apache License 2.0
146 stars 55 forks source link

BUG - No Account, AdGroup, or Campaign Info in Ad_Reporting model #31

Closed csoule-shaker closed 2 years ago

csoule-shaker commented 2 years ago

Are you a current Fivetran customer? Chris Soule, Data Architect Interworks

Describe the bug In the Ad_Reporting model there was no Account, AdGroup, or Campaign data in the table even though it is in the source.

Steps to reproduce

  1. Target a Google Ad Connector
  2. Run package
  3. See Nulls in the Account, AdGroup, or Campaign fields

Expected behavior Account, AdGroup, or Campaign data carried forward to the final Ad_Reporting model

Project variables configuration

copy dbt_project.yml here

Package Version

name: 'ad_reporting'
version: '0.5.0'
config-version: 2

Warehouse

- [ ] BigQuery - [ ] Redshift - [X] Snowflake - [ ] Postgres - [ ] Databricks - [ ] Other (provide details below) **Additional context** In the get_ad_stats_columns macro in google_ads_source package a lot of columns didn't have an alias specified properly and instead used the staging column name as the alias name which didn't match with the source fields. Example: AD_ID = ID in the source table Data Error: ![image](https://user-images.githubusercontent.com/94551079/144096074-dd0105bd-3228-4356-b8c4-ff8e5bf5a370.png) Original get_ad_stats_columns macro: ![image](https://user-images.githubusercontent.com/94551079/144096519-a21a8830-41e9-4ef5-8e3f-5973860775b3.png) What is needs to be corrected: ![image](https://user-images.githubusercontent.com/94551079/144096347-ad25c016-f6fd-4e64-ab14-16d262b2f910.png) **Screenshots**

Please indicate the level of urgency Medium/High. Performing a POC

Are you interested in contributing to this package?

csoule-shaker commented 2 years ago

This was determined to be due to a configuration issue between using adwords API and Google_ads API. Closing issue.