This adapter relies on a project app_marketing_analytics_config as specified in the manifest.lkml file. This project needs to include an adwords_config.view.lkml file.

For example:

view: adwords_config {
  extension: required

  dimension: adwords_schema {
    hidden: yes
    sql:adwords;;
  }
}

ad.view:

• ad_adapter
  • external_customer_id
  • campaign_id
  • ad_group_id
  • creative_id
  • creative
  • status_active

ad_group.view:

• ad_group_adapter
  • external_customer_id
  • campaign_id
  • ad_group_id
  • ad_group_name
  • status_active

campaign.view:

• campaign_adapter
  • external_customer_id
  • campaign_id
  • campaign_name
  • status_active
  • budget_id
  • amount

customer.view:

• customer_adapter
  • external_customer_id

geo.view

• geotargeting
  • state
  • country_code
  • name
  • postal_code

keyword.view

• keyword_adapter
  • external_customer_id
  • campaign_id
  • ad_group_id
  • criterion_id
  • criteria
  • status_active
  • bidding_strategy_type

ad_impressions.view

• _date
• ad_network_type
• device_type
• cost
• impressions
• interactions
• clicks
• conversions
• conversionvalue
• averageposition

Account Stats

• ad_impressions_adapter
• ad_impressions_hour_adapter
  • hour_of_day

Campaign Stats

• ad_impressions_campaign_adapter
• ad_impressions_campaign_hour_adapter
  • hour_of_day

Ad Group Stats

• ad_impressions_ad_group_adapter
• ad_impressions_ad_group_hour_adapter
  • hour_of_day

Keyword Stats

• ad_impressions_keyword_adapter

Ad Stats

• ad_impressions_ad_adapter

Targeting Reports

• ad_impressions * [age_range, audience, gender, geo, parental_status, video]

This Block is modeled on the schema from Fivetrans's Google AdWords ETL.

The schema documentation for AdWords can be found in Google's docs.

• Entity Tables and Stats Tables - There are several primary entities included in the AdWords data set, such as ad, ad group, campaign, customer, keyword, etc.. Each of these tables has a corresponding "Stats" table, which includes all the various metrics for that entity. For example, the "campaign" entity table contains attributes for each campaign, such as the campaign name and campaign status. The corresponding stats table - "Campaign Basic Stats" contains metrics such as impressions, clicks, and conversions. These stats tables are mapped to an ad_impression explore as an interface to the Looker Marketing Analytics application.