This package models Google Ads data from Fivetran's connector.

This package contains staging models, designed to work simultaneously with our Google Ads modeling package. The staging models name columns consistently across all packages:

• Boolean fields are prefixed with is_ or has_
• Timestamps are appended with _timestamp
• ID primary keys are prefixed with the name of the table. For example, the campaign table's ID column is renamed campaign_id.

Check dbt Hub for the latest installation instructions, or read the dbt docs for more information on installing packages.

To use this package, you will need to pull the following reports and columns through Fivetran:

• Final URL Performance:
  • account_descriptive_name
  • ad_group_id
  • ad_group_name
  • ad_group_status
  • campaign_id
  • campaign_name
  • campaign_status
  • clicks
  • cost
  • date
  • effective_final_url
  • external_customer_id
  • impressions
• Criteria Performance:
  • account_descriptive_name
  • ad_group_id
  • ad_group_name
  • ad_group_status
  • campaign_id
  • campaign_name
  • campaign_status
  • clicks
  • cost
  • criteria
  • criteria_destination_url
  • criteria_type
  • date
  • external_customer_id
  • id
  • impressions
• Click Performance:
  • account_descriptive_name
  • ad_group_id
  • ad_group_name
  • ad_group_status
  • campaign_id
  • campaign_name
  • campaign_status
  • clicks
  • criteria_id
  • date
  • external_customer_id
  • gcl_id

The package assumes that these three tables are named final_url_performance, click_performance, and criteria_performance. If in your warehouse they are named something else, you can point the package their location with the google_ads__final_url_performance, google_ads__click_performance, and google_ads__criteria_performance variables:

# dbt_project.yml

...
config-version: 2

vars:
    google_ads__final_url_performance: "{{ ref('a_model_you_wrote') }}"
    google_ads__click_performance: adwords.click_performance_report

By default, this package will look for your Google Ads data in the google_ads schema of your target database. If this is not where your Google Ads data is, please add the following configuration to your dbt_project.yml file:

# dbt_project.yml

...
config-version: 2

vars:
    google_ads_schema: your_schema_name
    google_ads_database: your_database_name 

Additional contributions to this package are very welcome! Please create issues or open PRs against master. Check out this post on the best workflow for contributing to a package.

• Provide feedback on our existing dbt packages or what you'd like to see next
• Find all of Fivetran's pre-built dbt packages in our dbt hub
• Learn more about Fivetran in the Fivetran docs
• Check out Fivetran's blog
• Learn more about dbt in the dbt docs
• Check out Discourse for commonly asked questions and answers
• Join the chat on Slack for live discussions and support
• Find dbt events near you
• Check out the dbt blog for the latest news on dbt's development and best practices