Case study · Messaging campaign
621 conversations on a $7 budget
The cheapest run in the set, and the one that most needs its method stated: a $0.01 unit cost is a signal about audience fit, not a repeatable rate card.
- Conversations started
- 621
- Cost per conversation
- $0.01
- Amount spent
- $6.86
Summary
The cheapest run in the set, and the one that most needs its method stated: a $0.01 unit cost is a signal about audience fit, not a repeatable rate card.
Decisions that made the difference
- Used a very small budget to test how well the audience matched the offer
- Treated the result as evidence of audience fit rather than a price that will hold at scale
- Re-derived the unit cost from spend and volume instead of quoting the rounded figure
How to read this result
Platform-reported. $6.86 ÷ 621 is $0.011, so the $0.01 is rounded and should be re-derived before it is quoted. Figures are reported exactly as the platform shows them. The client name is withheld until written permission and a dated account export are in place.
More results
Other case studies
798 website purchases on a $1,052 budget
- Website purchases
- 798
- Cost per purchase
- $1.32
- Amount spent
- $1,052.28
Platform-reported in Meta Ads Manager. No attribution window stated on the export.
Read the methodSales campaign307 purchases at $1.44 each
- Website purchases
- 307
- Cost per purchase
- $1.44
- Amount spent
- $442.26
Platform-reported. The poster’s badge reads $462.26; its own dashboard reads $442.26, and the dashboard wins.
Read the methodSales test101 purchases under a dollar each
- Website purchases
- 101
- Cost per purchase
- $0.93
- Amount spent
- $93.54
Platform-reported. A test-scale budget — a read on unit economics, not on capacity.
Read the methodWant results you can audit?
Give us read access to your ad account. We will tell you where spend is leaking, what is mistracked, and what we would change first.
