Case study · Sales campaign
798 website purchases on a $1,052 budget
A sales objective run to purchase events rather than to clicks, with creative rotated against cost per purchase weekly instead of at month end.
- Website purchases
- 798
- Cost per purchase
- $1.32
- Amount spent
- $1,052.28
Summary
A sales objective run to purchase events rather than to clicks, with creative rotated against cost per purchase weekly instead of at month end.
Decisions that made the difference
- Optimised the campaign for the purchase event, not for link clicks or landing-page views
- Reviewed creative weekly against cost per purchase and paused losing variants
- Kept the reporting unit the same from first week to last so results could be compared
How to read this result
Platform-reported in Meta Ads Manager. No attribution window stated on the export. 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
307 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 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.
