I have all of the same questions as the original poster and I'm very satisfied with this response. I think it would be great if people would "show some love" for this hardworking support team member by sharing this helpful reply on social media!
I do have one quick follow-up question though. 1. Is all of the documentation for the Google Ads API that you shared in your first link out of scope for the Google Ads API support team or only some parts of it? https://developers.google.com/google-ads/api/docs/get-started/introduction#prerequisites Apologies in advance if the entirety of the Google Ads official API documentation are out of scope for the google Ads API Support Team. Please let me know if there's a simple form I can fill out to get a reply within 1-4 weeks for an answer to this question, thanks. I hope as many people as possible inside and outside of Google get to see how one of the most exceptional "unsung heroes" of Google treats customers every day! On Tuesday, August 19, 2025 at 5:05:35 PM UTC-7 Google Ads API and AdWords API Forum wrote: > Hi, > > Thank you for reaching out to the Google Ads API support team. > > Upon checking your concerns, it is observed that your queries are related > to the developer token and their access levels. > > Kindly note that the concerns related to *developer tokens* are out of > scope for the Google Ads API support team, as our team specializes in *Google > Ads API* <https://developers.google.com/google-ads/api/docs/start>-related > concerns and *technical implementations* only. > > Since your concern*, “developer token access levels *” does not fall > under the Google Ads API support team, with this, I highly recommend you > reach out to the *Google Ads API Compliance* > <https://support.google.com/adspolicy/contact/contact_ads_api> team, as > they are better equipped to assist you on this. > > Meanwhile, please refer to the *Obtain a developer token* > <https://developers.google.com/google-ads/api/docs/get-started/dev-token> > and *Access Levels and Permissible Use* > <https://developers.google.com/google-ads/api/docs/access-levels> API > documentation for more information regarding developer tokens and their > access levels. > > Thanks & Regards, > > Google Ads API support team. > > On Friday, August 15, 2025 at 5:39:55 AM UTC+5:30 [email protected] > wrote: > >> *Dear Google Ads API Support Team,* >> >> We are developing a Google Ads analysis tool and need clarification on >> the specific access requirements for different developer token levels. We >> want to ensure we choose the correct path for our application architecture. >> >> *Our Goal:* We want to build a tool where users can: >> >> 1. Authenticate with their Google account via OAuth2 >> 2. Connect their Google Ads accounts to our application >> 3. Allow our tool to read campaign data from their accounts for >> analysis purposes >> 4. Provide a seamless user experience similar to tools like Shopify's >> Google Ads integration >> >> *Our Current Setup:* >> >> - We have a Basic Access developer token >> - We have a Google Ads Manager Account (MCC) >> - We have implemented OAuth2 authentication >> - Our tool currently works with accounts that are linked to our MCC >> >> *Specific Questions We Need Answered:* >> >> 1. *Basic Access Scope:* With a Basic Access developer token, can we >> access Google Ads accounts that are NOT linked to our MCC, provided we >> have >> valid OAuth2 consent from the account owner? >> 2. *MCC Linking Requirement:* Is MCC manager account linking a >> technical requirement for Basic Access tokens, or is it only a >> requirement >> during the application process ("Ensure you have linked all of your >> active >> Google Ads accounts to the manager account with the API token")? >> 3. *Standard Access Difference:* What are the specific technical >> differences between Basic Access and Standard Access regarding account >> access permissions? Does Standard Access remove any MCC linking >> requirements that Basic Access has? >> 4. *User Account Discovery:* Can a Basic Access token discover/list >> Google Ads accounts that a user has access to but are not linked to our >> MCC? >> 5. *Cross-Account API Calls:* If a user grants OAuth2 permission for >> their Google Ads account (customer ID: 123-456-7890) but this account is >> not linked to our MCC, will API calls using our Basic Access developer >> token + their OAuth2 token succeed or fail? >> >> *Example Scenario:* User owns Google Ads account 123-456-7890. User >> grants OAuth2 permission to our application. Our MCC (456-789-0123) is NOT >> a manager of account 123-456-7890. Using our Basic Access developer token + >> user's OAuth2 token, can we make API calls to read campaigns from account >> 123-456-7890? >> >> *Why This Matters:* We want to provide the best user experience >> possible. If Basic Access requires MCC linking, we need to build an MCC >> invitation flow. If Standard Access removes this requirement, we should >> apply for Standard Access to enable direct account connection. >> >> *Request:* Could you please provide definitive technical documentation >> or confirmation about these access level differences? We want to ensure >> we're building our application architecture correctly from the start. >> >> Thank you for your time and assistance. >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/adwords-api/33d95cdd-9bc5-4527-ba49-8efedc785a25n%40googlegroups.com.
