google-ads
Google Ads API for advertising campaign management. Use when user mentions "Google Ads", "AdWords", "ad campaigns", "GAQL", or Google advertising.
What this skill does
## Prerequisites
1. Connect Google Ads in Zero at Settings → Connectors → Google Ads.
2. Requests require both `GOOGLE_ADS_TOKEN` (OAuth access token) and `GOOGLE_ADS_DEVELOPER_TOKEN` (API developer token).
3. If using a manager (MCC) account, set `GOOGLE_ADS_LOGIN_CUSTOMER_ID` to the manager account ID.
4. All customer IDs should be in the format `1234567890` (no hyphens).
## Troubleshooting
If requests fail, run `zero doctor check-connector --env-name GOOGLE_ADS_TOKEN` or `zero doctor check-connector --url https://googleads.googleapis.com/v24/customers/1234567890/googleAds:search --method POST`
## Authentication
Every request requires these headers:
```
Authorization: Bearer $GOOGLE_ADS_TOKEN
developer-token: $GOOGLE_ADS_DEVELOPER_TOKEN
login-customer-id: <manager-account-id> (only when using MCC)
```
## GAQL Queries (Reporting)
Google Ads uses Google Ads Query Language (GAQL), a SQL-like syntax. All queries are POSTed to `googleAds:search` or `googleAds:searchStream`.
### Search (Paginated)
```bash
cat > /tmp/query.json << 'EOF'
{
"query": "SELECT campaign.id, campaign.name, campaign.status, metrics.impressions, metrics.clicks, metrics.cost_micros FROM campaign WHERE campaign.status = 'ENABLED' AND segments.date DURING LAST_30_DAYS ORDER BY metrics.cost_micros DESC LIMIT 100"
}
EOF
curl -s -X POST "https://googleads.googleapis.com/v24/customers/{customer-id}/googleAds:search" \
--header "Authorization: Bearer $GOOGLE_ADS_TOKEN" \
--header "developer-token: $GOOGLE_ADS_DEVELOPER_TOKEN" \
--header "login-customer-id: {manager-id}" \
--header "Content-Type: application/json" \
-d @/tmp/query.json
```
### SearchStream (Large Result Sets)
```bash
cat > /tmp/stream-query.json << 'EOF'
{
"query": "SELECT campaign.id, campaign.name, metrics.impressions, metrics.clicks, metrics.cost_micros FROM campaign WHERE segments.date DURING LAST_30_DAYS"
}
EOF
curl -s -X POST "https://googleads.googleapis.com/v24/customers/{customer-id}/googleAds:searchStream" \
--header "Authorization: Bearer $GOOGLE_ADS_TOKEN" \
--header "developer-token: $GOOGLE_ADS_DEVELOPER_TOKEN" \
--header "login-customer-id: {manager-id}" \
--header "Content-Type: application/json" \
-d @/tmp/stream-query.json
```
### Common GAQL Queries
**Ad group performance:**
```sql
SELECT ad_group.id, ad_group.name, ad_group.status, campaign.id, campaign.name, metrics.impressions, metrics.clicks, metrics.cost_micros, metrics.conversions FROM ad_group WHERE segments.date DURING LAST_30_DAYS
```
**Ad performance:**
```sql
SELECT ad_group_ad.ad.id, ad_group_ad.ad.name, ad_group_ad.ad.type, ad_group.id, campaign.id, metrics.impressions, metrics.clicks, metrics.cost_micros FROM ad_group_ad WHERE segments.date DURING LAST_30_DAYS
```
**Keyword performance:**
```sql
SELECT keyword_view.resource_name, ad_group_criterion.keyword.text, ad_group_criterion.keyword.match_type, metrics.impressions, metrics.clicks, metrics.cost_micros, metrics.average_cpc FROM keyword_view WHERE segments.date DURING LAST_30_DAYS
```
**Account hierarchy:**
```sql
SELECT customer_client.client_customer, customer_client.descriptive_name, customer_client.id, customer_client.manager, customer_client.status FROM customer_client WHERE customer_client.status = 'ENABLED'
```
## Campaigns
### List Campaigns
```bash
cat > /tmp/list-campaigns.json << 'EOF'
{
"query": "SELECT campaign.id, campaign.name, campaign.status, campaign.advertising_channel_type, campaign.start_date, campaign.end_date FROM campaign ORDER BY campaign.id"
}
EOF
curl -s -X POST "https://googleads.googleapis.com/v24/customers/{customer-id}/googleAds:search" \
--header "Authorization: Bearer $GOOGLE_ADS_TOKEN" \
--header "developer-token: $GOOGLE_ADS_DEVELOPER_TOKEN" \
--header "Content-Type: application/json" \
-d @/tmp/list-campaigns.json
```
### Create Campaign
```bash
cat > /tmp/create-campaign.json << 'EOF'
{
"operations": [
{
"create": {
"name": "My Search Campaign",
"status": "PAUSED",
"advertising_channel_type": "SEARCH",
"campaign_budget": "customers/{customer-id}/campaignBudgets/{budget-id}",
"bidding_strategy_type": "TARGET_SPEND",
"target_spend": {
"cpc_bid_ceiling_micros": "1000000"
},
"network_settings": {
"target_google_search": true,
"target_search_network": true,
"target_partner_search_network": false,
"target_content_network": false
}
}
}
]
}
EOF
curl -s -X POST "https://googleads.googleapis.com/v24/customers/{customer-id}/campaigns:mutate" \
--header "Authorization: Bearer $GOOGLE_ADS_TOKEN" \
--header "developer-token: $GOOGLE_ADS_DEVELOPER_TOKEN" \
--header "Content-Type: application/json" \
-d @/tmp/create-campaign.json
```
### Update Campaign Status
```bash
cat > /tmp/update-campaign.json << 'EOF'
{
"operations": [
{
"update": {
"resource_name": "customers/{customer-id}/campaigns/{campaign-id}",
"status": "PAUSED"
},
"update_mask": "status"
}
]
}
EOF
curl -s -X POST "https://googleads.googleapis.com/v24/customers/{customer-id}/campaigns:mutate" \
--header "Authorization: Bearer $GOOGLE_ADS_TOKEN" \
--header "developer-token: $GOOGLE_ADS_DEVELOPER_TOKEN" \
--header "Content-Type: application/json" \
-d @/tmp/update-campaign.json
```
## Ad Groups
### Create Ad Group
```bash
cat > /tmp/create-adgroup.json << 'EOF'
{
"operations": [
{
"create": {
"name": "My Ad Group",
"status": "PAUSED",
"campaign": "customers/{customer-id}/campaigns/{campaign-id}",
"type": "SEARCH_STANDARD",
"cpc_bid_micros": "1000000"
}
}
]
}
EOF
curl -s -X POST "https://googleads.googleapis.com/v24/customers/{customer-id}/adGroups:mutate" \
--header "Authorization: Bearer $GOOGLE_ADS_TOKEN" \
--header "developer-token: $GOOGLE_ADS_DEVELOPER_TOKEN" \
--header "Content-Type: application/json" \
-d @/tmp/create-adgroup.json
```
## Accessible Customers
List all accounts accessible by the authenticated user:
```bash
curl -s "https://googleads.googleapis.com/v24/customers:listAccessibleCustomers" \
--header "Authorization: Bearer $GOOGLE_ADS_TOKEN" \
--header "developer-token: $GOOGLE_ADS_DEVELOPER_TOKEN"
```
## Guidelines
1. `cost_micros` is in micro-currency units — divide by 1,000,000 for the actual currency amount (e.g., `1000000` = 1.00 USD).
2. Always create campaigns and ad groups with `"status": "PAUSED"` first, then activate after review.
3. Wait for the user to confirm before activating campaigns or modifying live campaigns.
4. Date macros: `TODAY`, `YESTERDAY`, `LAST_7_DAYS`, `LAST_30_DAYS`, `THIS_MONTH`, `LAST_MONTH`.
5. Use `searchStream` instead of `search` for queries expected to return more than 10,000 rows.
6. Campaign types: `SEARCH`, `DISPLAY`, `VIDEO`, `SHOPPING`, `HOTEL`, `PERFORMANCE_MAX`, `DEMAND_GEN`, `TRAVEL`.
7. Page size max is 10,000 for `search`. Use `next_page_token` for pagination.
8. Never include hyphens in customer IDs — use `1234567890`, not `123-456-7890`.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".