Case study · Sales test
101 purchases under a dollar each
A small test budget taken to statistical usefulness before it was scaled — the cost per purchase was the decision, not the volume.
- Website purchases
- 101
- Cost per purchase
- $0.93
- Amount spent
- $93.54
Summary
A small test budget taken to statistical usefulness before it was scaled — the cost per purchase was the decision, not the volume.
Decisions that made the difference
- Treated the first budget as a test of unit economics, not of capacity
- Ran it until the purchase count was large enough to trust
- Made the scaling decision on cost per purchase, not on total orders
How to read this result
Platform-reported. A test-scale budget — a read on unit economics, not on capacity. 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 methodMessaging campaign741 conversations at five cents each
- Conversations started
- 741
- Cost per conversation
- $0.05
- Amount spent
- $36.11
Platform-reported. A started conversation is not a qualified lead; the two are reported separately.
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.
