Publishing issue

55 views
Skip to first unread message

ais...@brendon.hu

unread,
May 31, 2024, 9:37:10 AM5/31/24
to Google Ads API and AdWords API Forum
Hi!

I developed an offline console application, using c#, which will responsible to send offline conversation data to Google Ads API, daily.
As I noticed, the refresh token expires after 7 days, so I want to switch "Publishing status" to published.
When I clicked the "Publish app" button I get a notification "You've configured your app in a way that requires verification".
I don't understand it, because my app is an internal tool, no one will use it, will be scheduled for daily run.

As the popup say:
  • An official link to your app's Privacy Policy
    But this tool don't have/don't need one
  • A YouTube video showing how you plan to use the Google user data you get from scopes
    My tool will not use any google user data, just send data to google ads api
  • A written explanation telling Google why you need access to sensitive and/or restricted user data
    We don't use any sensitive data, we only need OAuth cred for authorize the api calls
  • All your domains verified in Google Search Console
    The company has web site, but this too is not used there.
Can someone help me how to configure my app/OAuth consent/anything to skip the verification?

Thanks,
István Antal

Google Ads API Forum Advisor

unread,
May 31, 2024, 2:37:39 PM5/31/24
to ais...@brendon.hu, adwor...@googlegroups.com
Hi,

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

I understand that your concern is related to the OAuth consent screen. I would recommend you kindly refer to the “Google OAuth verification” documentation for more information. Also, I would suggest you refer to the 'OAuth API verification FAQs' and 'Unverified apps' articles which answer your queries. Since you're utilizing a web app flow, you need to authenticate as a user who can grant permission to your app to access their Google Ads account data. You may refer to this “Select an app type” guide for additional information.

If you still encounter any issues related to the OAuth, I would recommend you kindly reach out to the GCP Product support team as they are better equipped to address your concerns.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ9Un:ref" (ADR-00237355)

Thanks,
Google Logo Google Ads API Team


Reply all
Reply to author
Forward
0 new messages