You open Google Analytics, see direct traffic sitting near the top, and wonder how much of it is a person who asked an AI assistant a question and clicked through to your site. Gemini traffic in Google Analytics has been hard to pick out, because a visit that arrives with no referrer gets filed as direct and nothing says where it came from. Site owners have now spotted links from Gemini that carry a utm_source=gemini tag, which gives GA4 something to read. That does not mean every visit gets labeled, and it does not mean the number is large. It does mean you can open one report today and see whether any Gemini visits show up, which pages they land on and whether those visitors do anything useful. The check takes about ten minutes, costs nothing and leaves you with a view you can reopen every month.
Key Takeaways
Open Traffic acquisition, switch the primary dimension to Session source / medium and look for gemini. A tagged visit can show up there instead of hiding in direct.
Links from Gemini have been seen with utm_source=gemini. Read what your own landing URLs show before assuming any other value.
One or two conversions tell you which pages deserve a look. They do not give you a conversion rate to plan around.
How do I see Gemini traffic in Google Analytics 4?
You can do this in about ten minutes with the account you already have. Everything below sits in the standard reports, so there is nothing to install and nothing to buy.
- Open GA4 and go to Reports, then Acquisition, then Traffic acquisition.
- Set the date range to the last 28 days.
- Change the primary dimension from the default channel group to Session source / medium.
- Search the table for `gemini`, `gemini.google.com` and `ai-assistant`. Then try `chatgpt`, `perplexity`, `copilot` and `claude`.
- Add the columns for Landing page + query string, Engaged sessions, Engagement rate and Key events. If you sell online, add revenue too.
- Write down each source value you find, the pages those visitors entered on, and whether they did anything on the site.
- Save the report so you can reopen the same view next month.
Google's own help page for the Traffic acquisition report describes these session-level reports, and its page on the scopes of traffic-source dimensions explains why Session source and Session medium describe the visit that started on your site.
If the table shows nothing for Gemini, that is a result you can use. It means no tagged Gemini visit reached you in that window, and it is worth repeating the check next month rather than assuming the answer stays the same.
What did Gemini change, and what does it mean for my reporting?
Site owners noticed that links from Gemini now carry `utm_source=gemini`, and the first public mention was around September 28, 2026 in a Reddit thread on r/SEO. Google's John Mueller replied in that thread, "Nice. I see it too," and Search Engine Journal reported the change on October 1, 2026.
For your reporting, that has one practical effect. A UTM tag travels with the link, so a visit that would have been filed as direct can now arrive with a source of gemini. Treat `utm_source=gemini` as the only value you can rely on today. Look at the landing URLs in your own data, and let those tell you whether a medium or campaign value is attached, rather than guessing at one.
The tag may not appear the same way on every surface. Desktop web, the Gemini mobile app and Android assistant handoffs can behave differently, so a month with a few tagged visits and a month with none can both be normal.
Why do some Gemini visits still show up as direct?
A tag only helps when it survives the trip. A visit is filed as direct when GA4 has no source to read, and several ordinary things strip the source before the page loads.
| What happened | What GA4 may show | What you can do |
|---|---|---|
| The visitor copied the link and pasted it elsewhere | Direct or another source | Nothing; note it as a limit on the count |
| An app handed the visitor to a browser without a referrer | Direct or unassigned | Compare with how customers say they found you |
| A privacy setting removed the referrer | Direct | Nothing; the tag may still be present |
| A redirect or link rewrite dropped the query string | Direct, with the tag lost | Test your redirects with a tagged link |
| A consent tool delayed GA4 until after the page changed | Missing or misattributed session | Test the page with consent given and declined |
A custom channel group cannot rebuild what never arrived. It can group the sources you can identify, but a visit with no source, no referrer and no tag stays unidentified. So, the useful move is to test the part you control: load one of your pages with `?utm_source=gemini` added to the address, click through your site's usual redirects, and watch whether the tag is still in the URL when the page settles.
If your numbers look broken rather than small, work through what to check when Google Analytics shows zero or wrong visitors before you read anything into the Gemini rows.
How do I group AI assistant visits into one report?
Google Analytics already has a place for this. Its May 13, 2026 update describes an AI Assistant channel, where a visit gets the medium `ai-assistant` when the referrer matches a recognized assistant and the campaign shows as `(ai-assistant)`. That classification works from the referrer, so it is separate from the UTM tag, and the two can overlap or differ on the same visit.
That is why the table in step 4 matters. Look at the source and medium rows, and also at the default channel group, and report what each one shows without merging them.
If you want your own grouping, Google's page on custom channel groups shows the route: Admin, then Data display, then Channel groups. Add a rule for the AI assistant sources you care about and place it above Referral, or the visits are claimed by the Referral rule first. Other assistants appear in different ways: ChatGPT links have been seen carrying `utm_source=chatgpt.com` in a SearchPilot reference sheet, while Perplexity and Copilot usually show up by their own domains when the referrer comes through.
For a sense of how the big assistants compare as senders of clicks, see the BrightEdge numbers on ChatGPT and AI referral traffic.
What should I look at each month, and how do I read small numbers?
Once the report is saved, the monthly job is short: open it, read it and write down three things. The point is to learn whether AI visitors reach useful pages and take useful actions, not to chase a bigger total. Gemini rows may be small for a while, so the reading matters more than the count. The four checks below cover each visit.
Which pages do they land on?
Sort by Landing page + query string and note the pages that appear most for Gemini and AI Assistant visits. Those are the pages an assistant sends people to, and they deserve to be clear, current and easy to act on. Check that each one has a visible way to call, book or buy.
Do they engage and convert?
Look at engaged sessions, engagement rate and key events for the same rows. A form submission, a booking or a purchase marked as a key event is worth far more than a session count. If key events are missing or not marked, fix that first, because a visit you cannot connect to an action tells you little.
How do I treat one or two conversions?
Treat them as direction. Note which page they came from and what the visitor did, and keep watching. Compare month to month only when there are enough sessions to make the comparison fair, and do not turn a handful of conversions into a rate you plan around.
What stays out of this report?
A person can see your name in a Gemini answer and never click. A crawler can fetch your pages without ever running GA4. Neither one is a session. Keep citations, crawler requests and human visits as separate things, and describe session source and medium as the start of one visit, not every influence on a customer. A visitor may come back later by direct, search or another route.
| Look at | Where | What it tells you |
|---|---|---|
| Sessions for gemini and ai-assistant | Traffic acquisition, Session source / medium | Whether tagged or recognized assistant visits arrived |
| Landing page + query string | Same report, added column | Which pages assistants send people to |
| Engaged sessions and engagement rate | Same report | Whether those visitors stayed and read |
| Key events and revenue | Same report | Whether they took an action that matters |
| Direct sessions | Same report | A rough marker of visits GA4 could not identify |
When does it make sense to pay someone for this?
Not for the basic check. You can read Session source / medium yourself, and nothing about Gemini requires a paid tool to see it. Do that first, for one or two months, so that anyone you hire starts from your real numbers.
Paid help starts to make sense when the setup itself is the problem: redirects or consent tools that strip query strings, key events that are missing or misconfigured, several domains or an online store, or a need to tie GA4 visits to leads in a CRM. Those are jobs for someone who can test and fix the plumbing. They can show you identifiable AI visits and the pages those visits reach. They cannot prove every AI-influenced customer, and they cannot promise future Gemini traffic.
Can you read your Gemini traffic?
Pick an answer to begin.
1. Where in GA4 do you look for tagged Gemini visits first?
2. Which parameter value can you rely on for Gemini today?
3. Your month shows two Gemini conversions. How should you read it?
Frequently Asked Questions About gemini traffic google analytics
Does Gemini add UTM tags to website links?
Links from Gemini have been seen carrying `utm_source=gemini`. Check the landing URLs in your own GA4 data before assuming any other parameter is attached.
Where do I see Gemini traffic in GA4?
Go to Reports, then Acquisition, then Traffic acquisition. Switch the primary dimension to Session source / medium and search for gemini and ai-assistant.
Will every Gemini visit appear as Gemini?
No. Referrers and query strings can be stripped by apps, copied links, redirects or privacy settings, and those visits may show as direct, referral or unassigned.
What is the AI Assistant channel in GA4?
It is a channel Google added in 2026 for visits whose referrer matches a recognized AI assistant. Those visits get the medium ai-assistant.
Can a custom channel group recover missing AI traffic?
No. It can group sources you can already identify, but it cannot supply a source that was never recorded.
How often should I review it?
Once a month is enough. Open the same saved report and note sessions, landing pages, engagement and key events.
Wrapping Up
Start with the ten-minute check: Traffic acquisition, Session source / medium, and a search for gemini and ai-assistant. Note the pages those visitors enter and whether they reach a key event. Keep in mind that a visit with no referrer and no tag still lands in direct, so a quiet month for Gemini is a result, not a failure.
Over a few months you build something more useful than a single number: a record of which pages AI assistants send people to, and whether those people act. That record tells you where to improve a page, where to fix tracking and when a paid review would help.
At Web Leveling, we work with small and medium businesses across the country and overseas on how their sites show up in AI answers and how to measure the visits that follow. If your redirects, consent setup or key events are getting in the way of this report, contact us about measuring AI traffic and we will look at your setup. You can also read how generative engine optimization fits with the rest of your search work.
Terms
Terms used in this post
Tap a term to see what it means.
UTM tag. A short label added to the end of a link's address, such as utm_source=gemini, that tells your analytics where a visit came from.
Session source / medium. A GA4 dimension that pairs where a visit started with the kind of link it came through.
Traffic acquisition. The GA4 report that groups sessions by how they arrived at your site.
AI Assistant channel. A GA4 channel for visits whose referrer matches a recognized AI assistant, with the medium ai-assistant.
Key event. An action in GA4, such as a form submission or purchase, that you mark as important.
Referrer. The page or app a visitor came from, passed to your site when the browser sends it.
