Hi Ryan,
Thank you for reaching out to the Google Ads API support team.
By reviewing your concern, I understand that you are facing an issue while adding a service account to Google Ads. Please note that the service account must be correctly linked to the Google Ads account via the OAuth2 assertion flow and the email address you may have used to generate the credentials should have access or be associated with Google Ads accounts.
Here are some guidelines, to connect to Google Ads API using a Google service account, you will need a
Google Workspace domain since it is a prerequisite for using service accounts. You need to follow all the mentioned
prerequisites:
- The service account that you created needs to be granted domain wide delegation access by a super administrator for the domain.
- Using a Google Ads user with permissions on the Google Ads account you want to access.
- Make sure that you have your own domain registered with Google Workspace.
- Service accounts will have the ability to impersonate any user in the domain.
You may refer to this “
Service Accounts” documentation that discusses how to access the Google Ads API with service accounts.
In addition, we strongly recommend using
OAuth2 installed app or web flows instead of service accounts unless you need domain-specific features (for example, impersonation). OAuth2 installed application and web flows require user interaction only once, when access to the account is granted. You need to implement the code set up on your end to make calls using service accounts.
I hope this helps. Kindly get back to us if you have any further questions related to the Google Ads API.
This message is in relation to case "ref:!00D1U01174p.!5004Q02qXRML:ref"
Thanks,
 |
Google Ads API Team |
