iOS broke the tracking. The panic budget cuts broke the growth.
A DTC skincare brand saw reported ROAS collapse from around 3.1x to 1.6x after iOS privacy changes, triggering panic budget cuts, even though real sales had held. Beeyacorp deployed the Meta Conversion API, server-side tagging, and enhanced conversions. Reported ROAS recovered to 3.4x with a 98% event match rate, and the winning campaigns got their budgets back.
A DTC skincare brand saw reported ROAS collapse from around 3.1x to 1.6x after iOS privacy changes, triggering panic budget cuts, even though real sales had held. Beeyacorp deployed the Meta Conversion API, server-side tagging, and enhanced conversions. Reported ROAS recovered to 3.4x with a 98% event match rate, and the winning campaigns got their budgets back.
Reported returns collapsed while the bank balance held steady
After iOS privacy changes stripped browser-based conversion signal, the brand’s reported returns cratered while actual revenue barely moved. Unable to see which campaigns were truly working, the team cut budgets defensively, including on campaigns that were still profitable. The problem was measurement, not marketing, but the response was damaging the business anyway.
Objectives
- Restore accurate conversion measurement. Recover the signal lost to iOS privacy changes.
- Stop unreliable ROAS driving budget decisions. Remove the guesswork from spend allocation.
- Recover confidence to scale profitable campaigns. Let the team invest without fear of a hidden loss.
- Reconcile reported performance with actual revenue. Bring the two numbers back into agreement.
What the first look revealed
The audit is where every engagement starts. What follows is pulled straight from the account, not estimated.
| Area | Finding |
|---|---|
| Analytics | Browser-pixel tracking had lost significant conversion signal after iOS privacy changes. |
| Tracking | No Conversion API or server-side tagging, so events depended entirely on the browser. |
| Attribution | Reported ROAS diverged sharply from actual sales, driving defensive budget cuts. |
| Paid Media | Profitable campaigns were being defunded based on understated returns. |
Reliance on browser pixels alone left the account exposed when iOS restricted them, and without server-side tracking a large share of real conversions never reached the ad platform. That gap between reported and real performance turned every budget decision into a guess.
The strategy behind the turnaround
Restore the signal before touching the budget. We deployed the Meta Conversion API, added server-side tagging, and enabled enhanced conversions, bringing reported performance back in line with reality so the team could scale profitable campaigns with confidence.
Want the same audit on your account? It's free on every new engagement.
30 minutes · Free · No obligation
What we did
- Deployed the Meta Conversion API. Recovered conversion signal lost to browser restrictions.
- Added server-side tagging. Made tracking resilient to future browser changes.
- Enabled enhanced conversions. Improved match quality across the account.
- Reconciled reported ROAS against actual store revenue. Confirmed the fix closed the gap for good.
How it was sequenced
| Phase | Timeframe | What Happened |
|---|---|---|
| Audit | Days 1–7 | Signal-loss assessment and reconciliation |
| Deploy | Week 2 | Conversion API and server-side tracking live |
| Verify | Weeks 2–3 | Event match confirmed, reporting reconciled |
| Scale | Ongoing | Profitable campaigns refunded with confidence |
Restoring reported ROAS from 1.6x to 3.4x
These figures come straight from the account, reflecting the outcomes as documented over the engagement.
| Metric | Before | After |
|---|---|---|
| Reported ROAS | 1.6x | 3.4x |
| Event match rate | Degraded | 98% |
| Conversion signal | Lost to iOS | Recovered |
| Budget decisions | Defensive cuts | Confident scaling |
| Deploy time | — | 2 weeks |
After iOS, collapsed reported ROAS usually signals broken measurement, not failing ads, which is why fixing tracking came before any budget decision. Server-side tracking and the Conversion API took this account's event match rate to 98%, and reconciling reported ROAS to actual revenue is what lets a team scale with confidence rather than cut in fear. More on our e-commerce marketing page.
Frequently Asked Questions
iOS privacy changes stripped browser-based conversion signal, so the ad platform stopped seeing many of the sales that were still happening. The revenue was real; the platform's ability to attribute it was broken.
It sends conversion events to Meta from the server rather than the browser, which recovers signal that browser restrictions block. Combined with server-side tagging, it rebuilds the measurement the platform needs to optimise.
It indicates that almost all conversion events are being matched back to the right users and campaigns. High match quality is what makes reported ROAS trustworthy again, so budget decisions can be based on it.
Because budget decisions made on broken data cut winning campaigns and scale losing ones. Restoring accurate measurement first meant the team could scale profitable campaigns with confidence instead of cutting them in fear.
Related client results
Ready to fix what’s costing you conversions?
We’ll review your acquisition funnel, show you exactly what’s underperforming, and hand you a clear, prioritised plan, whether or not you choose to work with us.
Get a clear diagnosis of your acquisition performance.
- 30-minute review
- Free, with no obligation
- Clear findings and priorities
- You keep the findings
30 minutes · Free · No obligation · You keep the findings