Google Ads Management Skill

Comprehensive skill for managing Google Ads accounts via the Google Ads API.

Why This Skill Exists

The Problem:
Google Ads management requires precise, methodical work. Missed settings cause wasted spend. Forgotten fields cause API rejections. Small mistakes compound into big losses.

The Solution:
This skill provides battle-tested checklists, query templates, and workflows for common Google Ads operations. It captures lessons learned from real production use — the gotchas that aren't in the official docs.

What it prevents:

• Campaign creation with broken landing pages ($$ wasted on 404s)
• RSA text rejections (character limits are strict)
• Missing required fields that cause API errors
• Pausing the wrong campaigns
• Forgetting to set end dates on promotional campaigns

When to Use This Skill

Setup Verification

The agent should verify API access before proceeding:

# Check for API configuration
ls ~/.google-ads.yaml 2>/dev/null && echo "API config found" || echo "No API config — see references/api-setup.md"

# Check for SDK
python3 -c "from google.ads.googleads.client import GoogleAdsClient; print('SDK installed')" 2>/dev/null || echo "SDK not installed — run: pip install google-ads"

If API is not configured, guide the user through references/api-setup.md. The API approach is strongly recommended — it's reliable, automatable, and doesn't depend on UI changes.

Campaign Creation Checklist

⚠️ COMPLETE THIS BEFORE CREATING ANY CAMPAIGN

This checklist exists because every item has caused real-world failures:

1. Pre-Flight Verification

# ALWAYS verify landing page is live
curl -sI "https://your-landing-page.com/path" | head -2
# Must return: HTTP/2 200 or HTTP/1.1 200 OK

# Why? We've seen campaigns launch with 404 landing pages. 
# All ad spend went to a broken page. Verify FIRST.

2. Plan Structure Before Code

Before writing any campaign creation code, document:

Why plan first? Iterating campaign structure via API is slow and error-prone. Get it right on paper first.

3. Required API Fields (Easy to Forget)

# EU Political Advertising field (REQUIRED even for non-political ads)
campaign.contains_eu_political_advertising = (
    client.enums.EuPoliticalAdvertisingStatusEnum.DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING
)
# Why? Without this, the API rejects the campaign with a confusing error.

# RSA character limits (STRICT)
# Headlines: exactly ≤30 characters (not "about 30")
# Descriptions: exactly ≤90 characters (not "about 90")
# Why? The API rejects over-length text, doesn't truncate it.

4. Post-Creation Verification

• Campaign status shows ENABLED (not PAUSED or ERROR)
• Ads show "Eligible" or "Under review" (not "Disapproved")
• Conversion tracking is connected
• Location targeting is correct
• Budget is what you intended
• End date set (if time-limited)

Account Audit Checklist

Quick health check for any Google Ads account:

Common Queries (API Mode)

Campaign Performance (Last 30 Days)

query = """
    SELECT 
        campaign.id,
        campaign.name,
        campaign.status,
        campaign_budget.amount_micros,
        metrics.cost_micros,
        metrics.conversions,
        metrics.cost_per_conversion
    FROM campaign
    WHERE segments.date DURING LAST_30_DAYS
      AND campaign.status != 'REMOVED'
    ORDER BY metrics.cost_micros DESC
    LIMIT 50
"""

# Parse results
for row in response:
    cost = row.metrics.cost_micros / 1_000_000
    conv = row.metrics.conversions
    cpa = row.metrics.cost_per_conversion / 1_000_000 if conv > 0 else 0
    print(f"{row.campaign.name}: ${cost:.2f} | {conv:.1f} conv | ${cpa:.2f} CPA")

Find Wasted Spend (Zero-Conversion Keywords)

query = """
    SELECT 
        ad_group_criterion.keyword.text,
        ad_group_criterion.keyword.match_type,
        campaign.name,
        metrics.cost_micros,
        metrics.clicks,
        metrics.impressions
    FROM keyword_view
    WHERE metrics.conversions = 0
      AND metrics.cost_micros > 500000000  /* $500 in micros */
      AND segments.date DURING LAST_90_DAYS
      AND ad_group_criterion.status = 'ENABLED'
    ORDER BY metrics.cost_micros DESC
    LIMIT 100
"""

# Why 90 days? Short windows miss slow converters.
# Why $500 threshold? Adjust based on your CPA expectations.

Search Terms Report (Find Bad Matches)

query = """
    SELECT 
        search_term_view.search_term,
        campaign.name,
        metrics.cost_micros,
        metrics.conversions,
        metrics.clicks
    FROM search_term_view
    WHERE segments.date DURING LAST_30_DAYS
    ORDER BY metrics.cost_micros DESC
    LIMIT 200
"""

# Look for irrelevant searches eating budget.
# Add them as negative keywords.

Common Mutations (API Mode)

Mutations change live ad spend. Before running any mutation (pause, budget change, status flip, negative keyword), show the user the exact campaigns or keywords and the change you're about to make, and get explicit approval. Run a read query first to confirm you're targeting the right resources.

Pause Campaigns

from google.ads.googleads.client import GoogleAdsClient
from google.api_core import protobuf_helpers

def pause_campaigns(client, customer_id, campaign_ids):
    """Pause one or more campaigns."""
    campaign_service = client.get_service("CampaignService")
    operations = []

    for campaign_id in campaign_ids:
        operation = client.get_type("CampaignOperation")
        campaign = operation.update
        campaign.resource_name = campaign_service.campaign_path(
            customer_id, campaign_id
        )
        campaign.status = client.enums.CampaignStatusEnum.PAUSED

        # Set field mask so the API only updates the fields we changed
        client.copy_from(
            operation.update_mask,
            protobuf_helpers.field_mask(None, campaign._pb)
        )
        operations.append(operation)

    response = campaign_service.mutate_campaigns(
        customer_id=customer_id,
        operations=operations
    )
    return response

Pause Keywords

from google.api_core import protobuf_helpers

def pause_keywords(client, customer_id, keyword_resource_names):
    """Pause specific keywords by resource name."""
    service = client.get_service("AdGroupCriterionService")
    operations = []

    for resource_name in keyword_resource_names:
        operation = client.get_type("AdGroupCriterionOperation")
        criterion = operation.update
        criterion.resource_name = resource_name
        criterion.status = client.enums.AdGroupCriterionStatusEnum.PAUSED

        client.copy_from(
            operation.update_mask,
            protobuf_helpers.field_mask(None, criterion._pb)
        )
        operations.append(operation)

    return service.mutate_ad_group_criteria(
        customer_id=customer_id,
        operations=operations
    )

Browser Fallback (Not Recommended)

Stability Warning: Browser automation against ads.google.com is fragile. Google frequently changes their UI, which breaks selectors and workflows. Use the API whenever possible.

If the API is truly unavailable (no developer token, client account without API access), browser automation can work for read-only checks. See references/browser-workflows.md for details.

Limitations of browser mode:

• UI selectors break without warning when Google updates the interface
• Cannot be reliably scheduled or automated
• Requires the user to be logged in with an active session
• Slower and more error-prone than API calls
• Not suitable for mutations (pausing, budget changes) — too risky without confirmation loops

Recommended path: Invest the 1-2 hours to set up API access (see references/api-setup.md). It pays off immediately.

Output Format

When reporting findings, use clear tables:

## Campaign Performance (Last 30 Days)
| Campaign | Cost | Conv | CPA | Status |
|----------|------|------|-----|--------|
| Branded  | $5K  | 50   | $100| ✅ Strong |
| Generic  | $10K | 5    | $2K | ⚠️ Review |
| Test     | $2K  | 0    | N/A | ❌ Pause |

## Recommended Actions
1. **PAUSE**: Test campaign ($2K spent, 0 conversions)
2. **REVIEW**: Generic campaign (CPA too high)
3. **INCREASE**: Branded budget (efficient performer)

Troubleshooting

API Issues

Why This Belongs in Tier 4 (Growth)

This skill directly drives revenue growth:

• Tier 1 = Foundation (secrets, setup)
• Tier 2 = Communication (email, Slack)
• Tier 3 = Business Ops (POS, accounting)
• Tier 4 = Growth (advertising, marketing, SEO)

Google Ads is one of the primary paid growth channels for SMBs. This skill helps you manage it without the expensive mistakes that eat into margins.

Files Included

google-ads/
├── SKILL.md                    # This documentation
└── references/
    ├── api-setup.md            # Full API setup guide (start here)
    └── browser-workflows.md    # Browser fallback (unstable, last resort)