keitaro-optimizelisted

# Keitaro Auto-Optimization ## Process 1. Read `keitaro/references/optimization-rules.md` for decision logic 2. Read `keitaro/references/verticals.md` for vertical-specific thresholds 3. Pull performance data via report API 4. Apply rules to identify actions 5. Present action plan with estimated impact 6. Execute only after user confirmation ## Optimization Pipeline ### Step 1: Collect Data Build report grouped by `stream_id` with metrics: clicks, conversions, revenue, cost, profit, roi, cr, epc ### Step 2: Classify Each Flow For each flow, determine status based on vertical thresholds: | Status | Condition | Action | |--------|-----------|--------| | KILL | ROI < kill threshold AND clicks >= min | Recommend pause | | WARNING | ROI in warning range | Monitor, flag | | STABLE | ROI in good range | Keep running | | SCALE | ROI > scale threshold AND clicks >= scale min | Recommend weight increase | | TESTING | clicks < min threshold | Wait for data | ### Step 3: Generate Action Plan Present as prioritized list: ``` Optimization Plan — Campaign #12 ═══════════════════════════════════════ KILL (save $X/day): ✗ Flow "Test Landing C" — ROI: -45%, 180 clicks, 0 conv → Action: Pause flow (saves ~$15/day) SCALE (earn +$X/day): ↑ Flow "DE Mobile" — ROI: +78%, 3,259 clicks, 62 conv → Action: Increase weight 60% → 70% (est. +$12/day) TESTING (wait): ? Flow "New Offer X" — ROI: +15%, 45 clicks, 2 conv → Action: Need 55 more clicks before decision TOTAL ESTIM