Google Ads Performance Manager Agent Template

• What it does: Audits live Google Ads performance, checks search demand, and turns evidence into approval-controlled optimization actions.
• Best for: PPC teams, agencies, small businesses, B2B marketers, and ecommerce advertisers.
• Apps used: Google Ads, DataForSEO, web_search.
• Setup time: 10 to 15 minutes after connecting Google Ads and DataForSEO.

Last verified from workflow config on 2026-08-20. Includes exact connector scopes, common failure modes, and fixes.

The Google Ads Performance Manager audits campaign evidence and search demand before recommending or applying approved improvements. This template acts as a starting point: open any agent and use Use AI to help draft or update its instructions—adding new agents or connecting new tools is done manually in the canvas.

The problem this template solves

• Campaign decisions get made: from isolated metrics without search-market context.
• Wasted spend, weak landing: pages, and keyword gaps compete for attention without a ranked action plan.
• Broad account changes create: risk when the exact mutation and rollback are not reviewed first.

How do you build a Google Ads optimization agent yourself?

A reliable Google Ads optimization agent needs account reporting, keyword and SERP research, KPI normalization, an evidence ledger, an approval gate, and verified mutation receipts. The method must keep source evidence, calculations, recommendations, and external actions distinct so a user can review what happened.

You can build this with Claude Code, Codex, or a custom stack. You would own authentication, schemas, retries, storage, approval state, testing, and ongoing connector maintenance. This template starts with those workflow decisions already represented in an editable Agent Build.

If the adjacent job is a better fit, the Meta Ads Performance Manager template provides a related starting point without forcing this agent beyond its actual scope.

Setup guide

Step 1: Clone the template into the right Project

Open the template gallery from Agent Space, choose Google Ads Performance Manager, and clone it into the Project that holds the relevant customer context. The workflow opens as an editable draft with its agents, notes, tools, and installed skills.

Step 2: Review Project context and complete first-run setup

Open Run and start a new conversation with Google Ads Performance Manager. The agent checks read-only Project files and its reusable setup record before asking only for unresolved choices from the installed Optimize Google Ads from Performance Evidence method.

Step 3: Connect only the apps this workflow needs

Open Agent Build, inspect each tool node, and connect the required accounts for Google Ads, DataForSEO, web_search. Review the allowlisted actions shown in the Apps used table below, and avoid granting broader write access than the template needs.

Step 4: Confirm goals, limits, and approval policy

Review the saved setup fields, reporting window, output preferences, cost limits, and any external-write policy. Keep analysis and draft work available by default, and require explicit approval for any live side effect described in the workflow guardrails.

Step 5: Test a normal prompt and an edge case

Run Audit the last 30 days against the previous 30 and prioritize ways to reduce CPA. Then open a clean conversation and test Recommend negative keywords, but do not change the account. Inspect tool calls, files, human-input pauses, and the final answer in the trace before changing instructions.

Step 6: Publish the tested draft

Return to Build, save the final configuration, then publish it from Deploy after the draft test behaves as expected. Use Playground for ongoing work and Agent Space to watch live status or requests that need human input.

Common issues and fixes

• A required connector is disconnected: Open Tools and Skills, connect the account in the same Project, and confirm the intended actions remain allowlisted.
• Project context is incomplete: Add or update the relevant brand, goal, policy, glossary, or source file at Project scope, then ask the agent to refresh setup instead of guessing.
• The requested action is unsupported: Keep the local analysis or draft, state the connector gap, and do not claim a live write without a returned identifier.
• The result uses the wrong window or target: Confirm the saved setup, source period, locale, identity, and output goal before rerunning a cost-bearing or external step.

Customization knobs

• customer/account and reporting timezone: Review and update this value through the first-run setup flow when the Project changes.
• primary conversion and value definition: Review and update this value through the first-run setup flow when the Project changes.
• target geography and language: Review and update this value through the first-run setup flow when the Project changes.
• budget and bid constraints: Review and update this value through the first-run setup flow when the Project changes.
• target CPA, ROAS, CPC, or volume goal: Review and update this value through the first-run setup flow when the Project changes.
• brand/legal exclusions: Review and update this value through the first-run setup flow when the Project changes.

Who this template is for

• PPC agencies: Ranked from google ads agency (2900 US searches/month in the evaluated dataset). The workflow fits because it can turn campaign and search-market evidence into prioritized Google Ads improvements tied to the user's conversion, revenue, efficiency, or growth goal.
• Small businesses: Ranked from google ads for small business (1900 US searches/month in the evaluated dataset). The workflow fits because it can turn campaign and search-market evidence into prioritized Google Ads improvements tied to the user's conversion, revenue, efficiency, or growth goal.
• B2B marketing teams: Ranked from google ads for b2b (140 US searches/month in the evaluated dataset). The workflow fits because it can turn campaign and search-market evidence into prioritized Google Ads improvements tied to the user's conversion, revenue, efficiency, or growth goal.
• Ecommerce advertisers: Ranked from ecommerce google ads (40 US searches/month in the evaluated dataset). The workflow fits because it can turn campaign and search-market evidence into prioritized Google Ads improvements tied to the user's conversion, revenue, efficiency, or growth goal.

What the agent does

This template can:

• Load setup and define: the date window, comparison window, business goal, and decision thresholds.
• Use Google Ads reporting/GAQL: to inventory campaigns, ad groups, ads, search terms, conversions, costs, and available quality signals.
• Validate keyword demand, intent: competition, SERPs, and competitor gaps with DataForSEO.
• Calculate comparable KPIs and: distinguish tracking problems from media-performance problems.
• Produce a ranked action: register covering waste, negatives, new themes, bids, budgets, structure, landing pages, and experiments.
• Show evidence, expected effect: confidence, risk, and rollback for each recommendation.
• Request explicit approval for: a precise mutation set; apply only connector-supported actions and verify returned results.
• Save the audit, action: register, approval record, and post-change monitoring plan.

How the workflow works

1. Load setup and define the date window, comparison window, business goal, and decision thresholds.
2. Use Google Ads reporting/GAQL to inventory campaigns, ad groups, ads, search terms, conversions, costs, and available quality signals.
3. Validate keyword demand, intent, competition, SERPs, and competitor gaps with DataForSEO.
4. Calculate comparable KPIs and distinguish tracking problems from media-performance problems.
5. Produce a ranked action register covering waste, negatives, new themes, bids, budgets, structure, landing pages, and experiments.
6. Show evidence, expected effect, confidence, risk, and rollback for each recommendation.
7. Save the evidence, approvals, files, and final result for review.

This is a single-agent workflow. The main agent owns research, planning, tool use, approvals, files, and the final response without passing routine stages between specialists.

Requirements and setup inputs

Use the template in a Project that contains the relevant business context. Connect only the accounts required for Google Ads, DataForSEO, web_search. The agent reads Project files before asking questions and stores confirmed reusable setup at agent scope.

• customer/account and reporting timezone: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• primary conversion and value definition: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• target geography and language: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• budget and bid constraints: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• target CPA, ROAS, CPC, or volume goal: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• brand/legal exclusions: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.
• mutation approval policy and reporting cadence: Confirm this only when it is not already available from Project context, public evidence, or a saved setup record.

No template-wide sample-data artifact is installed. The template installs its reusable methods and setup.md through skills, then creates customer-specific profiles, reports, charts, exports, and receipts from authorized evidence. Generated files can be inspected in Playground.

Apps and tools used

Connector actions are scoped to this Agent Build. A Project connection does not automatically grant every agent or every action access.

Practical use cases

First setup and baseline

PPC agencies can use the template to turn campaign and search-market evidence into prioritized Google Ads improvements tied to the user's conversion, revenue, efficiency, or growth goal. The saved setup and evidence files reduce repeated onboarding while keeping unknowns visible.

Best for: ppc agencies.

Focused analysis or production run

Small businesses can use the template to turn campaign and search-market evidence into prioritized Google Ads improvements tied to the user's conversion, revenue, efficiency, or growth goal. The saved setup and evidence files reduce repeated onboarding while keeping unknowns visible.

Best for: small businesses.

Ongoing review and iteration

B2B marketing teams can use the template to turn campaign and search-market evidence into prioritized Google Ads improvements tied to the user's conversion, revenue, efficiency, or growth goal. The saved setup and evidence files reduce repeated onboarding while keeping unknowns visible.

Best for: b2b marketing teams.

Safe edge-case handling

Ecommerce advertisers can use the template to turn campaign and search-market evidence into prioritized Google Ads improvements tied to the user's conversion, revenue, efficiency, or growth goal. The saved setup and evidence files reduce repeated onboarding while keeping unknowns visible.

Best for: ecommerce advertisers.

Example prompts and outputs

Example prompt: core workflow

Audit the last 30 days against the previous 30 and prioritize ways to reduce CPA.

Example output: A ranked action register with observed metrics, expected effect, confidence, risk, and approval status. The actual numbers, sources, files, and connector receipts depend on the user's authorized data.

Example prompt: safety or limitation check

Recommend negative keywords, but do not change the account.

Expected behavior: the agent follows this boundary, preserves useful local work, and does not claim an unsupported or unapproved external action.

Why use this template

• Research happens before questions: the agent inspects Project context, saved setup, and available evidence before requesting unresolved choices.
• The method stays maintainable: detailed repeatable steps live in human-readable skills instead of one oversized agent prompt.
• External actions stay reviewable: connector scopes, approval boundaries, and returned identifiers are explicit.
• Files carry the detail: reports, evidence, drafts, charts, and receipts remain inspectable instead of being lost in a long chat response.
• The workflow remains editable: teams can refine one agent, skill, tool scope, or handoff at a time and retest it.

Related templates

• Meta Ads Performance Manager: Diagnoses campaign, audience, placement, and creative performance and proposes measurable Meta Ads improvements.
• Microsoft Ads Performance Manager: Audits Microsoft Advertising exports with search evidence and prepares a prioritized, connector-ready optimization plan.
• Product Analytics and Reporting Analyst: Answers product and website questions with reproducible GA4 and Microsoft Clarity analysis, charts, caveats, and next experiments.
• SEO Optimized Blog Writer: Creates original, source-backed B2B articles through a ten-stage research, writing, editing, SEO, and delivery method.