Google Cloud OAuth verification — status update

[kLOsk]

We have applied for Google Cloud OAuth verification and are currently waiting for the review to complete.

What this means

When you first authorize AdLoop, Google shows a consent screen. Because AdLoop requests access to sensitive scopes (Google Ads and GA4 data), Google requires the app to go through their OAuth verification process. Until that is approved, the consent screen shows a "Google hasn't verified this app" warning and limits the app to 100 users.

What happens when verification completes

• The "unverified app" warning on the consent screen goes away
• The 100-user cap is lifted
• OAuth tokens stop expiring weekly (currently apps in "Testing" mode have tokens that expire every 7 days, requiring re-authorization)

What you need to do

Nothing right now. If you are already using AdLoop, everything continues to work. The only inconvenience is the unverified app warning during initial setup and the weekly token expiry.

If your token expires, delete ~/.adloop/token.json and run any AdLoop tool — it will trigger the OAuth flow again.

Timeline

Google's verification process typically takes 2-4 weeks but can vary. We will update this thread when the review is complete.

Feel free to ask questions below if you run into any auth-related issues in the meantime.

[kLOsk]

We are at 49 users / 100 user cap right now btw. I hope Google will let it pass first review.

[kLOsk]

Status update — 100-user cap reached, wizard now defaults to manual setup

We've crossed Google's 100-user cap on the unverified OAuth client. The verification request is still in review with Google.

What changed in v0.9.0 (just released):

• adloop init no longer defaults to the built-in OAuth credentials. The wizard now leads with the "bring your own Google Cloud project" path — same ~5-minute setup, no user cap, works immediately.
• The bundled option is still available as an opt-in for existing users whose tokens were issued before the cap. Picking it as a brand-new Google account will still hit "This app is blocked" at the consent screen — the wizard warns about this up front so nobody gets stranded.
• The README "Setup" section has been restructured to put the custom GCP path front and center, and the warning callout links back to this discussion.

TL;DR for current users:

• You already authorized AdLoop before the cap was reached: nothing changes. Your existing token keeps working until it expires (weekly under Testing mode). When it expires, re-running auth with the same Google account is generally allowed because you're already an authorized user.
• You're new and just installed AdLoop: run adloop init, take the default (custom GCP project) — the wizard guides you through it. Steps are also in the README under Custom Google Cloud Project Setup.
• You hit "This app is blocked": that's the consent screen rejecting a new sign-in. Switch to a custom Google Cloud project (see the wizard, or the README link above). No need to wait for verification.

When Google verification completes we'll flip the wizard default back to bundled, drop the warning, and update this thread. Until then, the manual path is the supported route for new installs.

[paquettej]

Any update on this?

[kLOsk]

I'm afraid not :( I guess they are overwhelmed by requests due to the rise of ai development. I'd suggest going the custom route for now https://github.com/kLOsk/adloop#custom-google-cloud-project-setup it's just a few clicks more.

[paquettej]

Thanks for the update, hopefully they will approve it soon. I tried to follow the instructions in the read + what is printed by uv adloop init, but I am getting permission denied:

Adloop has not completed the Google verification process. The app is currently being tested, and can only be accessed by developer-approved testers. If you think you should have access, contact the developer.