Which ads drive your delivery-app orders.
Most of a Saudi restaurant's revenue arrives through HungerStation, Jahez and Mrsool, where ad platforms cannot see the sale. MIQAS closes that gap and shows the real return on every campaign.
Why restaurant ROAS always looks wrong
A customer sees your ad on Snapchat, then orders through a delivery app. The sale is real, but the pixel never fires: the conversion happened inside someone else's platform. Your dashboards call the campaign a failure while the kitchen gets busier.
Judged only on website orders, ad performance for F&B is systematically understated, and the campaigns that actually fill orders are often the ones that get cut.
How MIQAS reconciles it
Weekly exports from the HungerStation, Jahez and Mrsool merchant portals are uploaded to MIQAS, normalized, and placed on the same timeline as your ad spend.
One view shows how revenue divides between your own channels and the delivery apps, and how that mix shifts when campaigns run.
Aggregator order volume is read against each campaign's flight dates and spend, so you see which ads move total orders, not just website ones.
Foodics and other POS connections plus your website and app orders complete the picture, in SAR, in Arabic or English.
Decisions this unlocks
- Keep or cut a campaign based on total order lift, including delivery apps.
- Price the real cost per order when commissions and ad spend are counted together.
- See whether promotions shift customers from commission-heavy apps to direct channels.
- Report one trusted revenue number to owners and partners.
Stop judging ads on half the revenue.
Aggregator reconciliation is included from the Growth plan. Connect your channels and upload your first export the same day.