Google Ads
Connect Google Ads to ingest campaign keywords into your prompt list. MCC and direct accounts supported.
The Google Ads integration pulls keyword data from your campaigns into the prompt-ingestion flow. If you’ve spent on paid search, this is the most efficient way to translate that intent data into AI-monitored prompts.
What it unlocks
- Ingest keywords from one or more Google Ads customers (accounts).
- Filter by campaign, ad group, match type, and impression threshold.
- Works with both direct accounts and MCC (manager) accounts — pick which child customer to pull from.
The integration is read-only — we never modify your campaigns.
Prerequisites
- A Google account with at least Read-only access to the Google Ads account(s) you want to pull from.
- Access to your project’s Settings → Integrations page.
- If you’re authorizing via an MCC, the MCC must be linked to the customer accounts you want to access (the usual Google Ads pattern).
Connecting
- Open Settings → Integrations in the dashboard.
- Find Google Ads in the integration list and click Connect.
- You’ll be redirected to Google. The scope requested is
https://www.googleapis.com/auth/adwords— read access to your Ads accounts. - Approve and you’ll land back in the dashboard with the integration showing Connected.
Picking a customer
After connecting, Settings → Integrations → Google Ads → Pick customer lists every customer the authorizing account can see.
- Direct customer — pick it and you’re done.
- MCC account — pick the MCC; you’ll then see its child customers. Pick the child customer to pull from.
You can change the selected customer at any time. CiteFoundry only pulls from the currently selected one.
Pulling keywords
- Go to Prompts → Ingest → Google Ads.
- Optionally filter by campaign, ad group, match type, and minimum impressions.
- Pull kicks off an ingestion job.
- Review candidates, accept the relevant ones, and discard the rest.
Match-type keywords (“exact”, “phrase”, “broad”) are normalized to plain text. If you have both “running shoes” (exact) and “buy running shoes online” (broad), both show up as candidates.
Refresh, disconnect, expiry
- Tokens refresh automatically on each pull.
- Disconnect at any time from Settings → Integrations. The token is revoked immediately.
- Switching the selected customer doesn’t reauthorize — same token, different account.
Troubleshooting
- “No customers listed” — your authorizing account has access to none of the customers it’s been granted. In Google Ads, check Tools → Access and security for the account.
- “Quota exceeded” — your Google Ads API quota for the day is done. Try again tomorrow or contact us if it’s recurring; we have platform-level caps we can adjust.
- “Customer not active” — you’re trying to pull from a closed or canceled account. Pick another customer.
API
- POST
/v1/integrations/google-ads/authorize— returns a Google OAuth URL. - GET
/v1/integrations/google-ads/customers— list customers (and MCC children). - POST
/v1/projects/{projectId}/prompt-sources/google_ads/start— start an ingestion job. - DELETE
/v1/integrations/google-ads— disconnect.