Case study · Messaging campaign
253 conversations, twelve cents apiece
A narrower audience with a higher unit cost, kept running because the conversations converted at a rate that justified the premium.
- Conversations started
- 253
- Cost per conversation
- $0.12
- Amount spent
- $31.38
Summary
A narrower audience with a higher unit cost, kept running because the conversations converted at a rate that justified the premium.
Decisions that made the difference
- Chose a narrower, more qualified audience over the cheapest possible conversation
- Judged the campaign on what the conversations turned into, not only on their cost
- Kept it running because downstream conversion justified the higher unit cost
How to read this result
Platform-reported. Conversion downstream of the conversation sits in the client account, not in this figure. 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.
