Google Ads integration

Run a Google Ads strategist as an AI employee.

Connect Google Ads in one click and let an Oya AI employee monitor campaigns, surface anomalies, and propose changes. Approval gates keep destructive actions in your hands.

What it does

Campaign performance

Pull spend, CTR, CPA, and conversions across campaigns, ad groups, and keywords on demand or on a schedule.

Anomaly detection

Get a Slack DM or email when a keyword’s CPA spikes, a campaign blows budget, or conversions drop unexpectedly.

Proposed changes

The AI employee drafts bid adjustments, negative-keyword additions, and budget shifts — with a one-click approval before anything goes live.

How to connect Google Ads

  1. 1

    Open Channels & Apps on the AI employee

    Pick a paid-acquisition AI employee and click the Google Ads tile.

  2. 2

    Authorize via Google

    Sign in with the Google account that has access to your Ads MCC or sub-accounts. We request read + write scopes you control.

  3. 3

    Pick the accounts to monitor

    Multi-account agencies can scope which sub-accounts the AI employee operates against. One AI per account or one across all.

  4. 4

    Configure approval gates

    Decide which actions require human approval (e.g. any spend change > $X/day) versus what the AI can run autonomously (e.g. pause an ad whose CPA tripled).

Detailed walkthrough with screenshots: Channels & Apps in the docs.

What it doesn’t do (yet)

We’d rather be upfront about the edges than promise things we don’t deliver.

  • Display, Performance Max, and Demand Gen campaigns have fewer fine-grained controls than Search.
  • Bid-strategy changes still go through Google’s usual learning period.
  • Account-level permission changes are not supported — request access in Google Ads itself.

Frequently asked

Can the AI employee actually change bids and budgets?

Yes — but only with the permission you grant. Most teams start in approval-required mode where every change is reviewed; trust gradually expanded once you’re confident.

Does it work with MCC (manager) accounts?

Yes. Authorize at the MCC level and the AI employee can be scoped to specific sub-accounts.

How often does it pull data?

On-demand for one-off questions, or on a schedule (e.g. every morning) via Routines. You configure cadence per AI employee.

How do I disconnect?

Open Channels & Apps, find Google Ads, and click Disconnect. We immediately revoke our OAuth tokens.

How is the data handled?

Campaign data is processed for the active run and stored in your run history for audit. We do not use your account data to train any AI model.

A note on AI accuracy

Oya’s AI employees are powered by large language models and may produce inaccurate, incomplete, or out-of-date responses. They are tools to assist your work, not authoritative sources. Always verify important information — especially numbers, dates, names, and any business or financial action — before relying on AI-generated output. If your AI employee suggests a destructive action (deleting data, sending money, posting publicly), confirm it yourself before approving.

No model training

Your data is not used to train AI models. It’s used to do the work you asked for, then logged in your run history for your audit.

Full audit trail

Every AI employee action maps to a run in Oya. Inputs, outputs, tools used, cost — all visible and auditable.

Hire an AI paid-search strategist.

Free to connect. $10 in free credits. Approval gates protect every change.