Google Ads

Google Ads

Strategic guide for building new Google Ads campaigns and reporting on existing accounts. Research first, consult intelligently, validate everything, and build with the granular resource tools in dependency order (budget → campaign → targeting → ad groups → ads / asset groups). The API has exactly one campaign create — google_ads_campaigns_create — and the campaign type is just advertising_channel_type; type-specific requirements are enforced by the tools' built-in validators, which return corrective errors. Reporting is GAQL-backed and evidence-first — dashboards are optional presentation surfaces.

Requirements

• Hyper MCP installed and connected. https://app.hyperfx.ai/mcp
• Google Ads integration connected at https://app.hyperfx.ai/apps.

If google_ads_accounts_list is not found, the integration to connect is Google Ads.

How to run the tools in this skill

Every tool in this skill is named by its canonical tool name. Run it with the call your surface gives you:

If a tool is not found: in Hyper chat, find its toolkit id with discover_toolkits and pass it to enable_toolkit. On an MCP client or the CLI, tell the user which integration to connect in Hyper.

Out of scope

• Live optimization mutations (bid adjustments, pausing keywords, restructuring existing campaigns). Reports may recommend these changes; applying them needs explicit per-change user approval.
• Creative generation (headlines, descriptions, images) → the ad-creative-generation skill.
• Cross-platform campaign launches → use this skill for Google, then invoke meta-ads / tiktok-ads separately.

Tool surface

Reads are GAQL (google_ads_gaql_query covers every resource). Writes are one tool per resource operation, named google_ads_<resource>_<create|update|remove>. Generated create and update tools take (customer_id, body), where body is the bare resource object in snake_case. A generated _remove takes body={"resource_name": "customers/<cid>/<collection>/<id>"}. The keyword, location, asset-group, asset-link, image-upload and _delete tools take flat arguments: read them with describe or search_tools.

Rules that must never be forgotten

BUDGETS IN MICROS: $50/day = 50,000,000 micros. Never pass dollar amounts directly.

ALWAYS START PAUSED: Create campaigns with status="PAUSED". Activate only after explicit user approval.

SUMMARIZE BEFORE CREATE: Present the full build plan (budget, campaign settings, targeting, ad groups, ads/assets) and get explicit user approval before the first mutate. Create in dependency order. Generated bodies take the full resource_name that the mutate returns (e.g. "campaign": "customers/<cid>/campaigns/<id>"). The flat tools (google_ads_location_targets_add, google_ads_keywords_create, google_ads_asset_groups_create, google_ads_asset_group_assets_link, google_ads_campaign_assets_link) take the bare id: the last part of that resource name. The tools validate bodies against the real API schema (writable fields, enum values) plus channel-type rules and return corrective errors — fix and retry rather than guessing.

NEVER INVENT: Don't assume URLs, budgets, or location IDs. Don't skip research. Don't invent keywords or copy — creative comes only from the actual site. Don't build without user buy-in.

PLACES COME FROM THE ID: Name a targeted place only from its canonical_name (google_ads_location_targets_list, or geo_target_constant.canonical_name in GAQL). A campaign name or the user's words is not a location.

SMALL SAMPLES: A cost per result from fewer than 10 conversions gets one line that the sample is too small to judge. Do not rank or cut a campaign on that cost alone.

DERIVED NUMBERS SHOW THEIR INPUTS: A total, difference or rate that you compute names the tool values it comes from: "312 carts with no purchase (414 add-to-carts − 102 purchases)".

GAQL GUARDRAILS: Never join ad_group_criterion with search_term_view. Never query more than 5 sub-accounts in a single batch.

See references/constraints.md for the full constraint set.

All reference files live in references/. Read them at references/<file> (e.g. references/discovery.md). They are not in the same directory as this SKILL.md.

Core process

Every campaign build follows this sequence. Do not skip steps.

1. Identify the goal — new campaign, reporting/analysis, or both?
2. Check the routing table and read the files of your row only, before calling any tools. The other reference files are for other tasks
3. Discovery is mandatory for creation (references/discovery.md) — account setup, site scan, conversion tracking check, market research, consultation
4. Present the pre-creation summary and wait for explicit approval
5. Build in dependency order (budget → campaign PAUSED → targeting → ad groups → ads/assets) after approval, by the campaign file; read a section of references/constraints.md only when a step names it
6. Activate only when the user approves

Full workflow: Initial Setup → Research (site + GAQL + market) → Analyze (goals, audience, keywords) → Consult (options + trade-offs) → Recommend (structure + bids) → Confirm (summary approved) → Create in dependency order (PAUSED) → Verify by GAQL → Activate (post-approval).

Routing table

A report names the customer ID, the date range, the GAQL resource queried and its key results, and says whether the output is a written report or a dashboard. It treats rows as evidence, not as recommendations, unless the user asks for recommendations.