Hi Sithara, Thanks for getting back to us.
If you set the publish status to In Production in order to generate refresh tokens that persist longer than 7 days. So that does indeed sound like the right setting for your use case. Note that we have examples of how you can generated refresh token with our Google Ads API client libraries here: https://developers.google.com/google-ads/api/docs/samples/generate-user-credentials If you leave the project unverified, you will see an unverified warning when you authenticate and your project will be subject to an OAuth user quota. But if this is an internal script that will not be authenticating many individual external users, that is normally sufficient for most developers. However, if your app is going to be used in any of the following scenarios, you do not need to submit it for review: Personal Use: The app is not shared with anyone else or will be used by fewer than 100 users (all of whom are known personally to you). Note that your app will be subject to the unverified app screen and the 100-user cap will be in effect. Development/Testing/Staging: If your app’s publishing status is set to “Testing” and not “In production”, then you do not need to submit your app for verification. Note that your app will be subject to the unverified app screen and the 100-user cap will be in effect. Learn more about Publishing status. Service-owned Data Only: The app only accesses its own data (using a Service Account), and not user data (linked to a Google Account). To understand what service accounts are, see Service accounts. For instructions on using a service account, see Using OAuth 2.0 for Server to Server Applications. Internal Use: The app is used only by people in your Google Workspace or Cloud Identity organization. Note that your app will not be subject to the unverified app screen or the 100-user cap if it's marked as Internal. Learn more about public and internal applications. Learn how to mark your app as internal in the FAQ How can I mark my app as internal-only? Domain-wide Installation: The app is used only by Google Workspace enterprise users. Access will depend on permission being granted by the domain administrator. Google Workspace domain administrators are the only ones that can add the app to an allowlist for use within their domains. To learn how to make your app a Domain-Wide Install, see My application has users with enterprise accounts from another Google Workspace Domain. SMTP/IMAP/WP: The app is used to send emails through WordPress, or similar single-account SMTP plugins. Let me know if you have any follow up questions, so that our team can assist you further. Regards, Yasar Google Ads API Team ref:_00D1U1174p._5004Q2h0KWQ:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/Yu2hp000000000000000000000000000000000000000000000RMMM0400wvTCRiZYT1KQNmyDXAnXHw%40sfdc.net.
