Google Ads

Working in dev?How we estimated thisTime to register an app and complete one sign-in with your own account. It covers console setup, not building your integration.Evidence: InferredEnabling the API grants Test access immediately (test accounts only); Explorer for production accounts is automated 'in most cases'. Creating test accounts and the OAuth client takes most of the time.

1–2 hours

Signing in with your own account

Any user can connect?How we estimated thisA multi-user agent that reads reports and manages campaigns at Basic access (15,000 ops/day), which needs brand verification plus Google OAuth app verification for the Google Ads scope; Standard access adds a manual audit of about 10 business days. Google Ads docs call the scope restricted; if it is reviewed as restricted, Google's FAQ estimate is 6 weeks instead. Includes waiting on: Google's OAuth app verification for the Google Ads scope (3–5 business days typical for sensitive scopes, often longer), then automated Basic approval; Standard needs a manual Google compliance review.. Provider review times vary, so this is a range, not a promise.Evidence: InferredAccess-level timings are sourced; whether the scope goes through sensitive or restricted verification is unclear, so the range is our estimate.

1–4 weeks

A multi-user agent that reads reports and manages campaigns at Basic access (15,000 ops/day), which needs brand verification plus Google OAuth app verification for the Google Ads scope; Standard access adds a manual audit of about 10 business days. Google Ads docs call the scope restricted; if it is reviewed as restricted, Google's FAQ estimate is 6 weeks instead.