You can now see, in Google Analytics, how many travellers reach your hotel website from ChatGPT, Gemini or Claude. Since 13 May 2026, GA4 sorts that ChatGPT traffic into its own channel, with no setup required. Checking it takes about five minutes.
It's worth the five minutes. At Hotel Harmony in Ghent, a full week of Google Analytics taken a few weeks after its website was rebuilt showed more than one visit in ten arriving through an AI assistant. Only organic search and direct sent more. One hotel and one week is not a benchmark for the industry, but it shows the number can be big enough to matter.
By the end of this guide you'll know how many visits AI assistants send your website, how that compares with your other channels, and why the real number is probably higher.
Running your website on AskWhisper? GA4 tells you how many travellers AI assistants send you. The AI search visibility dashboard in the AskWhisper platform shows the other half: whether those assistants recommend your hotel at all. Every week it asks them the questions travellers ask, shows which hotels they name instead, and flags answers that get a fact about your hotel wrong, with suggestions for your website.
What you need before you start
- Access to your hotel's Google Analytics 4 property. Viewer access is enough to read the reports.
- GA4 installed on your website, not just on your booking engine.
- Ideally, booking engine clicks tracked as a key event, so you can see whether AI visitors go on to book. If you don't have that, you can still do steps 1 to 3.
Step 1: Open the traffic acquisition report
In GA4, go to Reports, then Acquisition, then Traffic acquisition. Set the date range to start after 13 May 2026, when the new channel arrived. The last 28 days is a good first look.
This report shows where your website sessions come from, grouped into channels such as Organic Search, Direct, Referral and Paid Search.
Step 2: Find the AI Assistant row
Check that the table is grouped by Session default channel group, which is the default. Then look for the AI Assistant row.
Google announced the channel on 13 May 2026. When GA4 recognises a visit as coming from an AI assistant, it sets the medium to "ai-assistant", the campaign to "(ai-assistant)" and puts the session in the AI Assistant channel. Google names ChatGPT, Gemini and Claude as examples, but hasn't published the full list of assistants it recognises.
Compare the AI Assistant row with Organic Search, Direct and Referral. The share of sessions matters more than the raw count: 40 visits means little on its own, but 40 out of 400 is the one-in-ten Hotel Harmony saw.
If AI Assistant is in your top five channels, travellers are already asking chatbots about your hotel.
Step 3: Look back before May with the source dimension
Before 13 May, traffic from AI chatbots landed in the Referral channel. To see the months before the new channel arrived, change the primary dimension to Session source and search the table for the domains of the main assistants:
- chatgpt.com
- gemini.google.com
- claude.ai
- perplexity.ai
- copilot.microsoft.com
That gives you a rough trend: whether AI traffic was already growing before Google gave it a name. The list is a starting point for your search, not Google's list of the assistants it recognises.
Step 4: Check what AI visitors do next
Traffic only matters if it books. Add your booking engine click to the report, as a key event, and compare the AI Assistant row with your other channels: engagement rate, key events, and key event rate.
A traveller who arrives from ChatGPT has often already asked their question and been sent to you on purpose. Whether they go on to book depends on what they find when they land: the price, the room, the answer to the question the chatbot couldn't fully give.
The number to watch is how many AI visitors reach your booking engine.
Why the number you see is a floor
The AI Assistant channel only counts visits GA4 can recognise from the referrer, the address a browser passes along when someone clicks a link. As Search Engine Journal notes, GA4 can only place a visit in the channel when it can identify the assistant from the referrer. Some apps and browsers don't send one, and those visits fall into Direct instead.
Three other things keep the number low:
- Copy-paste visits. A traveller who reads your hotel's name in a chatbot answer and then types it into Google shows up as Organic Search, not AI.
- Unlisted assistants. Google hasn't published which assistants it recognises, so traffic from a smaller one may still sit in Referral.
- Mobile apps. Links opened from inside a chatbot's app don't always pass a referrer.
So whatever share you see in the AI Assistant row, the real influence of AI assistants on your bookings is larger.
Read the AI Assistant row as the minimum, never the total.
What to do with the number
| What you see | What it means | What to do |
|---|---|---|
| No AI Assistant row at all | AI assistants aren't recommending your website, or none of those visits sent a referrer | Read why hotels don't show up in AI search and fix the basics first |
| A small share, under 2% | You're being mentioned, but rarely | Make sure your website answers the questions travellers ask, in text, on the pages chatbots link to |
| A share like Hotel Harmony's, one in ten | AI assistants are a real channel for you | Track it monthly, and check that AI visitors reach your booking engine as often as organic visitors do |
Whatever your number, check it again next month. The channel is new, the assistants are changing fast, and a trend over three months tells you more than one snapshot.
Where AskWhisper fits
On AskWhisper, every hotel website reads from the same brain as the webchat, the WhatsApp flows and the email replies, with every room, policy and answer written out in text that travellers and AI assistants can both read. Hotel Harmony's rebuilt site is one of them.
GA4 counts the visits. The AI search visibility dashboard, built into the AskWhisper platform, shows what comes before them. Every week it asks AI assistants a set of traveller questions, twice each because answers vary, from "where to stay in Ghent for a weekend" to questions that name your hotel, in the languages your travellers use. You see which questions recommend you, which hotels get named instead, and where an answer gets a fact wrong, like the walking distance to a landmark. Each finding comes with a suggestion for your website, in the same place you run it.
If your AI Assistant row is empty, our breakdown of what a hotel website actually costs and our guide to replacing it without losing Google rankings are the next two reads. The website is also where the seven handoffs where hotels lose revenue begin.
Checked your AI Assistant row and didn't like what you saw? See how AskWhisper works, or start with why hotels don't show up in AI search.
Turn lookers into bookers. Just Ask Whisper.
