/launch-ad-campaign

name: launch-ad-campaign
description: "Create and launch a paid ad campaign on Google, Meta, LinkedIn, or TikTok through the connected ad-platform MCP — campaign structure, audience targeting, bid strategy, negative targeting, creative quality scoring, compliance review, and a post-launch monitoring schedule. A mandatory execution gate shows the full spend summary and requires an explicit typed yes before anything goes live; budgets over brand thresholds force re-confirmation and every approval is recorded via approval-manager.py. Triggers on \"/digital-marketing-pro:launch-ad-campaign\", \"launch the Google Ads campaign\", \"put these Meta ads live\", \"start the LinkedIn campaign tomorrow\", \"deploy our TikTok ads\". Reads the brand profile's budget thresholds, guidelines, and agency SOPs; it is the paid-ads subset that /digital-marketing-pro:launch-campaign delegates to."
disable-model-invocation: false
argument-hint: "[platform]"

/digital-marketing-pro:launch-ad-campaign

Purpose

Create and launch a paid advertising campaign on the specified ad platform with proper campaign structure, audience targeting, bid strategy, budget controls, and compliance checks. Includes mandatory budget safeguards that require explicit re-confirmation when spend exceeds brand thresholds, and sets up post-launch monitoring to catch early performance issues before budget is wasted on underperforming configurations.

Execution gate (MANDATORY — cannot be skipped)

1. Present the full preview — recipients / spend / changes / compliance — as an **Execution Summary** before touching any live system. 2. The user must type `yes` (or an equivalent explicit approval). ANY other input — ambiguous, implied, partial, or absent approval — cancels the run. 3. Never proceed on ambiguous input. Never auto-retry a failed execution; a failure needs human review before any re-run. 4. Record the approval with `python "${CLAUDE_PLUGIN_ROOT}/scripts/approval-manager.py" --brand {slug} --action create-approval --data '{"risk_level":"<tier>","summary":"..."}'` **before** executing, then `python "${CLAUDE_PLUGIN_ROOT}/scripts/approval-manager.py" --brand {slug} --action mark-executed --id {approval_id}` after the platform confirms success.

Input Required

The user must provide (or will be prompted for):

• **Ad platform**: Where to launch — Google Ads, Meta Ads, LinkedIn Ads, or TikTok Ads — must have the corresponding MCP server connected
• **Campaign objective**: Primary goal — awareness (reach/impressions), consideration (traffic/engagement/video views), or conversion (leads/sales/app installs/ROAS target)
• **Budget**: Daily budget or lifetime budget with currency and any maximum CPC or CPA caps the brand requires
• **Campaign dates**: Start date, end date, and any dayparting or ad scheduling preferences (hours of day, days of week)
• **Audience targeting**: Demographics (age, gender, income), interests, behaviors, custom audiences (email lists, website visitors), lookalike or similar audiences, and retargeting segments — with geographic and language targeting
• **Ad creative**: Headlines (multiple variants for responsive ads), descriptions, images or video assets, display URLs, final URLs, and sitelink extensions or callout assets where applicable
• **Bid strategy preference**: Manual CPC, maximize conversions, target CPA, target ROAS, maximize clicks, or platform-recommended — with any bid caps, floors, or portfolio bid strategy settings
• **Conversion tracking**: Which conversion events to optimize for, pixel or tag installation status, conversion value assignment, and attribution window preference (7-day click, 1-day view, etc.)
• **Negative targeting**: Negative keywords (Search), placement exclusions (Display/Video), or audience exclusions to prevent wasted spend on irrelevant traffic
• **Landing page**: Destination URL(s) with confirmation that the page is live, loads under 3 seconds, and has conversion tracking installed
• **Campaign naming convention**: Custom naming format or use the brand's standard naming convention from agency SOPs for consistent cross-platform reporting
• **Ad extensions or assets**: Optional — sitelinks, callout extensions, structured snippets, price extensions, or lead form extensions for Google Ads; instant experience or lead forms for Meta; conversation ads or message ads for LinkedIn
• **Remarketing strategy**: Optional — whether this campaign should feed into a retargeting funnel, and if so, which audiences to build from campaign engagers (website visitors, video viewers, lead form openers)
• **UTM parameters**: Tracking parameters for all destination URLs (source, medium, campaign, content), or auto-generate based on campaign naming conventions

Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. Also check for guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. 2. **Verify budget against brand thresholds**: Check the campaign budget against `budget_range` in `profile.json`. If the daily or lifetime budget exceeds the brand's defined maximum, halt and require explicit re-confirmation from the user with the exact dollar amount displayed prominently. This safeguard cannot be bypassed — it protects against accidental overspend. 3. **Verify ad platform connection**: Check which ad platform MCP server is connected and confirm it matches the user's target platform. Verify conversion tracking pixel or tag is active on the brand's website. If not connected, instruct the user to configure the MCP server and tracki