What It Solves

AdLoop exists because managing Google Ads alongside your code is a mess. These are the specific problems it handles:

• "My conversions dropped and I don't know why." AdLoop cross-references Ads clicks, GA4 sessions, and conversion events in one query. It detects whether the gap is from GDPR consent rejection, broken tracking, or an actual landing page problem — before you waste hours checking each dashboard separately.

• "I'm wasting ad spend on irrelevant searches." Pull your search terms report, identify the junk, and add negative keywords — all from a single conversation in your IDE. No context-switching to the Ads UI.

• "Is my tracking even working?" Compare the event names in your actual codebase against what GA4 is receiving. Find the mismatches: events you fire that GA4 never sees, events GA4 records that you didn't know about.

• "I need to create ads but the Google Ads UI is hostile." Draft responsive search ads, create campaigns, add keywords — all through natural language. Every change shows a preview first. Nothing goes live without your explicit confirmation. New ads and campaigns start paused.

• "My landing page gets paid traffic but nobody converts." AdLoop joins your ad final URLs with GA4 page-level data. See which pages get clicks but no conversions, which have high bounce rates, and which ones are orphaned from any ad campaign.

• "I don't know if my EU consent setup is causing data gaps." In Europe, 30-70% of users reject analytics cookies. AdLoop accounts for this automatically — it won't diagnose a normal GDPR consent gap as broken tracking.

Built From Real Usage

Every tool exists because of an actual problem hit while running real Google Ads campaigns. The cross-reference tools exist because we kept manually asking the AI to "get Ads data, then get GA4 data, then compare them" — so we automated the join. The Broad Match + Manual CPC safety rule exists because the AI once created that exact combination and wasted budget. The GDPR consent awareness exists because the AI kept diagnosing normal EU cookie rejection as broken tracking.

The best features come from real workflows. If you're using AdLoop and find yourself wishing it could do something it can't, open an issue describing your situation — not just "add feature X" but "I was trying to do Y and couldn't because Z." The context matters more than the request.

All 43 Tools

Quick start: pip install adloop or git clone https://github.com/kLOsk/adloop.git && cd adloop && uv sync && uv run adloop init

Diagnostics

GA4 Read Tools

Google Ads Read Tools

Cross-Reference Tools (GA4 + Ads Combined)

These tools call both APIs internally and return unified results with auto-generated insights. They're the core of what makes AdLoop different from having separate GA4 and Ads tools.

Tracking Tools

Planning Tools

Google Ads Write Tools

All write operations follow a draft → preview → confirm workflow. Nothing executes without explicit approval.

Orchestration Rules

AdLoop ships with orchestration rules that teach the AI how to combine these tools — marketing workflows, GAQL syntax, safety protocols, GDPR awareness, and best practices. Without rules, the AI has tools but doesn't know the playbook.

• Cursor: .cursor/rules/adloop.mdc (canonical source)
• Claude Code: .claude/rules/adloop.md (synced from Cursor rules via scripts/sync-rules.py)

The rules include:

• Orchestration patterns for common workflows (performance review, conversion diagnosis, campaign creation, negative keyword hygiene, keyword discovery, tracking validation, budget planning, landing page analysis)
• GAQL quick reference with syntax, common queries, and gotchas
• Safety rules including Broad Match + Manual CPC prevention and pre-write validation
• Ad copy character limit guidance (30-char headlines are shorter than you think)
• GDPR consent awareness to prevent false tracking diagnoses in EU markets

Slash Commands (Claude Code)

AdLoop includes pre-built slash commands in .claude/commands/ for common workflows:

Safety Model

AdLoop manages real ad spend, so safety is not optional.

• Two-step writes. Every mutation returns a preview first. A separate confirm_and_apply call is required to execute.
• Dry-run by default. Even confirm_and_apply defaults to dry_run=true. Real changes require explicit dry_run=false.
• Budget caps. Configurable maximum daily budget — the server rejects anything above the cap.
• Audit log. Every operation (including dry runs) is logged to ~/.adloop/audit.log.
• New campaigns and ads are PAUSED. Nothing goes live without manual enablement.
• Destructive ops require double confirmation. Removing entities or large budget increases trigger extra warnings.
• Broad Match + Manual CPC blocked. The #1 cause of wasted ad spend is automatically prevented — draft_keywords refuses to add BROAD match keywords to campaigns without Smart Bidding.
• Pre-write validation. Before any write, the AI checks bidding strategy, conversion tracking status, and quality scores. If the campaign is fundamentally broken, AdLoop warns you instead of making things worse.
• Structured error handling. All tools return actionable error messages with hints instead of raw exceptions. Auth errors include specific re-authorization steps.
• API version pinning. The Google Ads API version is pinned to prevent silent breaking changes from library updates. health_check warns when a newer version is available.
• Ask mode compatibility. Read tools declare readOnlyHint so they work in Cursor's Ask mode without switching to Agent mode.

Setup

Quick Start (Recommended)

Option A — Install from PyPI:

pip install adloop
adloop init

Option B — Install from source:

git clone https://github.com/kLOsk/adloop.git
cd adloop
uv sync
uv run adloop init

The adloop init wizard walks you through everything. AdLoop ships with built-in Google OAuth credentials, so you don't need to create a Google Cloud project.

⚠️ Built-in credentials temporarily unavailable — Google verification pending. Google limits unverified OAuth apps to 100 users. AdLoop has reached that cap while awaiting Google's app verification. Until verification is complete, the built-in credentials will show a "This app is blocked" error for new users.

Workaround: set up your own Google Cloud project using the Advanced Setup instructions below (takes ~5 minutes). Your own project has no user cap and is the recommended setup path in the meantime.

The wizard:

1. Developer token — from your Google Ads MCC (API Center)
2. MCC Account ID — your Manager Account ID (top bar in the MCC UI)
3. OAuth sign-in — opens a browser to sign in with Google (or prints a URL for headless servers)
4. Auto-discovers your accounts — finds your GA4 properties and Ads accounts automatically
5. Safety defaults — budget cap and dry-run preference
6. Editor config snippets — prints MCP configuration for both Cursor and Claude Code

Requirements

• Python 3.11+
• A Google Ads account with an MCC (Manager Account)
• A Google Ads Developer Token (see below)

Google Ads Developer Token

A developer token is always required — even when using AdLoop's built-in OAuth credentials. The built-in credentials handle Google sign-in; the developer token is a separate key that grants API access to your Google Ads data.

1. Create an MCC (free) at ads.google.com/home/tools/manager-accounts if you don't have one. Link your regular Google Ads account to it.
2. In the MCC, go to Tools & Settings → API Center
3. Your developer token is shown there. Copy it — the wizard will ask for it.

Access levels — your token's access level determines what it can do:

Getting DEVELOPER_TOKEN_NOT_APPROVED? Your token is at "Test Account" level. Go to API Center in your MCC and check your access level. If it shows "Test Account", you need to apply for Basic access or wait for Explorer access to be granted after your first production API call.

Headless Servers

Running on a server without a browser (VMs, Docker, SSH)? The wizard automatically detects this and falls back to a manual flow: it prints an authorization URL you can open on any device, then you paste the redirect URL back into the terminal.

Advanced Setup (Custom Google Cloud Project)

{
  "mcpServers": {
    "adloop": {
      "command": "/absolute/path/to/adloop/.venv/bin/python",
      "args": ["-m", "adloop"]
    }
  }
}

claude mcp add --transport stdio adloop -- /absolute/path/to/adloop/.venv/bin/python -m adloop

{
  "mcpServers": {
    "adloop": {
      "command": "/absolute/path/to/adloop/.venv/bin/python",
      "args": ["-m", "adloop"]
    }
  }
}

adloop install-rules

Use It

Ask your AI assistant things like:

• "How are my Google Ads campaigns performing this month?"
• "Which search terms are wasting budget? Add them as negative keywords."
• "My sign-up conversions dropped — check GA4 and Ads to find out why."
• "Draft a new responsive search ad for my main campaign."
• "Which landing pages get paid traffic but don't convert?"
• "Is my tracking set up correctly? Compare my codebase events against GA4."
• "What keywords should I target for [product]? Find ideas and estimate the budget."
• "How much budget would I need for these keywords in Germany?"
• "Create a new search campaign for [product feature] with a €20/day budget."

Configuration Reference

All configuration lives in ~/.adloop/config.yaml. See config.yaml.example for a documented template.

Project Structure

src/adloop/
├── __init__.py        # Entry point — routes 'adloop init' to wizard, otherwise starts MCP server
├── server.py          # FastMCP server — 43 tool registrations with safety annotations
├── config.py          # Config loader (~/.adloop/config.yaml)
├── auth.py            # OAuth 2.0 flow (bundled + custom credentials, headless fallback) + service accounts
├── cli.py             # Interactive 'adloop init' setup wizard
├── crossref.py        # Cross-reference tools (GA4 + Ads combined analysis)
├── tracking.py        # Tracking validation + code generation tools
├── ga4/
│   ├── client.py      # GA4 Data + Admin API clients
│   ├── reports.py     # Account summaries, reports, realtime
│   └── tracking.py    # Event discovery
├── ads/
│   ├── client.py      # Google Ads API client (version-pinned) + retry/backoff for rate limits
│   ├── gaql.py        # GAQL query execution with human-readable error parsing
│   ├── read.py        # Campaign, ad, keyword, search term, negative keyword, shared sets, recommendations, audience reads
│   ├── pmax.py        # Performance Max tools — campaign/asset group performance, asset labels, top combinations
│   ├── write.py       # Draft campaign, RSA, keywords; pause, enable, remove, confirm
│   └── forecast.py    # Budget estimation + keyword discovery via Keyword Planner API
└── safety/
    ├── guards.py      # Budget caps, bid limits, blocked operations, Broad Match safety
    ├── preview.py     # Change plans and previews
    └── audit.py       # Mutation audit logging

Roadmap

What's been shipped and what's next:

• GA4 read tools ✓
• Google Ads read + write tools with safety layer ✓
• Cross-reference intelligence (campaign→conversion mapping, landing page analysis, attribution comparison) ✓
• Tracking utilities (validate events against GA4, generate gtag code) ✓
• Budget estimation + keyword discovery via Keyword Planner ✓
• Shared negative keyword lists (SharedSet API) ✓
• Retry/backoff for API rate limits ✓
• Setup wizard (adloop init) ✓
• Claude Code support ✓ — CLAUDE.md, .mcp.json, .claude/rules/, .claude/commands/, CLI wizard snippets
• Claude Desktop one-click install — adloop install claude-desktop (and/or a .dxt extension bundle) that writes the AdLoop MCP entry into claude_desktop_config.json automatically, so Claude Desktop + Cowork users don't have to hand-edit JSON
• PyPI package ✓ — pip install adloop
• Bundled OAuth credentials ✓ — no Google Cloud project required, auto-discovery of GA4/Ads accounts (currently capped at 100 users pending Google verification — use Advanced Setup in the meantime)
• Headless server support ✓ — manual URL copy-paste flow for servers without a browser
• Behavioral eval suites ✓ — 28 prompt-and-expectation tests covering read, write, tracking, and planning workflows
• Community launch — HN, Indie Hackers, r/cursor, Twitter
• Video walkthrough

Contributing

See CONTRIBUTING.md for guidelines. The short version: open an issue describing your situation first, then submit a PR if you want to build it.

License

MIT — see LICENSE.

Privacy

AdLoop runs entirely on your machine. No data is collected, stored, or transmitted to any server. See PRIVACY.md for the full privacy policy.