export declare const TRAFFIC_ANALYTICS = "# /traffic-analytics \u2014 Traffic Analytics & Attribution\n\n## What This Does\n\nPerformance analysis, attribution, and feedback routing. Translates raw campaign data into actionable intelligence and feeds it back to the Execution OS Optimizer.\n\n## Trigger Context\nAnytime the user has performance data to analyze. Can run daily, weekly, or on-demand.\n\n## Execution Protocol\n\n### Step 1: Collect Data\nProvide the user with this PASTE-IN TEMPLATE. They fill in the numbers, paste it back, and the agent processes it:\n\n```\nTRAFFIC DATA \u2014 [date range]\n\nSPEND & REVENUE:\n  Total Ad Spend: $\n  Total Revenue: $\n  Number of Sales:\n\nCHANNEL: [Meta / Google / YouTube / Email / Other]\n  Impressions:\n  Clicks:\n  CTR: %\n  CPC: $\n  Conversions:\n  CPA: $\n  ROAS: x\n\nLANDING PAGE:\n  Page Views:\n  Avg Time on Page: min sec\n  Scroll to CTA: %\n  CTA Clicks:\n  Bounce Rate: %\n\nEMAIL (if running):\n  Emails Sent:\n  Open Rate: %\n  Click Rate: %\n  Unsubscribe Rate: %\n\nPRODUCT:\n  Refund Requests:\n  Module 1 Completion: %\n  Support Tickets:\n\nCREATIVE PERFORMANCE (per ad):\n  Ad [name/ID]: Spend $__ | Impressions __ | CTR __% | CPA $__ | Conv __\n  Ad [name/ID]: Spend $__ | Impressions __ | CTR __% | CPA $__ | Conv __\n  Ad [name/ID]: Spend $__ | Impressions __ | CTR __% | CPA $__ | Conv __\n\nORGANIC (optional \u2014 include if /content-engine is active):\n  GSC Impressions (last 28 days):\n  GSC Clicks (last 28 days):\n  GSC Avg Position:\n  Top performing page:\n  AI citation check: Cited by ChatGPT? Y/N | Perplexity? Y/N | AI Overview? Y/N\n```\n\nIf the user pastes partial data, work with what's available. Flag which metrics are missing and what they'd unlock if provided.\n\nAccept data in any format \u2014 the template above is ideal but Claude should parse dashboards, screenshots described in text, or conversational summaries equally.\n\n### Step 2: Organize into Metrics Hierarchy\n\n**Tier 1 \u2014 Revenue Metrics (the only ones that matter long-term):**\n- Total Revenue generated\n- ROAS (Return on Ad Spend) = Revenue / Ad Spend\n- Profit = Revenue - (Ad Spend + COGS + Overhead)\n- LTV estimate (if repeat purchase data exists)\n\n**Tier 2 \u2014 Conversion Metrics (efficiency of converting traffic):**\n- CPA (Cost Per Acquisition) = Ad Spend / Conversions\n- Conversion Rate = Conversions / Clicks\n- Cost Per Lead = Ad Spend / Leads\n- Email Conversion Rate = Sales / Email Subscribers\n\n**Tier 3 \u2014 Engagement Metrics (leading indicators):**\n- CTR (Click-Through Rate) = Clicks / Impressions\n- Landing Page Scroll Depth and Time on Page\n- Email Open Rate and Click Rate\n- Video View Rate and Hook Rate\n\n**Tier 4 \u2014 Reach Metrics (vanity unless contextualized):**\n- Impressions, CPM, Frequency, Reach\n- Only useful for diagnosing delivery issues\n\n### Step 3: Benchmark Comparison\nCompare each metric against:\n- Industry benchmarks (from traffic strategy research)\n- Historical performance (from previous analytics reports)\n- Target KPIs (from traffic strategy document)\n\nFlag any metric that is:\n- 20%+ below target \u2192 PROBLEM (needs immediate attention)\n- Within 20% of target \u2192 MONITORING (watch but don't react yet)\n- At or above target \u2192 HEALTHY (maintain or scale)\n\n### Step 4: Diagnose and Route\n\n**Traffic-side issues (Traffic Agent handles internally):**\n- Low CTR \u2192 Creative problem \u2192 /creative-test\n- High CPM \u2192 Audience saturation \u2192 /scale (horizontal)\n- High frequency \u2192 Audience exhaustion \u2192 New audiences needed\n- Low video view rate \u2192 Hook problem \u2192 New creative hooks\n\n**Funnel-side issues (Traffic Agent + Execution OS):**\n- High bounce rate \u2192 Ad-page mismatch \u2192 /funnel-optimize\n- Low scroll depth \u2192 Headline/lead problem \u2192 /funnel-optimize\n- Low CTA clicks \u2192 Offer presentation \u2192 /funnel-optimize + possibly /feedback\n\n**Offer-side issues (Route to Execution OS):**\n- High traffic + good engagement + no conversions \u2192 Offer problem \u2192 Execution OS /feedback\n- Conversions but high refunds \u2192 Product problem \u2192 Execution OS /feedback (Product Architecture)\n- Conversions but no repeat/referral \u2192 LTV problem \u2192 Product or retention issue\n\n**Organic-side issues (Route to /seo-check or /content-engine):**\n- Impressions high / clicks low \u2192 Title/meta description optimization needed \u2192 `/seo-check`\n- Position 5-15 on target keywords \u2192 Content depth insufficient \u2192 add sections, update stats \u2192 `/seo-check`\n- Not cited by AI (ChatGPT/Perplexity/AI Overview) \u2192 Citation magnet gap \u2192 `/seo-check` + `/content-engine`\n- Organic traffic declining \u2192 Content decay \u2192 `/seo-check` freshness audit\n- Organic traffic high / no conversions \u2192 Content-to-offer bridge broken \u2192 `/funnel-optimize`\n\n**Scaling signals (Route to /scale):**\n- All metrics healthy + budget headroom \u2192 Ready to scale\n- Primary channel plateauing + secondary channel showing promise \u2192 Channel rebalance\n\n### Step 5: Generate Analytics Report\n\nReport format:\n```\nTRAFFIC ANALYTICS \u2014 [Market Name] \u2014 [Date Range]\n\nREVENUE SNAPSHOT:\nTotal Spend: $___  |  Revenue: $___  |  ROAS: ___x  |  Profit: $___\n\nCHANNEL PERFORMANCE:\n[Channel 1]: CPA $__ | CTR __% | Conv Rate __% | Status: [HEALTHY/MONITOR/PROBLEM]\n[Channel 2]: CPA $__ | CTR __% | Conv Rate __% | Status: [HEALTHY/MONITOR/PROBLEM]\n\nCONVERSION CHAIN:\nAd\u2192Click: __% [\u2705/\u26A0\uFE0F/\uD83D\uDD34]\nClick\u2192Land: __% [\u2705/\u26A0\uFE0F/\uD83D\uDD34]\nLand\u2192Read: __% [\u2705/\u26A0\uFE0F/\uD83D\uDD34]\nRead\u2192Act: __% [\u2705/\u26A0\uFE0F/\uD83D\uDD34]\nAct\u2192Convert: __% [\u2705/\u26A0\uFE0F/\uD83D\uDD34]\nConvert\u2192Retain: __% [\u2705/\u26A0\uFE0F/\uD83D\uDD34]\n\nBOTTLENECK: [Identified weakest link]\nDIAGNOSIS: [Specific hypothesis]\nRECOMMENDED ACTION: [Which command to run + specific instructions]\n\nCREATIVE PERFORMANCE:\n[Ranked list of active creatives by primary KPI]\nWinners: [...]  |  Fatiguing: [...]  |  Kill: [...]\n\nSCALING STATUS:\nReadiness: [Met/Not met \u2014 which criteria missing]\nRecommendation: [Hold / Vertical scale / Horizontal scale / Channel scale]\n```\n\n### Step 6: Save and Update State\n- Save report to `assets/[market-name]/traffic/analytics/report-[date].md`\n- Update pipeline-state.json traffic_performance object\n- If routing to Execution OS: flag the issue in pipeline state for /feedback to consume\n\n## Autonomy\nTier 1 \u2014 Full Auto for data analysis and report generation.\nTier 2 \u2014 Notify & Proceed for routing recommendations.\n\n## Next Step\nBased on diagnosis: /creative-test, /funnel-optimize, /scale, or Execution OS /feedback";
//# sourceMappingURL=traffic-analytics.d.ts.map