Load adwords data into your data warehouse Segment makes it easy to get your data from Google AdWords (and lots of other sources) into your Data Warehouse for advanced analysis.
Take your company’s analysis to the next level by having SQL access to all your Google AdWords data alongside your customer event data in Redshift and Postgres.
With your Google AdWords data in your warehouse, you’ll be able to analyze your campaigns, ad set, ads and ad insights in SQL. Even cooler, you’ll be able to join your Google AdWords data with the Segment event data you’re already sending to your warehouse, so you can now do things like combining your advertising spend and product usage data, analyzing advertising impact on new sales leads and understand paid acquisition impact on support load.
From your workspace’s
Give the source a nickname and a schema name. The nickname will be used to designate the source in the Segment interface, and the schema name is the namespace you’ll be querying against in your warehouse. Both can be whatever you like, but we recommend sticking to something that reflects the source itself, like
AdWordsfor nickname and
adwords_usafor the schema name.
Finally, just click Connect on the next page to OAuth into Google.
AdWords has a sync component, which means we’ll make requests to their API on your behalf on a 3 hour interval to pull the latest data into Segment. In the initial sync, we’ll grab all the Adwords objects (and their corresponding properties) according to the Collections table below. The objects will be written into a separate schema, corresponding to the source instance’s schema name you designated upon creation. For example, if you went with
ads collection will be accessible at
adwords.ads in SQL.
Our sync component uses an upsert API, so the data in your warehouse loaded via sync will reflect the latest state of the corresponding resource in AdWords. For example, if
100 between syncs, on its next sync that tickets status will be
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources will sync with Segment every 3 hours. Depending on your Warehouses plan, we will push the Source data to your warehouse on the interval associated with your billing plan.
For a complete visual breakdown of the AdWords collections, all their properties, and ID linkages between objects, view the visual schema here.
Collections are the groupings of resources we pull from your source. In your warehouse, each collection gets its own table.
|ad_groups||object||An ad group is a set of ads that share the same daily or lifetime budget, schedule, bid type, bid info, and targeting data|
|ads||object||An ad object contains the data necessary to visually display an ad and associate it with a corresponding ad set.|
|campaigns||object||A campaign is a grouping of ad sets which are organized by the same business objective.|
|campaign_performance_report||object||Campaign performance reports include a daily snapshot of performance statistics per campaign|
|click_performance_report||object||Click performance reports include stats at the click level, including both valid and invalid clicks|
When setting up your AdWords Source, you may notice that we don’t list all AdWords accounts your Google user can view. This is because AdWords API does not expose a list of “managed” or sub-accounts to non-administrator via the API. That said, if you have read permissions to the account, you can enter your AdWords Customer ID directly. For more information about finding your AdWords Customer ID, see here.
What unit is money in?
Currency values in AdWords are in micros, or one millionth of the smallest unit. For example, in USD, the value for
campaign.budget would be in one millionth of a cent.
What AdWords MCC do you sync?
By default, we sync the “primary” AdWords account connected to your Google account, but if you’d like to override this, you can specify an AdWords Customer ID in settings.