paid-ads-strategy
When the user wants to plan paid ads strategy, allocate ad budget, or choose paid channels. Also use when the user mentions "paid ads," "paid media," "PPC," "SEM," "web ads," "app ads," "TV ads," "CTV," "OOH," "banner ads," "ad network," "ad alliance," "Taaft ads," "Shopify App Store ads," "Google Ads," "Meta Ads," "PMF testing," "PMF validation," "test product-market fit with ads," "ad spend," "ad budget," "ROAS," "paid acquisition," "Quality Score," or "ad-to-page alignment." For Google Ads execution, use google-ads. For Meta Ads execution, use meta-ads. For landing page alignment, use landing-page-generator.
What this skill does
# Strategies: Paid Ads Guides paid ads strategy: when to use paid acquisition, channel selection, budget allocation, ad-to-landing-page alignment, and cross-platform best practices. Paid ads (Google Ads, Meta, LinkedIn, Reddit, TikTok, etc.) deliver immediate reach and targeting; use when PMF is validated and budget allows. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. **Platform-specific execution**: Web: **google-ads**, **meta-ads**, **linkedin-ads**, **reddit-ads**, **tiktok-ads**. App: **app-ads**. TV/Streaming: **ctv-ads**. ## Before Starting **Check for project context first:** If `.agents/project-context.md` or `.claude/project-context.md` exists, read it before asking questions. Gather this context (ask if not provided): | Area | Questions | |------|-----------| | **Goals** | Primary objective? (Awareness, traffic, leads, sales, app installs) Target CPA/ROAS? Monthly budget? Constraints? | | **Product & offer** | What are you promoting? Landing page URL? What makes it compelling? | | **Audience** | Ideal customer? Problem you solve? What do they search for or care about? Existing customer data for lookalikes? | | **Current state** | Run ads before? What worked/didn't? Pixel/conversion data? Funnel conversion rate? | ## Two Modes: PMF Testing vs Conversion-Driven | Mode | When | Goal | Budget | Metrics | |------|------|------|--------|---------| | **PMF testing** | Pre-PMF; idea validation | Validate demand, messaging, pricing, audience before building | $47–500; small | CTR, sign-up rate, bounce rate; low CTR/high bounce = messaging issue | | **Conversion-driven** | PMF validated | Commercialization; scale; efficient acquisition | Scale; ROAS target | ROAS, CAC, conversion rate | **PMF testing**: Use paid ads as a **learning tool**—simple landing page, "Join Waitlist" or "Get Early Access" CTA, test ad variations (value props, price points, audiences). No full product needed. See **google-ads** for PMF testing setup. **Conversion-driven**: Full funnel; conversion tracking; scale budget. Avoid large-scale paid acquisition before PMF—see **cold-start-strategy**. **Reference**: [Marketing Cactus – Using Google Ads to Test Product-Market Fit](https://mktcactus.com/en/using-google-ads-to-test-product-market-fit-before-launching/) ## When to Use Paid Ads | Condition | Rationale | |-----------|-----------| | **PMF validated** (conversion mode) | Product-market fit confirmed; scale acquisition | | **PMF testing** (validation mode) | Small budget; validate demand, messaging, pricing before building | | **Budget available** | CAC and LTV modeled (conversion); or $47–500 for testing | | **Need speed** | Organic takes months; paid delivers traffic immediately | ## When NOT to Use Paid Ads | Condition | Rationale | |-----------|-----------| | **Pre-PMF + large scale** | Large-scale paid acquisition before PMF wastes budget; use PMF testing mode or cold-start channels first | | **No conversion tracking** | Can't measure ROAS; optimize blindly (PMF testing uses CTR/sign-up) | | **Organic can work** | SEO, content, community may achieve goal at lower cost; see **seo-strategy** | **Cold start**: For acquisition, use Product Hunt, Reddit, directories, founder-led outbound first. For PMF validation, small-budget Google Ads + landing page is valid. See **cold-start-strategy**, **google-ads**. ## Ad Formats by Medium Paid ads span multiple media beyond web. Choose by product type and audience. | Medium | Format | Best for | Skill | |--------|--------|----------|-------| | **Web** | Search, Display, Social (landing page) | Websites, SaaS, e-commerce, leads | google-ads, meta-ads, linkedin-ads, reddit-ads, tiktok-ads | | **Display / Banner** | Ad networks, programmatic, banner ads | Brand awareness; retargeting; publisher sites | display-ads | | **App** | App install, in-app ads, App Store/Play Store | Mobile apps; user acquisition (UA) | app-ads | | **TV / Streaming** | CTV, OTT, linear TV | Brand awareness; streaming viewers; 95% ad completion | ctv-ads | | **Directory / Marketplace** | Taaft, Shopify App Store, G2, Capterra | High-intent directory visitors; app/software discovery | directory-listing-ads | | **Out-of-home (OOH)** | Billboards, transit, DOOH | Brand reach; unskippable; real-world exposure | — | **Web** drives to landing pages; **Display** = banner/network on publisher sites; **App** = install or in-app; **TV/CTV** = awareness or QR/URL; **Directory** = paid placements within Taaft, Shopify App Store, G2, Capterra. ## Platform Selection (Web) | Platform | Best for | Use when | |----------|----------|----------| | **Google Ads** | High-intent search traffic | People actively search for your solution | | **Meta (FB/IG)** | Demand gen, visual products | Creating demand; strong creative assets | | **LinkedIn Ads** | B2B, decision-makers | Job title/company targeting matters; higher ACV | | **Reddit Ads** | Niche communities, discussion-driven | Audience in specific subreddits; authentic, value-first messaging | | **TikTok Ads** | Younger demographics, viral creative | Audience 18–34; video capacity | | **X (Twitter) Ads** | Tech audiences, thought leadership | Audience active on X; timely content | **Decision tree**: High intent? → Google Search. No? → Awareness: Meta/TikTok/YouTube. B2B: LinkedIn. E-commerce: Meta + Google Shopping. **App?** → app-ads. **Streaming/TV?** → ctv-ads. **Display/banner?** → display-ads. **Directory (Taaft, Shopify, G2)?** → directory-listing-ads. ## Dual-Channel Strategy Treat Google Ads and Meta Ads as **complementary**, not competing. Google captures high-intent search at moment of need; Meta creates and shapes demand by introducing brands to new audiences. A dual-channel approach often outperforms single-channel; use unified KPIs (prioritize profit over volume). See **google-ads**, **meta-ads** for platform setup. ## Budget Allocation | Phase | Approach | |-------|----------| | **Testing (2–4 weeks)** | 70% proven/safe; 30% new audiences/creative | | **Scaling** | Consolidate into winners; increase 20–30% at a time; wait 3–5 days between increases | ## Ad Copy Frameworks (Cross-Platform) | Framework | Structure | |-----------|-----------| | **PAS** | Problem → Agitate pain → Introduce solution → CTA | | **BAB** | Current painful state → Desired future state → Your product as bridge | | **Social Proof** | Impressive stat/testimonial → What you do → CTA | ## Creative Best Practices **Image ads**: Clear product screenshots; before/after; stats as focal point; human faces (real); text overlay <20%. **Video ads (15–30 sec)**: Hook (0–3s) → Problem (3–8s) → Solution (8–20s) → CTA (20–30s). Captions always; vertical for Stories/Reels; native feel outperforms polished. **Creative testing order**: 1) Concept/angle 2) Hook/headline 3) Visual style 4) Body copy 5) CTA. ## Retargeting Overview | Funnel stage | Audience | Message | |--------------|----------|---------| | Top | Blog readers, video viewers | Educational, social proof | | Middle | Pricing/feature visitors | Case studies, demos | | Bottom | Cart abandoners, trial users | Urgency, objection handling | **Exclusions**: Existing customers; recent converters (7–14d); bounced visitors (<10s). ## Budget & Metrics | Metric | Purpose | |--------|---------| | **ROAS** | Return on ad spend; primary paid channel metric | | **CAC** | Cost per acquisition; compare to LTV | | **Quality Score** (Google) | Ad relevance, LP experience; higher = lower CPC | | **CPC/CPM** | Cost per click/impression; platform-specific | **Quantified benchmarks**: Quality Score 5→7 can reduce CPC by 30–50%. Smart bidding (Target CPA/ROAS) typically needs ≥30 conversions in 30 days to work effectively. Proper optimization can increase conversion rates 30–150% and reduce CPA 2
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".