How GA4 Classifies AI Traffic for Arab Websites: What Saudi, UAE and Egyptian Sites Lose (2026 Study)

GA4 counts only a thin slice of AI traffic to Arab websites. Its AI Assistant channel, live since 13 May 2026, catches recognised chatbot referrers, yet Google files AI Overviews and AI Mode under Organic Search. For one Saudi client, 96.9% of measured AI citations came from those two Google surfaces. Up to 5.29% of Saudi chatbot referrals (StatCounter, September 2026) come from assistants Google’s channel page does not name.

Key takeaways

• The AI Assistant channel matches on referrer only. Google names ChatGPT, Gemini, DeepSeek, Copilot and Grok on its channel page, and states that AI Overviews and AI Mode stay in Organic Search.
• Perplexity and Claude sent 1.08% (Bahrain) to 5.29% (Saudi Arabia) of AI chatbot referrals in nine Arab markets in September 2026, per StatCounter. Those clicks are at risk of landing in Referral.
• Google’s source category list has no Gulf marketplace: amazon.sa, amazon.ae, noon.com, namshi.com and haraj.com.sa are all absent, so their untagged clicks fall to Referral.
• HUMAIN Chat (Saudi Arabia) and Fanar (Qatar) are not named by Google either.
• Treat the AI Assistant number as a floor. Read it next to Organic Search, Direct and Referral.

Where does each AI surface land in GA4 for an Arab site?

Each AI surface lands in one of four GA4 channels, decided by what reaches your tag. Recognised chatbot referrers go to AI Assistant. Google’s own AI Overviews and AI Mode go to Organic Search. Assistants Google does not recognise go to Referral. Any click that arrives with no referrer, such as a link pasted into WhatsApp, goes to Direct.

The table maps the surfaces Arab users actually meet. Channel rules come from Google’s Default channel group definitions, which we read on 2 October 2026. Where Google has not published the rule, the row says so.

What did Google change on 13 May 2026?

On 13 May 2026 Google Analytics added a default AI Assistant channel. When a session’s referrer matches Google’s list of AI assistants, GA4 sets the medium to “ai-assistant” and the campaign to “(ai-assistant)”. The change works forward only. Sessions before the rollout stay in Referral or Direct, and the full referrer list is unpublished.

Google’s Analytics release notes date the launch to 13 May 2026 and give ChatGPT, Gemini and Claude as examples. Search Engine Journal reported it on 14 May 2026 and noted that Google had not published the recognised list.

The channel definition page we read on 2 October 2026 names a different set: ChatGPT, Gemini, DeepSeek, Copilot and Grok. Claude, named in May, is missing from that sentence. Perplexity appears in neither. Google writes “sources like”, so a missing name does not prove an assistant is unrecognised. It does mean nobody outside Google can confirm coverage without testing a live property.

Two more facts shape every Arab GA4 report. Default channel groups cannot be edited. And the downloadable GA4 source category list contains no AI assistant hostname at all. We searched its 819 entries on 2 October 2026 for chatgpt, openai, perplexity, claude, gemini, copilot, deepseek, grok, humain and fanar. None appear.

How much Arab AI referral traffic falls outside Google’s named assistants?

Between 1.08% and 5.29% of AI chatbot referrals in nine Arab markets came from Perplexity and Claude in September 2026, per StatCounter. Saudi Arabia is highest at 5.29% and Bahrain lowest at 1.08%. Every Arab market sits below the worldwide figure of 6.80%, because Perplexity is weaker in the region than globally.

We read each StatCounter AI chatbot market share country page on 2 October 2026. StatCounter shows the top five assistants and measures referral clicks to sites running its tracker, not chatbot usage. The “at risk” column adds Perplexity and Claude, the two top-five assistants absent from Google’s channel definition. The last column keeps only Perplexity, which Google has named nowhere.

Keep the scale in view. AI chatbots sent 0.41% of tracked search, social and chatbot referrals in Saudi Arabia in September 2026, against 82.45% from search, per StatCounter. The misfiled chatbot slice is small. The search slice, which now carries Google’s AI answers, is not. Our Gulf AI assistant referral study tracks how these shares moved since 2025.

Why do ChatGPT clicks from Gulf phones end up in Direct?

ChatGPT clicks end up in Direct when no referrer reaches your tag. That happens when a user copies an answer’s link into WhatsApp, opens it inside an in-app browser, or taps it in a mobile app that strips the header. GA4 then sees source “(direct)” and medium “(none)”, which matches its Direct rule exactly.

Mobile dominates Gulf browsing. Phones carried 68.27% of web traffic in Saudi Arabia, 60.04% in the UAE and 63.74% in Egypt in September 2026, per StatCounter platform data. We found no reliable statistic on how often Gulf users pass AI answers along through WhatsApp. GA4 lists whatsapp.com as a social source, so a click that does carry a WhatsApp referrer goes to Organic Social. A pasted link opened from the app usually carries none.

The web referrer is thinner than most guides assume. On 2 October 2026 we asked three assistants in desktop Chrome to find a VOCTOS article, then inspected the links in each answer before clicking. chatgpt.com serves a referrer meta tag set to “origin” and a Referrer-Policy header of strict-origin-when-cross-origin. More important, the two links in its answer carried rel=”noopener noreferrer”, which tells the browser to send no referrer at all.

One answer per assistant is a spot check, not a rate. We inspected the links rather than counting sessions, and we did not test mobile apps. Still, the ChatGPT result matters: in the answer we checked, a click from ChatGPT on the web would reach GA4 as Direct, so the AI Assistant channel would never see it. Some ChatGPT links seen in the wild carry utm_source=chatgpt.com instead, which creates a second case.

The UTM case is unresolved. Google’s URL-builder guidance says missing UTM parameters report as “(not set)”. If the UTM value wins over the referrer, the session reads chatgpt.com / (not set), which matches no default rule and becomes Unassigned. Google does not document which wins. Step 5 of the protocol below tests it on your property.

Which Gulf marketplaces are missing from GA4’s source categories?

None of the major Gulf marketplaces appears in GA4’s source category list. On 2 October 2026 we searched all 819 entries: amazon.sa, amazon.ae, amazon.eg, noon.com, namshi.com, salla.sa, zid.sa and haraj.com.sa are absent. The list carries amazon, amazon.com and amazon.co.uk only. Untagged clicks from Gulf marketplaces therefore fall to Referral, not Organic Shopping.

Two entries look regional but are not. “ar.search.yahoo.com” and “ar.pinterest.com” are Argentina subdomains, not Arabic ones. The fix is cheap: tag every link you control on a marketplace storefront with UTM parameters, and add a marketplace rule to your custom channel group for the rest.

Want a second pair of eyes on how your property files AI and marketplace visits? Ask VOCTOS to review your GA4 channel setup.

The Saudi proof: 96.9% of measured AI citations sit inside Organic Search

For one Saudi client, 5,400 of 5,570 measured AI citations in July 2026 came from Google AI Overviews and AI Mode. That is 96.9%, and GA4 files clicks from both surfaces under Organic Search. Only 170 citations, or 3.1%, came from ChatGPT and Gemini, the surfaces the AI Assistant channel can see.

The client is Delta Medical Labs, a Saudi medical laboratory that VOCTOS has worked with since March 2026. Its published July 2026 breakdown is 3,600 AI Overviews citations, 1,800 AI Mode, 130 ChatGPT and 40 Gemini. These are citations counted by tracking tools, not sessions. A citation does not guarantee a click, and the case study does not report click counts per surface.

The ratio still tells a Saudi marketing lead where to look. If a GA4 report shows a small AI Assistant row and the team concludes AI barely matters, it has read 3.1% of the citation picture. The other 96.9% is mixed into Organic Search, where GA4 cannot separate it from blue links.

Search Console is the only Google tool that isolates those surfaces. Google announced generative AI performance reports on 3 June 2026, and rolled them out to all sites on 31 August 2026. They show impressions by page, country and date, with no clicks, so they cannot be joined to GA4 sessions. Our guide to Google AI Overviews optimisation covers what earns those citations.

An 8-step reporting protocol for Arab GA4 properties

The protocol below keeps AI reporting honest for a Saudi, Emirati or Egyptian site. It date-stamps Google’s definitions, adds the regional assistants and marketplaces Google leaves out, tests the ChatGPT UTM case, and reads Direct by landing page. Each step works in a standard GA4 property without paid tools or developer time.

1. Date-stamp the definition. On reporting day, open Google’s Default channel group page and copy the AI Assistant sentence into the report. Google has changed the named assistants once since May.
2. Annotate 13 May 2026. Add the launch date, plus the date your AI Assistant row first filled, to every chart spanning it. Referral drops at that point for definitional reasons.
3. Build a custom channel group. GA4 allows two. Create “AI, Arab markets” with: Default channel group exactly matches “AI Assistant” OR Source matches regex .*(chatgpt|openai|perplexity|claude|gemini\.google|copilot\.microsoft|deepseek|grok|humain|fanar).*. Place it above Referral and Organic Search. Google says custom channel groups apply retroactively, so the regex also catches pre-May sessions.
4. Add a Gulf marketplace channel. In the same group, add Source matches regex .*(amazon\.(sa|ae|eg)|noon\.com|namshi\.com|salla\.sa|zid\.sa|haraj\.com\.sa).*, above Referral.
5. Test the ChatGPT UTM case. In Explore, filter Session source = chatgpt.com and break down by medium. Rows in (not set) or Unassigned mean the UTM overrode the AI rule.
6. Read Direct by landing page. Pull Direct sessions for deep pages nobody types, such as long percent-encoded Arabic slugs. Compare with the same period before May 2026 and split by mobile and desktop.
7. Put Search Console next to Organic Search. Filter the generative AI report to Saudi Arabia, the UAE or Egypt and report AI Overviews and AI Mode impressions beside Organic sessions. Do not join them.
8. Report a floor and three residuals. Label AI Assistant as a floor. Show Referral (unnamed assistants), Direct (stripped referrers) and Organic Search (Google AI) beside it, plus citation counts from your tracking tool.

What the evidence supports, and how confident we are

The evidence firmly supports the channel mechanics: AI Assistant matches referrers only, Google’s AI surfaces stay in Organic Search, and Gulf marketplaces are absent from the source list. It supports the StatCounter shares at medium confidence. It does not support any estimate of how many Arab AI clicks GA4 files as Direct.

One more limit applies. The Delta Medical Labs ratio describes one Saudi healthcare site in one month. A retailer or a B2B software firm in Dubai will see a different mix.

Our read

Our position is that Arab marketing teams are watching the wrong AI row. The AI Assistant channel is useful, yet for Arabic content the larger exposure sits inside Organic Search, where Google’s AI answers live. A report that shows only the native AI channel understates AI’s role and overstates classic organic performance in the same breath.

We would not spend a sprint chasing the Perplexity and Claude slice. At 1.08% to 5.29% of chatbot referrals, which are themselves 0.41% of Saudi referral traffic, it is a rounding issue for most budgets. Add the regex, then move on.

The Gulf-specific gap deserves more attention than it gets. GA4’s source categories were not built with amazon.sa, noon.com or HUMAIN in mind, and that will not change by default. Any channel report for a Gulf retailer that has not added these by hand is mixing marketplace demand into Referral.

Finally, stop judging AI visibility by sessions alone. Track citations by surface, read Search Console impressions next to Organic sessions, and accept that some value will never show up as a click. Our analysis of the Saudi Internet Report 2025 AI findings shows how widely Saudis already use these tools.

FAQ

Why does my GA4 AI Assistant channel show almost nothing for my Saudi site?

Because it only counts recognised chatbot referrers. Google’s AI Overviews and AI Mode, which carry Google’s AI answers for Arabic searchers, report as Organic Search. Clicks pasted into WhatsApp or opened in app browsers arrive as Direct. For one Saudi lab, 96.9% of measured AI citations in July 2026 came from Google surfaces the channel cannot see.

Does GA4 recognise HUMAIN Chat or Perplexity as AI assistants?

Google does not say. Its channel page, read on 2 October 2026, names ChatGPT, Gemini, DeepSeek, Copilot and Grok, and the referrer list is unpublished. HUMAIN Chat, Fanar and Perplexity appear nowhere in Google’s documentation, so treat their clicks as Referral and add a custom channel group regex to catch them.

Can I see AI Overviews traffic separately in GA4?

No. GA4 files AI Overviews and AI Mode clicks under Organic Search, with no separate dimension. Search Console’s generative AI report, available to all sites since 31 August 2026, shows impressions by page and country but no clicks. Report those impressions beside Organic sessions, and do not attempt to join the two datasets.

Why are noon and amazon.sa referrals counted as Referral, not Shopping?

GA4’s Organic Shopping channel matches a fixed list of shopping sources, and that list contains amazon, amazon.com and amazon.co.uk but no Gulf marketplace. Untagged clicks from noon.com, amazon.sa, amazon.ae or namshi.com fall to Referral. Tag your storefront links with UTM parameters, or add a marketplace rule to a custom channel group.

Will GA4 move my old ChatGPT referral traffic into AI Assistant?

No. The AI Assistant channel launched on 13 May 2026 and classifies sessions forward only. Earlier ChatGPT visits stay in Referral or Direct, so Referral will look weaker after May for definitional reasons. Annotate the launch date on every chart and use a custom channel group, which Google says applies retroactively.

What should an Arab marketing team do next?

The useful question is not how much AI traffic GA4 shows, but where GA4 is putting the AI traffic it cannot name. For most Saudi, Emirati and Egyptian sites, the answer is Organic Search first, Direct second and Referral third. The native channel is a floor.

If your GA4 property already has a custom channel group and Search Console access, run the 8-step protocol this month and add the Gulf marketplace and regional assistant rules. If it does not, fix the basics first: confirm Search Console is verified for the right domain, tag your marketplace and campaign links, then build the custom group.

If you would rather have a team map your AI citations and fix the reporting at the same time, see how VOCTOS runs AI search optimisation for Arab brands.

Sources

• Google Analytics Help, Default channel group (read 2 Oct 2026): support.google.com/analytics/answer/9756891
• Google, GA4 source categories list (searched 2 Oct 2026): storage.googleapis.com
• Google Analytics release notes, 13 May 2026: support.google.com/analytics/answer/9164320
• Google Analytics Help, URL builders and UTM parameters: support.google.com/analytics/answer/10917952
• StatCounter, AI chatbot market share by country, September 2026: gs.statcounter.com/ai-chatbot-market-share
• Google MENA blog, AI Overviews in MENA and in Arabic, 20 May 2025: blog.google
• Arab News, AI Mode expands to Arabic, 8 Oct 2025: arabnews.com
• Saudi Press Agency, HUMAIN Chat launch, 25 Aug 2025: spa.gov.sa