Hi,
Thank you for reaching out to the Google Ads API support team.
With regard to your concern for the application type, as per this documentation (https://developers.google.com/google-ads/api/docs/oauth/cloud-project#create_a_client_id_and_client_secret) in creating client ID and client secret, you can select either Desktop app or Web application as the app type, depending on your use case. Then for the refresh token, if you're using our client library, you can check this documentation guide (https://developers.google.com/google-ads/api/docs/first-call/refresh-token) on how to generate it.
In addition to that, to enable API access, first obtain the required OAuth2 credentials. Then, add the authorization and account details to a config file. Once the config file is set up, you're ready to call the API. Kindly check this (https://developers.google.com/google-ads/api/docs/first-call/overview), for more information.
![]() |
Google Ads API Team |
Hi,
Thanks for getting back to us.
Kindly note that we have limited knowledge on third-party tools like Google ads connector on Azure Data Factory as our team specializes in Google Ads API related concerns and technical implementations only.
With regards to your refresh token concern, as mentioned in our previous email, we highly recommend going through our Quickstart guide (https://developers.google.com/google-ads/api/docs/first-call/overview) and learn about the refresh token. Because OAuth2 access expires after a limited time, an OAuth2 refresh token is used to automatically renew OAuth2 access.
With regards to your concern about the client libraries, Google Ads API offers client libraries (https://developers.google.com/google-ads/api/docs/client-libs) that provide high-level views and basic building blocks of Google Ads API functionality, making it easier to develop apps quickly. It is highly recommended starting out with one if you're new to the API.