I believe I may have used the wrong verbiage / terms, and I apologize for any confusion that I may have caused in so doing.
It was my intention to inquire about moving from a "*Test*" *publishing status* to "*Production*" *publishing status*, as described at https://support.google.com/cloud/answer/10311615#publishing-status&zippy= Given that, may you please verify that the same three questions you answered for me still are what you have replied? I just want to ensure we are taking the correct next step. So essentially, what I meant to ask was: 1) Will we lose our current access while awaiting approval for Production access? 2) If we do lose access, may you please advise the maximum time historically users have lost it, so that we might anticipate the ramification? 3) Lastly, once we click the *[PUBLISH APP]* button shown on our OAuth consent screen, do we need to again complete the form we had previously submitted? 3b) if so, will it still suffice to simply submit that it is a console application using both the *.net client library* and direct *REST calls *via search & search stream, or would we be required to have more granular details than that? Thank you for your patience and assistance. On Tuesday, January 16, 2024 at 3:55:35 PM UTC-5 Google Ads API Forum Advisor wrote: Hi, Thank you for reaching out to the Google Ads API support team. Please find below responses for your queries: 1. Will we lose Development access while awaiting approval for Production access? No, you won't lose access to Development mode while awaiting Production approval. Kindly, refer to the document to obtain a developer token <https://developers.google.com/google-ads/api/docs/get-started/dev-token#:~:text=Send%20feedback-,Obtain%20a%20developer%20token,-bookmark_border> for more information. 2. What is a rough expectation of time for approval? Approval times for Production access can vary depending on the complexity of your request and existing Google Ads usage. Kindly, refer to the document to access levels and permissible use <https://developers.google.com/google-ads/api/docs/access-levels#:~:text=Access%20Levels%20and%20Permissible%20Use> for more information. 3. Since a .net console application is what we have been using (and intend to continue using) we are wondering how best to describe the application. Would it suffice to describe it as a console application using both the .net client library and direct REST calls via search stream, or would we be required to have more granular details than that? Yes, it's sufficient to describe it as a console application using both the .net client library and direct REST calls via search stream. Kindly, refer to the document on how to get started with the Google Ads API .NET library <https://developers.google.com/google-ads/api/docs/client-libs/dotnet/getting-started> for more information. I hope this helps. Kindly get back to us if you have any further queries. This message is in relation to case "ref:!00D1U01174p.!5004Q02rWv4V:ref" Thanks, [image: Google Logo] Google Ads API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 on the web visit https://groups.google.com/d/msgid/adwords-api/1d1fa63c-4cca-41a5-8ee7-01afd171a8d7n%40googlegroups.com.
