NotFair

Connect Google Ads to your AI agent without building OAuth and API plumbing

NotFair turns Google Ads into a tool your AI client can safely use: live campaign reads, search-term review, recommendations, and approval-gated writes from one connection flow.

Works with Claude, Codex, Cursor, and MCP-compatible clients

Start with read-only diagnosis, then approve negatives, bids, budgets, and campaign edits

Keep every write tied to a user, account, and change record

Ready to connect your Google Ads account?

Start with the main product flow, then use your preferred AI client to inspect campaigns and review optimization ideas.

Connect Google Ads

Why this page exists instead of sending search users to login

People searching for a Google Ads connector need to understand the workflow before they authenticate. This page explains what NotFair connects, what the AI can do, and where approval gates protect the account.

The first useful action after connecting

The best first session is not a generic report. Ask your agent to inspect wasted spend, identify bad search terms, and prepare a small negative-keyword or budget recommendation you can approve.

What the connection enables

After OAuth, NotFair gives your AI client structured Google Ads tools instead of screenshots or CSV exports. That means the agent can query campaigns, keywords, search terms, conversion actions, budgets, and recent changes, then prepare safe edits through dedicated write tools.

Account and campaign performance reads
Search term and keyword diagnostics
Negative keyword, bid, budget, ad, and campaign-state writes
Change history and impact review for follow-up sessions

How approval-gated writes keep it safe

NotFair is designed for operator-led automation, not blind autopilot. The agent can do the tedious analysis and draft the change, but account mutations remain explicit, logged, and reviewable.

Read tools are separate from write tools
Risky actions use purpose-built mutation endpoints
Every write creates a change record for undo and review
Auth routes stay noindexed; public pages explain the product before login

Example workflows

Prompts that lead to real account work

Find wasted spend

“Review the last 30 days of campaigns, keywords, and search terms. Rank wasted-spend pockets by cost, conversions, CPA, and intent.”

A prioritized list of account leaks with evidence and proposed next actions.

Prepare negative keywords

“Group irrelevant search terms into phrase and exact negative keyword candidates, and explain the risk of blocking each group.”

A reviewable negative-keyword plan that can become the first approved write.

Check conversion setup

“List conversion actions, primary/secondary status, counting type, and any campaign goal mismatches that could distort bidding.”

A conversion-tracking sanity check before scaling spend or changing bidding.

FAQ

Short answers to the most common questions around this workflow.

Can I connect Google Ads directly to Claude or Codex?

NotFair provides the connection layer. You connect Google Ads to NotFair, then use NotFair's MCP-compatible tools from Claude, Codex, Cursor, or another supported AI client.

What can the AI do after I connect?

It can inspect live Google Ads data, diagnose account problems, recommend fixes, draft changes, and apply approved writes such as negatives, bids, budgets, ads, and campaign state changes.

Is this safe for a live Google Ads account?

NotFair separates reads from writes and keeps changes approval-gated and logged. It is built for AI-assisted execution, not unreviewed autopilot.

Use these pages to move from the exact search intent into the broader NotFair workflow.