Meta claims what would have been bought anyway
Retargeting and brand traffic land in the report as the campaign’s achievement. We separate new and returning customers, measure incrementality — and part of the budget gets freed up.
The ad account almost always shows a ROAS higher than the bank account. We separate new and returning buyers, fix event deduplication and measure the ad-cost-to-revenue ratio on money that reached the account.
Retargeting and brand traffic land in the report as the campaign’s achievement. We separate new and returning customers, measure incrementality — and part of the budget gets freed up.
Pixel and server-side events without deduplication double the purchases: the ROAS in the account looks great, the bank account does not match. We set up event_id and reconcile with the store’s backend.
In seasonal goods the sales window is weeks. Campaigns are warmed up in advance, on last season’s data, not from scratch at peak demand.
Pixel natively, Conversions API, deduplication, reconciliation with orders in the store admin.
Feed, product sets, dynamic retargeting — and control so the campaign does not live off one bestseller.
Separate tracking of the first purchase. The growth metric is new customers, not overall ROAS.
We hold a corridor of ad cost to revenue instead of chasing the peak ROAS of one campaign.
Statics and video for every key SKU and purchase occasion, refreshed as they burn out.
Warm-up before the season, a weekly budget plan, a review afterwards — what we keep for next year.
| 249% | ROMI on a $44,000 budget | Gamers are expensive to acquire — LTV made paid traffic pay off, 249% ROMI |
| 286% | ROMI: $13,516 → $52,165 | Clothing sales with ad spend at 26% of revenue — every dollar invested brought $3.86 |
| 479% | seasonal ROMI: $18,475 → $106,892 | A narrow seasonal window — three seasons in a row, 479% ROMI |
| $142 | cost per sale in a niche with expensive competition | Gamers are expensive to acquire — LTV made paid traffic pay off, 249% ROMI |
Three reasons: view-through attribution, duplicated events and retargeting purchases claimed by the campaign. We reconcile the ad account with orders in the admin and work from the bank figure.
Yes. A browser pixel alone loses part of the events to blockers and ITP. We set up server-side events with deduplication — the signal is restored without doubling.
Yes. In the Christmas ornaments case the client came back three seasons in a row — ROMI above 380% in each.
From $3,000/month. At a smaller volume the algorithm does not collect enough purchases for stable optimization.
The one that holds at the bank account, not in the ad account. We hold a corridor of ad cost to revenue instead of chasing the peak ROAS of one campaign. From our cases: ROMI 249%, ad cost 26% of revenue.
A fixed fee plus a percentage of ad spend. The ad budget is separate — from $3,000 per month.
Egor Balandin
online