RE: oauth user not seeing sub-mcc or client accounts in resource_names via google ads api

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

Please be informed that I have removed your response from the forums as it contains the PII information.

Please find the below answers for your queries:

1.The listAccessibleCustomers method returns a list of resource names of customers based on your OAuth credentials. This will not necessarily include all accounts within the account hierarchy; rather, it will only include accounts where your authenticated user has been added with admin or other rights in the account. I would recommend you to go through the documentation for more information. 

2.Kindly note that we are able to retrieve the campaign details from the client account successfully through the Google Ads API. Also, note that you cannot directly retrieve the campaign data from the sub MCC account through the Google Ads API. To retrieve the data, issue separate requests against each client account under the sub manager account. However I'm providing the below GAQL query to retrieve the campaign data from the client account:

SELECT campaign.id, campaign.name, campaign.advertising_channel_type, campaign.status FROM campaign

You can use the search or searchStream methods in making the API calls while retrieving the data by specifying the customer-id as client account ID and login-customer-id as MCC account ID. Additionally, you can utilize the Google Ads Query Builder and Query Validator to build and validate the queries for retrieving the data from the Google Ads API. 

If you still face any issues, provide us with the complete API logs (request and response with request-id and request header) generated at your end for further investigation.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.

You can send the details via Reply privately to the author option, or direct private reply to this email.

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-06-27 04:44:29Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rgV1N:ref" (ADR-00315985)