Paid Media for Gulf Ecommerce: What Changes in Saudi Arabia and the UAE

Two Markets, One Region

Plenty of brands enter the Gulf with one campaign structure, one landing page and one set of assets, then find that performance in Riyadh looks nothing like performance in Dubai.

The countries differ in ways that touch campaign mechanics directly. Separate data protection regimes with separate regulators. Different dominant payment methods. Different practical language mix, even though Arabic is official in both. Different retail peaks.

None of that is exotic. It is the same work you would do before launching in France versus Germany. It gets skipped more often because the region gets treated as one line on a media plan.

The Compliance Points, Briefly

Two things are worth knowing before you build the consent flow, and both should then go to a local adviser.

Saudi Arabia's Personal Data Protection Law is in force and enforced by the Saudi Data and Artificial Intelligence Authority, which publishes the law and its implementing regulations on its regulations and policies pages. The law restricts direct marketing: consent is required before sending advertising material to someone through their personal communication channels, and there has to be a simple way for them to stop receiving it.

The UAE has a federal regime under Federal Decree-Law No. 45 of 2021, summarised on the UAE government portal. Separately, entities established in the DIFC and ADGM financial free zones fall under those zones' own data protection laws instead.

Which regime reaches your business depends on where your entity is established, where the data sits and who you are marketing to. That determination is a legal question, and it is worth putting to counsel in the relevant jurisdiction before you write consent copy. What follows is the operational consequence rather than the legal analysis.

The practical version: record consent per channel with a timestamp and the wording shown, and make the opt-out work. A list built from pre-ticked boxes is a liability in Saudi Arabia regardless of how it would be treated elsewhere.

Worked Example: What Cash on Delivery Does to Reported ROAS

Cash on delivery remains a common payment choice across the region. It creates a measurement problem that is purely mechanical, and the arithmetic is worth doing on your own numbers.

An order placed is not revenue received. Some cash orders are refused at the door, returned or never delivered. If your purchase event fires at checkout with the basket value attached, every failed order reaches Google and Meta as a completed conversion carrying full revenue.

Here is the shape of it. The figures below are illustrative and chosen to show the mechanism. Substitute your own delivery rates from finance, because they are the only ones that matter.

Assume a month with 1,000 orders at an average basket of SAR 400, against SAR 80,000 of media spend.

Reported return on ad spend is 400,000 divided by 80,000, which is 5.0. Delivered return is 311,200 divided by 80,000, which is 3.9. The dashboard is overstating performance by about 28 per cent against money actually received.

The more interesting number is per segment. Both segments produced roughly SAR 155,000 of delivered revenue, but the cash segment needed 600 orders to get there against the card segment's 400. If your cost per order is similar across both, the cash segment is costing you around half as much again per riyal of real revenue, and your fulfilment team is handling 50 per cent more parcels for the same money.

That is the argument for splitting them. Some practical moves that follow from it:

• Fire the checkout event as normal so the funnel stays visible in reporting
• Send a distinct event when the order is delivered and paid. Use it for bidding when volume and conversion delay support that choice; keep the checkout event out of the same bidding goal to avoid counting one sale twice
• Report delivered revenue alongside reported revenue, with the gap shown explicitly
• Consider a prepayment incentive and measure it against the delivery-failure cost rather than against the discount
• Look at whether the delivery-failure rate differs by campaign, creative or city, because that is where the actionable variation usually sits

Google documents the mechanism in its guidance on importing offline conversions, and Meta covers the equivalent through its Conversions API, which handles web, app and offline events. Both take engineering time to set up, and both need a data source that knows when an order was actually paid.

Payment infrastructure varies by country too. Saudi Arabia has a domestic card scheme and a growing buy now, pay later sector, both supervised by the Saudi Central Bank. Check which methods your checkout actually supports on a local card before you spend on traffic to it.

Arabic Is Written, Not Translated

Running English creative into Saudi Arabia because English is widely understood is a decision worth testing rather than assuming. The UAE has a large expatriate population and English often performs well in particular segments. Saudi Arabia has a different composition.

Points that repeatedly cause trouble:

• Right to left layout. Landing pages, forms and checkout need proper direction handling. Test the whole path including error states and the payment step, not just the homepage.
• Dialect versus Modern Standard Arabic. Formal written Arabic reads as institutional, Gulf dialect reads as familiar. Which one suits depends on category and audience. Test it rather than deciding in a meeting.
• Product feeds. Titles, descriptions and attributes need the same treatment as the ads. A feed left in English limits which queries you can match.
• Machine translation. Native speakers can tell, and in categories where trust drives conversion that matters more than the translation cost saved.

Build the Calendar Around Ramadan

The commercial year in the Gulf does not follow the Western retail calendar. Ramadan and the Eid period that follows change the shape of demand, the hours people are awake and shopping, and the tone creative can credibly take.

Ramadan moves through the Gregorian calendar by roughly eleven days each year. For 2027 it is expected to begin in February, though the start depends on the sighting of the moon and is confirmed locally. Plan against the approximate window and confirm closer to the time.

A simple planning frame:

There are also regional discount events in November marketed under local names rather than Black Friday. Put them in the plan explicitly.

A Setup Checklist Before You Spend

1. Confirm with local counsel which regime applies to the entity collecting the data
2. Write channel-specific consent copy, log consent with a timestamp, and test the opt-out
3. Separate Saudi and UAE campaigns so you can read them independently
4. Get the delivered-and-paid figure out of finance and run the table above on your own numbers
5. Add a delivered conversion event and move bidding onto it
6. Reconcile platform revenue against finance monthly and track the gap
7. Commission Arabic copy as original writing, and localise the product feed
8. Test the checkout end to end on a local card
9. Build the media calendar around the Islamic calendar and confirm dates locally

This is ordinary groundwork. It is also the difference between a Gulf launch that reads as considered and one that reads as a copy of another market.

Sources

• Saudi Data and Artificial Intelligence Authority, Regulations and Policies
• SDAIA, Implementing Regulation of the Personal Data Protection Law (PDF)
• UAE Government Portal, Data protection laws
• Saudi Central Bank
• Google Ads Help, About offline conversion imports
• Meta Business SDK for Node.js, Conversions API reference