This source can sync data for the Google Ads.
This source is capable of syncing the following streams:
Full Refresh Sync
Replicate Incremental Deletes
This source is constrained by whatever API limits are set for the Google Ads that is used. You can read more about those limits in the google developer docs.
Google Ads Account with an approved Developer Token (note: In order to get API access to Google Ads, you must have a "manager" account. This must be created separately from your standard account. You can find more information about this distinction in the google ads docs.)
login_customer_id (you can find more information about this field in Google Ads docs)
This guide will provide information as if starting from scratch. Please skip over any steps you have already completed.
Create an Google Ads Account. Here are Google's instruction on how to create one.
Create an Google Ads MANAGER Account. Here are Google's instruction on how to create one.
You should now have two Google Ads accounts: a normal account and a manager account. Link the Manager account to the normal account following Google's documentation.
Apply for a developer token (make sure you follow our instructions) on your Manager account. This token allows you to access your data from the Google Ads API. Here are Google's instructions. The docs are a little unclear on this point, but you will not be able to access your data via the Google Ads API until this token is approved. You cannot use a test developer token, it has to be at least a basic developer token. It usually takes Google 24 hours to respond to these applications. This developer token is the value you will use in the
refresh_token. Google provides instructions on how to do this.
customer_is refer to the id of each of your Google Ads accounts. This is the 10 digit number in the top corner of the page when you are in google ads ui. The source will only pull data from the accounts for which you provide an id. If you are having trouble finding it, check out Google's instructions.
Wow! That was a lot of steps. We are working on making the OAuth flow for all of our connectors simpler (allowing you to skip needing to get a
developer_token and a
refresh_token which are the most painful / time-consuming steps in this walkthrough).
Google is very picky about which software and which use case can get access to a developer token. The Airbyte team has worked with the Google Ads team to whitelist Airbyte and make sure you can get one (see issue 1981 for more information).
When you apply for a token, you need to mention:
Why you need the token (eg: want to run some internal analytics...)
That you will be using the Airbyte Open Source project
That you have full access to the code base (because we're open source)
That you have full access to the server running the code (because you're self-hosting Airbyte)
If for any reason the request gets denied, let us know and we will be able to unblock you.
The Google Ads Query Language can query the Google Ads API. Check out Google Ads Query Language
Annotate Oauth2 flow initialization parameters in connector spec
Add custom query stream support
allow additionalProperties in spec.json
Correct query to not skip dates
Added new stream UserLocationReport
Support new Report streams
Support main streams, fix bug with exception