Hi, Thanks for your detailed reply.
I want to clarify my intent: I don’t want to create real campaigns in production accounts — my goal is to test the full workflow (budget, Performance Max campaign, asset groups, conversion actions) **only inside test accounts** (the ones with the red "Test Account" banner). The difficulty I’m facing is that: - My developer token (account@...) is in “Test Access” mode, but it does not show the red “Test Account” banner. - My test MCC (ratoblaas6...) has the red banner, but the API Center is disabled there, so I cannot get a developer token directly from that account. - If I try to use the dev token from `account@...` against the red-flag MCC or its clients, I get `USER_PERMISSION_DENIED`. Questions: 1. How do I correctly set up the linkage between a production MCC (with the developer token in Test Access) and a test MCC (with the red banner) so I can use the dev token against the test accounts? Do I need to explicitly invite `account@...` as an admin in the red-flag MCC? 2. Is `OPERATION_NOT_PERMITTED_FOR_CONTEXT` expected if I mistakenly try to create campaigns on a real account using only a Test Access token? 3. Could you confirm that **the only supported way to create Performance Max campaigns in sandbox** is: - Use developer token from a production MCC (Test Access level) - But always target customer IDs that belong to a test MCC (red flag) This would really help me clarify the right structure between the token account and the test MCCs. Right now it’s not clear how to bridge the gap between “token comes from production” and “operations only allowed in test accounts”. Em quinta-feira, 7 de agosto de 2025 às 01:52:24 UTC-3, Google Ads API Forum Advisor escreveu: > Hi, > > Thank you for contacting the Google Ads API support team. > > Please find answers to your queries below: > > 1. Is this error caused by using a **test-mode Developer Token** with a > **real user account**? > > Answer: The *OPERATION_NOT_PERMITTED_FOR_CONTEXT* > <https://developers.google.com/google-ads/api/reference/rpc/v17/ContextErrorEnum.ContextError#operation_not_permitted_for_context> > > error indicates that the operation is not allowed for the given context. > Using a developer token with test access level for a production account > should result in *DEVELOPER_TOKEN_NOT_APPROVED* > <https://developers.google.com/google-ads/api/docs/common-errors#:~:text=DEVELOPER_TOKEN_NOT,N/A> > > error. But, as per the error you have encountered, it seems to be more > related to the operation you are performing. > > In order to verify that the operation you are performing is a valid > operation or not, we will need to check the complete API logs (request > <https://developers.google.com/google-ads/api/docs/concepts/field-service#request> > > and response > <https://developers.google.com/google-ads/api/docs/concepts/field-service#response> > > with request-id > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id> > > and request header > <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers>) > > generated at your end without redacting any information. If you are not > able to provide the complete API logs, try to at least provide a request ID > for it. 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 > <https://developers.google.com/google-ads/api/docs/client-libs/java/logging>, > .Net > <https://developers.google.com/google-ads/api/docs/client-libs/dotnet/logging>, > > PHP > <https://developers.google.com/google-ads/api/docs/client-libs/php/logging>, > Python > <https://developers.google.com/google-ads/api/docs/client-libs/python/logging>, > > Ruby > <https://developers.google.com/google-ads/api/docs/client-libs/ruby/logging> > or Perl > <https://developers.google.com/google-ads/api/docs/client-libs/perl/logging> > to enable logging at your end. For REST interface requests, you can enable > logging via the curl command by using the -i flag. > > 2. Do I **need a production-approved Developer Token** to create > Performance Max campaigns on real user accounts via OAuth? > > Answer: Yes, your understanding is correct. In order to make API calls to > the production accounts, you will need a developer token with either ‘Basic > Access’ or ‘Standard Access’. The access level controls the number of API > calls you can make per day with the token, as well as the environment to > which you can make calls. Please refer to this *document* > <https://developers.google.com/google-ads/api/docs/access-levels#access_levels_2> > > for more information and to understand how to apply for each access level > and their *permissible use* > <https://developers.google.com/google-ads/api/docs/access-levels#permissible_use>. > > In addition to it, you may refer to the *Obtain a developer token* > <https://developers.google.com/google-ads/api/docs/get-started/dev-token> > document for more information. > > 3. Can I only use the test token with **test accounts** (those with the > red "test account" banner)? > > Answer: Yes, your understanding is correct. As per the *Access Levels* > <https://developers.google.com/google-ads/api/docs/access-levels#access-levels> > > section, a developer token with access level as ‘Test account access’ can > only access test accounts. > > 4. Does the real user account require specific permissions or settings to > allow campaign creation? > > Answer: For campaign creation in a production account using Google Ads > API, you just need to follow the *prerequisites* > <https://developers.google.com/google-ads/api/docs/get-started/introduction#prerequisites> > > for using Google Ads API, have a developer token with appropriate access > level and should follow the *CampaignOperation* > <https://developers.google.com/google-ads/api/reference/rpc/v21/CampaignOperation> > > document in order to know the required fields for campaign creation. > > 5. Is there any workaround to test the full campaign creation flow > (including asset groups and conversion actions) without production token > access? > > Answer: If you are aiming to manage conversion actions and asset groups in > your production account, you need to have a developer token with either > Basic or Standard access. > > I understand that you are using version v18 of Google Ads API. Please note > that the 'v18' is deprecated and is about to sunset in August, 2025. After > this date, all v18 API requests will begin to fail. I would suggest you > *upgrade > to the latest version* > <https://developers.google.com/google-ads/api/docs/upgrade>, *'v21* > <https://developers.google.com/google-ads/api/docs/release-notes#v21_2025-08-06>', > > as soon as possible to benefit from new features. You may refer to this > *documentation* > <https://developers.google.com/google-ads/api/docs/sunset-dates> on > deprecation and sunset for more information regarding the specific > deprecation and sunset dates for each available version. > > Also, I understand that you are using NodeJS client library for using > Google Ads API. Please be informed that as per this *documentation* > <https://developers.google.com/google-ads/api/docs/client-libs#community_libraries>, > > we don't test, contribute to or maintain these libraries. You may use them > at your own risk. Any questions you may have should be directed to the > owners of the open source projects. > > *You can send the details via Reply privately to the author option, or > direct private reply to this email.* > Thanks, > > [image: Google Logo] Google Ads API Team > Feedback > How was our support today? > > [image: rating1] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=1&entry.295079254=500Ht00001syNeXIAU> > > [image: rating2] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=2&entry.295079254=500Ht00001syNeXIAU> > > [image: rating3] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=3&entry.295079254=500Ht00001syNeXIAU> > > [image: rating4] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=4&entry.295079254=500Ht00001syNeXIAU> > > [image: rating5] > <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=5&entry.295079254=500Ht00001syNeXIAU> > [2025-08-07 04:51:46Z GMT] This message is in relation to case > "ref:!00D1U01174p.!500Ht01syNeX:ref" (ADR-00329029) > > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/9c90ea6c-aca3-4dfb-addd-6f0ba8fcc02bn%40googlegroups.com.
