1.8x → 5.8x ROAS
after pixel fix
UAE e-commerce brand running Meta Ads with a pixel configured to fire on the wrong conversion event for 11 months. The algorithm had been optimising toward the wrong signal the entire time. ROAS tripled within the first campaign cycle after the event was corrected.
A stalled ROAS often traces to one misconfigured tracking event rather than the campaign itself, this case shows an 11-month-old Meta Ads account where a single wrongly-tagged event was capping ROAS at 2.1x, and correcting it alone moved ROAS to 5.8x in 42 days.
Reasonable CPM. Reasonable CTR. ROAS stuck below 2x.
A UAE-based e-commerce brand had been running Meta Ads for 11 months. Campaign structure looked reasonable from the surface: prospecting, retargeting, decent creatives. But ROAS had never exceeded 2.1x. The brand had attributed this to competitive pressure and product margin constraints, and had accepted it as the ceiling.
The issue was identified in the first 30 minutes of the audit. The Meta pixel on the product purchase page was firing an AddToCart event instead of a Purchase event. For 11 months, the algorithm had been told that adding a product to cart was a purchase, and it had been optimising, very effectively, for cart additions. People who were likely to add items to cart but never check out.
One wrong event. Eleven months of misdirected optimisation.
Purchase event on checkout confirmation page firing as AddToCart, incorrect event parameter in GTM trigger configuration
Signal quality 7.2/10 in Meta Events Manager, acceptable rating masking the wrong event type being optimised
Custom audience for purchase retargeting built on AddToCart events, meaning the retargeting pool was full of non-buyers
Server-side CAPI absent: all tracking browser-side only, with an estimated 35% signal loss from iOS and ad blockers
Fix the event. Rebuild the audiences. Implement CAPI.
The purchase event was corrected in GTM: AddToCart trigger removed from the checkout confirmation page, Purchase event added with correct parameters including value and currency. Verified in Meta Events Manager test events before going live.
Server-side CAPI implemented via GTM Server Container. Signal quality brought from 7.2 to 9.0. Purchase retargeting audience rebuilt from scratch using verified purchase events. The algorithm was given 28 days to exit the learning phase on clean signal before any budget changes were made.
No campaign structure changes were made initially. The objective was to isolate the signal fix as the variable, not to change structure and signal simultaneously and attribute results ambiguously.
1.8x to 5.8x. One broken event tag for 11 months.
ROAS moved from 1.8x to 5.8x over 42 days from the date the purchase event was corrected. The algorithm exited the learning phase after 18 days and began delivering to audiences with genuine purchase propensity for the first time. Revenue per campaign increased 3.2x with no budget change.
Wrong event type can misdirect an algorithm for months, and the data will not tell you
A ROAS ceiling of 1.8x for 11 months was not a creative problem or a budget problem. It was a measurement problem. Meta Events Manager showed signal quality of 7.2/10, sufficient to mask the underlying issue. The platform was reporting performance accurately against the event it had been given. The event itself was wrong. This case demonstrates why every engagement starts with a tracking audit before any campaign decision is made.
See Meta & Google Ads Service →How can one tracking error affect ROAS for almost a year?
The Purchase event was firing as AddToCart on the checkout confirmation page, a parameter error that had gone undetected for 11 months. Meta’s algorithm was optimising toward add-to-cart behaviour, not actual purchases, so campaigns kept reaching browsers rather than buyers regardless of budget or creative changes.
Was anything changed in the ad creative or targeting?
No creative or audience changes were made before the event was corrected. The fix sequence was: correct the Purchase event and its parameters in GTM, verify it in Meta Events Manager, migrate to CAPI, then let the algorithm relearn on accurate data.
How long after the fix did ROAS improve?
ROAS moved from 1.8x to 5.8x over 42 days from the date the Purchase event was corrected. The algorithm exited its learning phase after 18 days and began delivering to audiences with genuine purchase propensity from that point forward.
Direct access.
No account managers.
If your campaigns are producing results you cannot verify, reach out. Direct access from the first message.