Campaign comparison

4 with activity · click a header to sortExport CSV
List — all-time, ignores date filterSelected range — 08/16/2026 → 08/16/2026
CampaignList sizePenetrationList completionCallable loadedCallable completionDialsHoursDPHContactsContact %CPHNet contactNet contact %SalesConversionSPHCPSAHT saleAHT net, no saleAHT other contact
ACA00004 · PSX-1 DB-1
ACA_REN_PSX-1_DB-1
10,268100.0%28.3%00.000.0%00
ACA00009 · PSX-30
ACA_REN_PSX-30
5,994100.0%38.2%00.000.0%00
ACA00011 · PRX-30 AR Decline
ACA_REN_PRX-30_AR Decline
000.000.0%00
ACA00012 · PSX-1 DB-1
ACA_REN_PSX-1_DB-1
000.000.0%00
Total00.000.0%00

Dials over time

by ISO week · top 5 by dials
00.250.50.751ACA00004 · PSX-1 DB-1 · 2026-W33 — 0ACA00009 · PSX-30 · 2026-W33 — 0ACA00011 · PRX-30 AR Decline · 2026-W33 — 0ACA00012 · PSX-1 DB-1 · 2026-W33 — 02026-W33
DialsACA00004 · PSX-1 DB-1ACA00009 · PSX-30ACA00011 · PRX-30 AR DeclineACA00012 · PSX-1 DB-1

Two completion figures, never merged. List completion is attempts ÷ (list size × attempt cap), the rulebook §A.7 figure. Callable completion is attempts ÷ the callable records in campaign_leads.csv, a different source that is not yet in hand (blocker B3) — so that column is empty rather than quietly falling back to the other one. Ruled 2026-08-05: the ambiguity stays visible.

Per-campaign attribution is reattributed. 2 L3 de-mislabel rules are in force, so some calls are counted under a different campaign than the dialer recorded — per-campaign figures here will not match previously reported history. Program totals are identical either way: reattribution moves calls between campaigns, it does not create or destroy any. Penetration is capped at 100% by rulebook §C, and that cap hides the consequence: ACA00009 has dialed far more unique leads than its list contains, which is physically impossible and points at attribution rather than at dialing (FACTS.md L21). The date rule closes most of that gap; the remainder needs the prior-call-id extract (blocker B4).