OAuth differences between AdWords and Google Ads API

[Markus Heiden]

Hi,

I experienced some differences in the authentication between AdWords and Google Ads API access using the Java libs.

We have a setup with

1) The main MCC account that gets authenticated.

2) Below that a MCC which we use as "clientCustomerId" / "login-customer-id".

3) Below that a "normal" account.

This setup works fine with the AdWords API. When using this with the Google As API e.g. to access the sitelinks of the account, a USER_PERMISSION_DENIED error is raised. 

In other kinds of setups, our Google Ads API access works fine though. So our code seems to be correct.

Is the "login-customer-id" required to be the authenticated main MCC account instead?
Why is there a difference in the behavior between AdWords and Google Ads API?

I apologize if this has already been answered elsewhere. But I was able to find a definitive answer to that in the other posts.

Regards,
Markus

[Google Ads API Forum Advisor]

Hello,  

Thanks for reaching out to the Google Ads API support team. 
Please find the answer for your following questions:

• Is the "login-customer-id" required to be the authenticated main MCC account instead?

-Yes, you should specify the MCC as the login-customer-id if you are authenticating from an MCC account. You can refer to this page login-customer-id to get more information.

• Why is there a difference in the behavior between AdWords and Google Ads API?

-There are small differences, but also there are carryover concepts between AdWords and Google Ads API. You can refer to this page on carryover concepts.

As you’ve mentioned that you’ve encountered the error ‘USER_PERMISSION_DENIED’, it usually has the following root causes:

• The link between the manager and client account was removed.
• Your OAuth credentials are for a user who does not have access to the client customer ID specified or any of its manager accounts.

 

Best regards,

Jakeia Sabrina Google Ads API Team

ref:_00D1U1174p._5004Q2QEO3x:ref