Holiday Campaign · Meta Ads · Email · Local/In-person
Hanukkah 2026 Meta Ads: Small Budget, High ROAS
7.79x ROAS on a $406 budget — and the GA4 tracking gap I caught mid-campaign and documented a fix for.
7.79x
META ROAS · 7.59x ON CONSERVATIVE ESTIMATE
$14.50
COST PER CONVERSION
$406
TOTAL SPEND · 28 PURCHASES
3 wks
SINGLE TIGHTLY-TARGETED CONVERSION CAMPAIGN
Context
A 3-week Hanukkah catering push on Meta Ads, run on a genuinely small budget.
Problem
Catering products only make sense as paid-acquisition targets above a certain order value — the challenge was proving the channel could work at all on a shoestring spend, and figuring out why it worked so I could repeat it.
What I did
- Ran a single, tightly-targeted Meta conversion campaign for 3 weeks, total spend $405.86.
- Cross-checked Meta’s platform-reported revenue against a conservative, order-count-based estimate (28 orders × $110 realistic AOV) instead of trusting the platform number blindly.
- Identified a GA4 tracking gap mid-campaign — purchases weren’t firing as Key Events, making multi-channel attribution invisible — and wrote up the exact fix (purchase event with value/currency/transaction_id, UTM normalization, DebugView validation) as the #1 priority for the following month.
- Turned the result into a reusable rule for the business: paid ads only pay off on high-AOV catering, not low-ticket items — and recommended bundling / minimum-order thresholds to protect that going forward.
The hard data
HANUKKAH 2026 · META ADS MANAGER
{{ r.k }}
{{ r.v }}
- 7.79x ROAS on Meta’s platform numbers, 7.59x on a conservative AOV-adjusted estimate — both held up under scrutiny.
- $14.50 cost per conversion, 28 purchases, $405.86 total spend.
- Delivered not just a “campaign that worked” but a diagnosed measurement gap and a documented fix plan — the kind of finding that compounds across every future campaign, not just this one.