Paid Media
Saudi and the UAE in One Meta Account Is Why Your Numbers Look Fine
The same product, the same creative and the same account can produce completely different economics in Riyadh and in Dubai. When both sit inside one reported number, the healthy market pays for the one that is bleeding, and nothing in Ads Manager tells you that is happening.
Expert Perspective · Guest Contribution
Nearly every Gulf account I am asked to look at is structured the same way. One campaign, one product, creative in Arabic and English, targeting set to Saudi Arabia and the United Arab Emirates together because they are both Gulf and the product is the same. The reported return on ad spend sits somewhere respectable, the client is reasonably happy, and the question they bring me is how to scale it.
The question I ask back is what the return looks like in each country separately. Often nobody has checked. When we do check, the two numbers are frequently far enough apart that one of the markets has been losing money on every order for months, funded quietly by the other one.
A blended number is a weighted average, not a result
This is arithmetic rather than anything to do with advertising. If one market returns 5.0 and another returns 1.6, and the spend is split evenly, the account shows 3.3. Nothing in that 3.3 is false. It is also not a number that describes either market, and it is not a number you can make a decision with.
The reason this bites harder in the Gulf than elsewhere is that the two markets genuinely are different businesses wearing the same product. Average order values differ. Shipping cost and delivery time differ, particularly once you are outside the main cities. Competitive density on Meta differs, which moves your cost per result. And the share of orders that are cash on delivery differs, which decides how much of your reported revenue you will actually collect.
Those are not small adjustments stacked on a common baseline. They compound, and they compound in the same direction, which is how you end up with two numbers that are not close to each other.
A worked illustration
These figures are modelled on stated assumptions to show the shape of the problem. They are not measurements of a particular account, and your own numbers will differ.
Say you spend $5,000 a month in each market on the same product at a $60 average order value and a 40 percent contribution margin, so $24 of gross profit per order. In market A the cost per purchase is $10 and almost everything is prepaid, so $5,000 buys 500 orders, 500 collected, $12,000 of gross profit against $5,000 of spend.
In market B the cost per purchase is $18 because competition is heavier, and 60 percent of orders are cash on delivery with a fifth of those refused at the door. That $5,000 buys 278 orders, of which about 245 are actually collected. Gross profit is roughly $5,900 against $5,000 of spend, before you count the shipping you paid out and back on the 33 parcels that came home.
Once that return shipping is counted, market B is close to breaking even or slightly behind it. The account, meanwhile, reports a perfectly reasonable blended figure, and the obvious next move looks like adding budget.
The optimisation makes it worse, not better
There is a second mechanism underneath the first one, and it is the part that turns a reporting problem into a money problem.
When budget is allowed to move freely across a campaign, the delivery system sends it toward wherever conversions are cheapest to buy. Cheapest is not the same as most profitable. A market with a lower cost per purchase but a lower collection rate, a higher return rate or a worse margin looks like the better bet to a system that is only shown the purchase event.
So the system does exactly what you asked, scales the market that generates the cheapest checkouts, and your blended number stays acceptable while the mix underneath it drifts toward the weaker business. This is not a flaw in the platform. It is a measurement failure on our side: we optimised against the event we could send back easily instead of the outcome we actually wanted.
What to do about it
Separate the markets. One campaign per country, with its own budget, is the entire fix for the reporting half of the problem, and it costs nothing except a slightly less tidy account. If your volume is too small to split without starving the learning phase, you have a different and more urgent problem, which I have written about separately.
Then set a different target for each one. A single breakeven return across the account is meaningless when the margin, the shipping cost and the collection rate differ. Derive the target from each market's own contribution margin and its own refusal rate, and expect the two targets to be far apart. A market that has to clear 3.3 and a market that has to clear 2.1 are not failing and succeeding, they are two businesses with different costs.
Finally, send back something closer to the truth. If your orders are confirmed before dispatch, or you know which ones were collected, feeding that back through the Conversions API rather than the browser pixel alone lets the system optimise toward orders that became money instead of orders that became a delivery attempt. That is the only version of this where the automation is working on your side.
None of this is exotic. It is one campaign per market, one target per market, and a conversion signal that reflects cash rather than checkouts. The reason it keeps not happening is that the blended number looks fine, and a number that looks fine is very hard to argue with until somebody takes it apart.
The longer version
I cover Gulf account structure, budget distribution and the regional advertising rules in detail in the Meta Ads in the GCC and MENA guide on qlev, and teach the full method in the Digital Marketing and Content Strategy course. This article is the argument for separating the markets. That one is how to build the account once you have.
Sources
- Meta Business Help Center, Purchases ROAS (return on ad spend), for how Meta defines and attributes purchase conversion value, which is the reported figure that blends across markets before any margin or collection correction.
- Meta for Developers, Conversions API documentation, for sending server-side conversion events, which is the mechanism for reporting a collected order rather than a completed checkout.
The $60 average order value, the 40 percent contribution margin, the $10 and $18 costs per purchase, the 60 percent cash on delivery share and the 20 percent refusal rate are modelled illustrations on the assumptions stated beside them, not measurements of any particular account. Checked against Meta's published documentation on 25 October 2026.
