Google Analytics now labels AI traffic. Most of it still hides.

A new row showed up in your dashboard on Tuesday

Google fixed half of the AI traffic problem on Tuesday. On May 13, Google Analytics added a row called AI Assistant to the Default Channel Group, the labeled list of buckets on your Acquisition report. Visits from ChatGPT, Gemini, and Claude now land in their own row instead of getting buried in Referral or Direct. No setup. No filter rules. The row just shows up the next time you open your dashboard.

This is good news for any service business owner who has been trying to see AI traffic separately. The catch is the row only shows about a third of the AI traffic actually coming to your site. The other two thirds still hide in Direct. Google just automated the easy part. The hard part, the seventy percent that arrives without any way to tag it, is still hard.

What the new row actually does

Before Tuesday, AI traffic landed in one of two places. If your visitor clicked a link in a desktop browser, the visit carried a referrer tag (the tag that tells your dashboard the visit came from ChatGPT instead of looking like a random visitor). Google dropped those into the Referral bucket alongside any link from any other site. To pull AI traffic out of that bucket, you had to build a custom channel group with filter rules. Google Analytics caps you at two custom groups, so picking the AI rule cost you a slot.

The new default channel does that work for you. When Google sees a referrer it recognizes from a known AI tool, it sets the medium tag (the label under each visit in the report) to ai-assistant and groups the visit under AI Assistant in your channel list. No admin work. You can drop your custom filters this week.

What the row does not do is invent referrer data where none exists. If a visit arrives without a tag, the row does not see it, no matter where it came from. Google has only named three tools so far in the help-center notice: ChatGPT, Gemini, and Claude. Search Engine Journal reported on May 14 that Google did not publish the full list of recognized tools. So you should treat the row as the minimum amount of AI traffic Google can confirm, with more arriving from tools Google has not added yet.

Where do I find the new AI Assistant row in Google Analytics?

Open Google Analytics. Click Reports on the left, then Acquisition, then Traffic acquisition. The table groups visits by Default Channel Group. Look for the row called AI Assistant. If you have visits from ChatGPT, Gemini, or Claude with a referrer attached, the row shows up. If no visits qualify yet, the row stays hidden until one arrives.

Which AI tools does the new channel cover?

Google has only named three so far. ChatGPT, Gemini, and Claude are listed in the help center entry. Perplexity, Copilot, and other tools are not confirmed in the auto-detect list. Treat the new row as the minimum amount of AI traffic Google can confirm, with more arriving from tools Google has not added yet.

Where the rest of the traffic hides

Loamly published a study in February that measured this. They looked at 446,405 visits across their tracked sites and found that 70.6 percent of AI-sourced visits arrived without a referrer tag. Those visits landed in Direct, the bucket Google uses for people who typed your URL in by hand. The full report is on Loamly's blog.

The reason is in the phone apps. When a user taps a link inside the ChatGPT phone app, Claude phone app, or Perplexity phone app, the in-app browser strips the referrer tag before passing the visit to your site. Google has no way to know that visit came from an AI tool. It looks the same as someone typing your domain into Safari. The copy-paste pattern works the same way. A user reads a ChatGPT answer, copies your URL out of the chat, and pastes it into a new browser tab. No tag. No way for Google to label it.

So the new AI Assistant row picks up the desktop browser clicks plus any phone clicks that did keep the tag. The Loamly data says that is about 30 percent of the real volume. The other 70 percent looks identical to your real Direct traffic in every report.

Why is most of my ChatGPT traffic still showing up as Direct?

The phone apps for ChatGPT, Claude, and Perplexity strip the referrer tag when they open a link in your browser. So does any link copied and pasted from a chat answer. Google labels the visit based on that tag. With no tag, Google has no way to know it came from an AI tool, so it lands in Direct alongside people who typed your URL into a browser.

Why the hidden visits matter more than the visible ones

The Loamly study had a second number that turns the gap into a real money question. The visits hiding in Direct booked at a 10.21 percent rate. The non-AI traffic in the same study booked at 2.46 percent. That is about a four times higher booking rate, on the visits you cannot see in the new row.

Here is why that gap matters for your revenue. Two AI visits in a week is worth more to your phone than fifteen Direct visits from people typing your URL. The hidden seventy percent is your highest-converting traffic source, and right now Google labels it the same as someone who typed your name into a browser. The new row gives you the visible third. The hidden two thirds still pay the bills.

This is why operators who only watch the new row will get the wrong story for the rest of the year. The row says zero AI traffic some weeks and the owner concludes AI is not happening yet. In reality the row misses seven of every ten AI visits, and those seven are the ones most likely to call the office. The fix is to read the new row next to the Direct row, not on its own.

Do I still need to set up a custom channel filter for AI traffic?

No. Before this week, you had to build a custom channel group using filter rules to separate AI visits from other referrals. Google Analytics caps you at two custom groups. The new default channel does that work for you without burning a slot. Any custom filters you built last year will still run, but you can retire them.

The five-minute weekend check

Here is the routine that fits inside one cup of coffee on a Saturday.

Open Google Analytics. Go to Reports, then Acquisition, then Traffic acquisition. Look at the channel list and find the AI Assistant row. Note the number of visits and the pages those visits landed on. Write the number on a sticky note for next week.

Then click the Direct row. Compare Direct visits over the last 30 days to the same 30 days one quarter ago. If Direct has gone up by 15 percent or more while Organic stayed flat, that climb is the most likely place your AI traffic is hiding. The pages getting the most Direct visits this quarter are the pages AI tools are most likely citing in chat answers.

Last step. Open ChatGPT in your browser. Type a real customer question for your category. "Best dentist near me for same-day crowns." "HVAC repair near me on a Sunday." See whether your business shows up. If it does, the Direct climb has an explanation. If it does not, the Direct climb is mostly bookmarks and brand searches, and your AI work still needs to start.

That is the whole routine. Five to ten minutes. Repeat next Saturday. Track the visible number on the sticky note over four weeks. If the row climbs while Direct stays flat or climbs in parallel, your AI presence is real and growing.

How do I tell if AI traffic is hiding in my Direct number?

Open the Acquisition report. Compare Direct visits over the last four weeks against the same four weeks one quarter ago. If Direct climbs while Organic stays flat, that gap is the most likely place your AI traffic is hiding. Most service businesses we audit see Direct climb 15 to 30 percent on flat Organic during this kind of shift.