Sync data from Google Ads to your warehouse destination via RudderStack.
5 minute read
Google Ads is Google’s premier online advertising platform that lets advertisers display their advertisements, service offerings, and product listings to prospective customers.
This document guides you in setting up Google Ads as a source in RudderStack. Once configured, RudderStack automatically ingests your specified Google Ads data, which can then be routed to your RudderStack-supported data warehouse destination.
For more information on the conversion windows in Google Ads, refer to the FAQ section below.
Custom GAQL queries
The Custom GAQL Queries option lets you create a custom GAQL query for building a customized Google Ads report. The dashboard settings are described below:
Select resource: Select the Google Ads API resource from the dropdown.
Select: Select the relevant Attributes, Segments and Metrics from the dropdown.
Destination Table Name: Specify the table name in your warehouse destination where the results for the above query will be sent.
As you select the relevant options from the dropdown, you can observe the custom GAQL query displayed in the query box. You can also use the Reset and Edit query buttons to reset or change the query respectively.
The following image shows a sample custom GAQL query:
For more information on the Full Refresh and Incremental sync modes, refer to the Common Settings guide.
Where can I find my Google Ads customer ID?
You can find your Google Ads customer ID in the top right section of your dashboard:
What is a conversion window in Google Ads?
A conversion window is defined as the time period after the user interacts with an ad (clicks, video views, etc.) during which a conversion is recorded in Google Ads.
Is it possible to have multiple Cloud Extract sources writing to the same schema?
Yes, it is. RudderStack associates a table prefix for every Cloud Extract source writing to a warehouse schema. This way, multiple Cloud Extract sources can write to the same schema with different prefixes.
How does RudderStack count the events for Cloud Extract sources?
RudderStack counts the number of records returned by the source APIs when queried during each sync. It considers each record as an event.
How does RudderStack set the table name for the data sent via Cloud Extract sources?
RudderStack sets the table name for the resource you are syncing to the warehouse by adding rudder_ to the Table prefix you set while configuring your Cloud Extract source in the dashboard.
For example, if you set test_ as the Table prefix in the dashboard, RudderStack sets the table name as test_rudder_<resource_name>, where <resource_name> is the name of the resource you are syncing (for example, contacts, messages, etc.).
Note that RudderStack does not add the character _ to the prefix by default. Hence, you need to specify it while setting the prefix.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.