chore: add MVP planning backlog

backlog/tasks/task-19 - Add-campaign-performance-metrics.md

@@ -0,0 +1,44 @@
+---
+id: TASK-19
+title: Add campaign performance metrics
+status: To Do
+assignee: []
+created_date: '2026-06-03 19:15'
+labels:
+  - mvp
+  - analytics
+  - campaigns
+dependencies:
+  - TASK-15
+  - TASK-16
+  - TASK-17
+references:
+  - PRD.md
+priority: medium
+ordinal: 19000
+---
+
+## Description
+
+<!-- SECTION:DESCRIPTION:BEGIN -->
+Build the campaign metrics layer that summarizes acquisition progress from Convex data and enriches it with Rybbit audit signals. This is the practical reporting view Matthias uses to compare niches, regions, campaign runs, and outcomes.
+<!-- SECTION:DESCRIPTION:END -->
+
+## Acceptance Criteria
+<!-- AC:BEGIN -->
+- [ ] #1 Campaign dashboard shows found leads, leads with contact, Kontakt fehlt, audits created, approvals open, emails sent, follow-ups planned/sent, responses, conversations, offers, wins, and losses
+- [ ] #2 Metrics can be filtered by campaign, niche/category, PLZ/region, radius, priority, status, and timeframe
+- [ ] #3 Campaign run detail shows new leads, skipped duplicates, blacklisted/skipped leads, errors, and audits generated
+- [ ] #4 Rybbit-derived audit opens and CTA clicks are shown alongside Convex sales funnel metrics
+- [ ] #5 Metrics remain readable and lightweight, without becoming a full enterprise CRM dashboard
+<!-- AC:END -->
+
+## Implementation Plan
+
+<!-- SECTION:PLAN:BEGIN -->
+1. Define metric aggregation queries from campaigns, leads, audits, outreach, and run logs.
+2. Add filters for campaign, category, region, timeframe, priority, and status.
+3. Build campaign overview cards and run-detail tables.
+4. Merge Rybbit API-derived audit activity into the visible analytics where available.
+5. Add empty/error states and verify metrics update after lead, audit, send, and status changes.
+<!-- SECTION:PLAN:END -->