export declare const FUNNEL_OPTIMIZE = "# /funnel-optimize \u2014 Funnel Optimization Engine\n\n## What This Does\n\nConversion Rate Optimization across the entire funnel: ad \u2192 click \u2192 land \u2192 read \u2192 act \u2192 convert \u2192 retain. Identifies the weakest link and generates targeted fixes.\n\n## Trigger Context\nTraffic is flowing (from /channels or /creative-test) but conversion rates are below target. Or proactive optimization during scaling.\n\n## Execution Protocol\n\n### Step 1: Map the Conversion Chain\nCollect or estimate data for each stage:\n\n| Stage | Metric | Benchmark | Your Data |\n|-------|--------|-----------|-----------|\n| Ad \u2192 Click | CTR | 1.5-2.5% (Meta), 3-5% (Search) | [user provides] |\n| Click \u2192 Land | Load completion | 95%+ (under 3s) | [user provides] |\n| Land \u2192 Read | Scroll depth / Time on page | 60%+ scroll to CTA, 2+ min | [user provides] |\n| Read \u2192 Act | CTA click rate | 3-8% of page visitors | [user provides] |\n| Act \u2192 Convert | Checkout completion | 30-60% of CTA clickers | [user provides] |\n| Convert \u2192 Retain | Refund rate / M1 completion | <10% refund, >60% M1 | [user provides] |\n\n### Step 2: Identify the Bottleneck\nThe weakest link relative to benchmark is the optimization target. Fixing a non-bottleneck stage wastes effort.\n\n**Diagnosis routing:**\n- Ad \u2192 Click below benchmark \u2192 Creative problem. Route to /creative-test\n- Click \u2192 Land below benchmark \u2192 Technical problem. Page speed, mobile, redirects\n- Land \u2192 Read below benchmark \u2192 Headline/lead mismatch. Ad promises X, page delivers Y\n- Read \u2192 Act below benchmark \u2192 Offer presentation. Value unclear, risk not addressed, CTA weak\n- Act \u2192 Convert below benchmark \u2192 Checkout friction. Too many steps, trust signals missing, payment issues\n- Convert \u2192 Retain below benchmark \u2192 Product problem. Route to Execution OS /feedback for Product Architecture fix\n\n### Step 3: Generate Hypothesis\nFor the identified bottleneck, generate a specific, testable hypothesis:\n- \"Scroll depth is low because the headline references [problem] but the ad referenced [mechanism]\"\n- \"CTA clicks are low because the guarantee is buried below the fold\"\n- \"Checkout abandonment is high because there's no order summary before payment\"\n\nThe hypothesis MUST reference specific elements from the buyer research, Building Blocks, or product architecture. Never generic.\n\n### Step 4: Generate One Variation \u2014 IMPLEMENTATION-READY\nCreate exactly ONE change that tests the hypothesis. Output the actual replacement content, not a description of what to change:\n\n**If headline problem:**\n```\nCURRENT HEADLINE: \"[paste current from landing page file]\"\n\nTEST VARIATION A: \"[new headline \u2014 outcome-first angle]\"\nTEST VARIATION B: \"[new headline \u2014 mechanism-first angle]\"\nTEST VARIATION C: \"[new headline \u2014 pain-first angle]\"\n\nIMPLEMENT: Replace headline text on landing page. Keep everything else identical.\nSPLIT: 50/50 traffic between current and best-performing variation.\n```\n\n**If CTA problem:**\n```\nCURRENT CTA: \"[paste current button text + surrounding copy]\"\n\nTEST VARIATION:\n  Button text: \"[new text]\"\n  Supporting line above button: \"[new urgency/clarity line]\"\n  Placement change: [move above fold / add second CTA at mid-page / etc.]\n\nIMPLEMENT: [exact location on page to change]\n```\n\n**If email subject line problem:**\n```\nCURRENT SUBJECT: \"[paste current]\"\n  Open rate: [X]%\n\nTEST SUBJECTS (send to equal splits):\n  A: \"[new subject \u2014 curiosity angle]\"\n  B: \"[new subject \u2014 benefit angle]\"\n  C: \"[new subject \u2014 urgency angle]\"\n\nIMPLEMENT: Split list into 4 equal segments. Send A/B/C to 3 segments, current to 1.\n```\n\n**If checkout problem:**\n```\nCURRENT FLOW: [describe current steps]\nFRICTION POINT: [specific step where drop-off occurs]\n\nTEST VARIATION:\n  Remove: [specific field or step]\n  Add: [trust signal, summary, or simplification]\n  Result: [X] steps reduced to [Y] steps\n\nIMPLEMENT: [exact page/form changes needed]\n```\n\n**Rule: One variable at a time.** Complete redesigns make it impossible to learn what worked. The variation must be implementable in under 10 minutes.\n\n### Step 5: Define Test Parameters\n- Traffic split: 50/50 between control and variation\n- Minimum sample: 100 conversions per variation for statistical significance (adjust if low-traffic)\n- Duration: minimum 7 days to account for day-of-week variance\n- Success metric: primary KPI for the bottleneck stage\n- Decision threshold: 95% statistical confidence before declaring winner\n\n### Step 6: Document and Iterate\n- Winner replaces control\n- Loser is discarded with documented learning\n- Re-measure the full conversion chain\n- Identify NEW bottleneck (fixing one often reveals the next)\n- Cycle repeats\n\nSave optimization report to `assets/[market-name]/traffic/funnel-optimization/test-[N].md`\nUpdate pipeline-state.json with optimization history.\n\n## Integration with Execution OS\n- If diagnosis points to OFFER problem (Read \u2192 Act) \u2192 Alert Execution OS. May need Building Block revision via /feedback\n- If diagnosis points to PRODUCT problem (Convert \u2192 Retain) \u2192 Route to Execution OS /feedback for Product Architecture iteration\n- If diagnosis points to COPY problem (Land \u2192 Read) \u2192 Generate new copy variation AND notify Execution OS to update source assets\n- If diagnosis is purely traffic-side \u2192 Handle internally\n- **Organic bounce rate high** \u2192 Intent mismatch between search query and page content \u2192 Route to `/seo-check` for content-query alignment audit\n\n**Core Web Vitals note:** Page speed directly affects both search rankings and ad Quality Scores. Run [PageSpeed Insights](https://pagespeed.web.dev/) on the landing page \u2014 mobile score below 70 is a conversion headwind independent of copy quality. Fix speed before testing copy variations.\n\n## Autonomy\nTier 1 \u2014 Full Auto for diagnosis and variation generation.\nTier 2 \u2014 Notify & Proceed for implementing variations on test pages.\nTier 3 \u2014 Recommend & Wait if the diagnosis suggests a Building Block or Product issue (requires Execution OS coordination).\n\n## Next Step\nAfter optimization stabilizes \u2192 `/scale`\nIf fundamental offer issues \u2192 Execution OS `/feedback`";
//# sourceMappingURL=funnel-optimize.d.ts.map