Google Ads: Setup guide#
This guide explains how to collect data from Google Ads.
Prerequisites#
Before you start collecting data from Google Ads, perform all of the following actions:
Ensure that the account you use to connect to Google Ads has Read only or higher permissions. For more information, see the Google Ads documentation.
To collect invoice data, activate monthly invoicing in your Google Ads account. For more information, see the Google documentation.
Creating a datastream to collect data from Google Ads#
The basics of creating a datastream to collect data from any data source are explained in our guide to Collecting data in Adverity. This guide contains information about the specific steps to create a datastream to fetch data from Google Ads.
Configuration: Choose the data you want to collect from Google Ads#
Note
This connector reports data in the timezone of the authorized customer account.
To choose what data to collect and customize the Google Ads datastream configuration, follow these steps:
(Optional) Rename your datastream.
In MCCs, Customers, and Campaigns, select the My Client Centers accounts (MCCs), customers, and campaigns for which to collect data. If you do not select any items in a drop-down list, Adverity collects data for all items in the drop-down list.
In Report type, select the type of data to collect from Google Ads. The selected report type determines the additional fields to populate.
In Resource level, select a level in the hierarchy of Google Ads resources. Adverity generates a report for this level. For more information, see the Google documentation.
In Segments, select the categories that Adverity uses to divide and group your data. You can only select one of the following date segments: Day, Week, Month, Quarter. The selected date segment determines the date range you can choose later when you fetch data. For more information, see Selecting the date range for a fetch.
In Metrics and Attributes, change the list of fields that you want to see in your data extract.
Note
Google Ads considers some metrics to be attributes. If you cannot see a specific metric in the Metrics drop-down list, look in the Attributes drop-down list.
In Billing Setups, select the billing setups for which to collect data. If you do not select any billing setups in a drop-down list, Adverity collects data for all items in the drop-down list.
This field is visible if you select Invoice in Report type. The items selected in the MCCs and Customers fields determine which billing setups you can select.
In Recommendation fields, change the list of fields that you want to see in your data extract.
This field is visible if you select Recommendation in Report type.
What’s next?#
Apply Data Mapping to your collected data to harmonize data collected from different sources in Adverity.
Transform your data to meet your needs by creating and applying transformations to your datastream.
Load your data into Explore & Present to visualize your data in Adverity.
Load your data into an external destination of your choice.
Troubleshooting Google Ads#
I see an error message when fetching data from Google Ads#
The
Customer with ID [ID] has a policy to enforce 2-Step Verification, but the user is not enrolled
error message appears when the user who has authorized the connection to
Google Ads requires two-factor authentication.
To resolve this issue, the user who authorized the connection must log in to Google Ads and activate two-factor authentication for their account and any sub-accounts.
Accounts are missing from the data I have fetched from Google Ads#
Adverity synchronizes accounts daily around midnight UTC. This sycnhronization has lower priority than manual and scheduled fetches. As a result, if you perform or schedule a high number of fetches, accounts will not be synchronized until after these fetches are complete. Additionally, if you add an account after the daily synchronization and then fetch data, the newly added account will not appear in the data. It will only be included after the next synchronization.
To resolve this issue, manually synchronize the metadata for the authorization you are using to fetch data. For more information, see Synchronizing metadata.