Quri

Google Ads

Last updated 2026-06-14

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. Google Ads does not yet have a self-serve button on /app/connect — there is no in-app OAuth tile for it today, so this is an operator-assisted connection rather than a one-click grant.
  2. Reach out so a Quri operator can attach your Google Ads account to your workspace using the credentials below.
  3. Once attached, the connection behaves like the other ad sources: encrypted, workspace-scoped credentials, an automatic refresh, and campaign metrics that show up after the first sync.

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

Why is there no Google Ads button next to Meta Ads on the connect page?
The Google Ads connector reads campaign insights, but it is not wired to a self-serve OAuth tile yet, so connecting it is an operator-assisted step rather than a one-click grant. This guide describes the real path instead of pointing you at a button that does not exist.
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