The rule: match the conversation, not your brand guidelines
ChatGPT ads are matched to the topic of a conversation and targeted by language, among other things. That makes the language decision simpler than on Meta, where you guess who is scrolling. Here you know the language the person is already typing in. If they asked about villas in Arabian Ranches in English, the Sponsored placement should be in English. If they asked in Arabic about a school in Al Ain, answer in Arabic. The ad is text with a link, so there is no image to soften a language mismatch. The words are the whole creative.
This is why 'our brand is English' or 'our brand is Arabic' is the wrong starting point. Your brand can be either; the placement has to be the reader's. In practice a UAE campaign is two campaigns, one per language, each with its own topics, copy, landing page and WhatsApp greeting, and each judged on its own cost per tracked conversion. The old debate we covered for Kuwait in Arabic vs English ads still applies, but in the UAE the answer usually starts from a different default.
Why English goes first in the UAE
English is the working language of the UAE. Arabic is official, but the person in Dubai or Abu Dhabi asking ChatGPT about a car lease, a moving company, a Marina apartment or a weekend hotel is, more often than not, typing in English, whether they grew up in Kerala, Cairo, Manchester or Manila. Free-tier users, the only ones who see ads, lean towards personal use, and personal use across the UAE's many nationalities defaults to English as the shared language. That is the widest pool, so it is where a first test belongs.
English-first also means English done properly, not translated Arabic and not American ad-speak. UAE English has its own texture: 'villa', 'community', 'chiller-free', 'DEWA', 'Salik', 'freehold', 'off-plan', 'Golden Visa'. A Sponsored placement that uses the words a Dubai resident uses reads as local; one that does not reads as an import. Because creative is text-first, that difference is the entire ad. We write UAE English natively, the same way we write Gulf Arabic natively, and we test two or three angles per topic before we scale one.
When Arabic wins
Arabic wins when the buyer is Emirati or Gulf-national, and that is a valuable buyer: family villas in Abu Dhabi, majlis furniture, wedding services, private schools with an Arabic curriculum, Ramadan and Eid gifting, luxury cars, and property bought as a family rather than as an investor. It also wins with Saudi and Kuwaiti visitors researching Dubai before a trip, and with the large Arabic-speaking expat population from the Levant and North Africa, who search in Arabic at home even when they work in English. These conversations are less crowded, because most advertisers will default to English.
When Arabic wins, it has to be the right Arabic. Gulf register, the way a client in Abu Dhabi would phrase the question, not stiff MSA and not an Egyptian or Levantine voice bolted onto a Dubai offer. Brand names stay in Latin script. A Ramadan campaign in Arabic should sound like Ramadan in the Gulf, not a translation of a Western holiday ad. The Kuwait customer AI-search behaviour piece shows how Gulf buyers phrase things; the UAE version of that behaviour is similar in Arabic and different in English.
Language parity: ad, landing page, WhatsApp
The most common way a bilingual campaign fails is a broken chain. An Arabic Sponsored placement sends someone to an English landing page, or an English page hands off to a WhatsApp greeting in Arabic, or the agent who replies only speaks one of the two. Each break costs a share of the people who tapped, and because the pixel records the drop as a non-conversion, you end up blaming the channel for a page problem. Parity is the rule: the ad, the page and the first WhatsApp reply in the same language, every time.
For an Arabic campaign that means a real Arabic landing page, right-to-left, with prices in AED and the same offer, not a machine translation hidden behind a language toggle. For WhatsApp it means the Business API flow detects which ad the person came from and greets them in that language, then routes to an agent who can hold the conversation. This is the part of the setup that most Dubai agencies skip and the part that decides whether Arabic ads convert. The landing page and CRO work is not optional here.
Running both without doubling the work
Start with English on the topics with the most conversations, prove the conversion path with the OpenAI pixel and server-side tracking, then add Arabic on the topics where Emirati and Gulf-national buyers concentrate. Do not launch both on day one with a split budget; you learn less from two half-tests than from one full one. Once English has a cost per tracked lead you trust, Arabic gets its own test with its own stop-loss, and the two are compared on outcomes, not on clicks.
Rollout is staged by country and by plan, and GCC availability changes, so whether your UAE business can buy today, join a waitlist, or should prepare and wait is a WhatsApp question; we check the current status before anything is spent. Send us your website, what you sell, and who buys it, Emirati families, expat professionals, visitors, or all three. We tell you which language to launch in, what the landing pages need in each, and how the WhatsApp flow greets both. Aahfil is bilingual by design, so both versions are written natively, not translated.