Quri

Google Ads

Last updated 2026-06-21

What this unlocks

Connect Google Ads and Quri reads your campaign insights and creatives through the Google Ads API — so it can answer questions about search and shopping spend and flag when a campaign's cost or conversions move out of line.

Connect it in Quri

  1. Open /app/connect in Quri and find Google Ads under the data tools, then choose Connect with Google (OAuth).
  2. You are redirected to Google to authorize Quri — sign in with the account that manages your Google Ads and approve the read-only request.
  3. Google sends you back to Quri; the same grant powers both in-chat Google Ads questions and your ad reports.
  4. Click Choose ad account on the Google Ads tile and pick the account you want Quri to read — only the accounts your sign-in can reach are shown, so you do not type a customer id.
  5. Quri stores the grant as encrypted, workspace-scoped credentials and starts the first sync; your Google Ads spend and campaign metrics appear once it completes.

Get your credentials

  1. Sign in to your Google Ads manager (MCC) account and copy the developer token from API Center under Tools.
  2. A new developer token starts at Test Account access with Pending Approval — it works against test accounts immediately, but you must get it approved before it can read live production accounts.
  3. In the Google Cloud Console, create an OAuth 2.0 client (client ID and client secret) for the project that will call the Google Ads API.
  4. Run the OAuth consent flow once to mint a refresh token, then hand the developer token, client ID, client secret, refresh token, and the customer ID to the Quri operator setting up the connection.

Access Quri reads with

  • https://www.googleapis.com/auth/adwords — the single OAuth scope the Google Ads API uses for read access to campaigns and reporting.
  • A Google Ads API developer token is required in addition to the OAuth grant, and it must be approved (not left at Pending Approval) before it can read production accounts.
  • The token is read-oriented for Quri's reporting; the OAuth refresh token keeps the connection alive without re-authorizing.

Troubleshooting

I connected Google Ads but my ad reports are still empty.
The OAuth grant turns Google Ads on for chat first; your ad reports need one more step. Click Choose ad account on the Google Ads tile at /app/connect and pick which account Quri should read — that links the account to your reports.
My developer token shows Test Account Access with Pending Approval.
Google could not auto-approve the application, so it is queued for manual review. The token works against test manager accounts in the meantime; once approved it gains access to live production Google Ads accounts.
Authorization succeeded but the Google Ads API rejects my requests.
Check that the OAuth grant uses the adwords scope and that you are passing both the developer token and the correct customer ID. A grant without the developer token, or a token still pending approval, is the usual cause.

Related guides