Hi Jose,
Thank you for reaching out to our API support team.
Kindly not that the NOT_ADS_USER error usually occurs when the login used to generate the access token is not associated with any Google Ads account. Make sure to log in with a valid Google Ads account (typically your manager account) for the OAuth flow.
To investigate the issue further, could you please provide the complete
request and
response logs, with the
request-id? If you haven't yet, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from this
link.
Also, could please confirm if you followed all the prerequisites for service accounts? If not, you may refer to this
guide to confirm if you already followed every step of the service account, specifically the
prerequisites. If the issue persists, please provide us the user account / email address that you've used to set up the service account. We are referring here to the user account / email address for the Google API Console project that has
been configured for the Google Ads API. You can provide these details via Reply privately to author option. If this option is not available, you may send the details directly to our
googleadsa...@google.com alias instead.
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.
Thanks,
 |
| Nirmitabahen Gaurav |
| Google Ads API Team |
|
|
| |

ref:_00D1U1174p._5004Q2bm7gu:ref