Google Gemini UTM parameters

Gemini is Google’s assistant, but don’t let the Google name fool you into expecting Google Ads-style tracking. There’s no console, no click ID, no macro substitution — and none of it is necessary. Before anything else, separate two things people constantly conflate: Gemini the assistant versus AI Overviews inside Search. They behave completely differently for attribution.

Gemini as a traffic source

Gemini, at gemini.google.com, can browse and reference web pages. When a user clicks through to one of those references they land on your site as a real visitor.

The link Gemini shows is your canonical URL — not a rewritten tracking link. That’s why there’s nothing to configure, and why tagging is counterproductive.

How its traffic appears in analytics

Automatically, and in the right place.

GA4 ships a native AI Assistants default channel. Google’s documented rule is that the medium “is set to ai-assistant and the campaign is set to (ai-assistant) if the referrer matches a list of AI Assistants” — and Gemini is one of the sources Google names, alongside ChatGPT, Copilot, Grok, and Deepseek. So ai-assistant is a value GA4 writes once it recognizes the referrer, not something you supply.

AnyTrack does the equivalent, assigning every session a channel from the referrer and URL parameters, with conversions attached in the Campaign Report.

Clicks that arrive with no referrer land in (direct)/(none) and are unrecoverable — see limitations below.

Why you shouldn’t apply a UTM convention here

The common advice — tag “links you control that Gemini may surface” with utm_source=gemini&utm_medium=ai-assistant — doesn’t survive inspection.

Gemini surfaces your canonical URL. The only way to get parameters onto it is to publish your canonical URL with them attached, which means every visitor from organic search, email, referrals, and bookmarks lands on the tagged link and reports as Gemini traffic. On top of that, UTMs take precedence over referrer detection in GA4, so you’d overwrite a classification that was already correct — and ai-assistant is GA4’s own output, so writing it by hand asserts a referrer match that never happened.

For how the receiving end classifies all this, see Google Analytics .

Limitations and gotchas

• No click ID, no macros. Gemini has no gclid equivalent and no click-time substitution. That’s a Google Ads capability, not a Gemini one — and classification doesn’t need it.
• AI Overviews can’t be measured as Gemini. Overview clicks are organic search with no separate referrer. Don’t force them into a gemini source; use Search Console to understand visibility there.
• You can’t tag a link the model writes. There’s no convention that injects parameters into a URL generated inside someone else’s product.
• Referrer-less clicks are a hard floor. They land in Direct and nothing recovers them. Report the AI channel as a known undercount.
• Server-side capture is the durability fix. It preserves sessions that did carry a referrer but would otherwise be lost to ad blockers, consent gates, and fast bounces.

Verification

1. Check the AI Assistants channel. In GA4, open Reports → Acquisition → Traffic acquisition by default channel group. AI Assistants should be a row with no configuration. Switch the dimension to Session source to confirm gemini.google.com inside it.
2. Keep Gemini and Search separate. Confirm you aren’t reading Organic Search growth as Gemini traffic, or vice versa — AI Overview clicks live in the former.
3. Confirm your canonical URLs are bare. Check the pages Gemini is most likely to surface for stray utm_ parameters.

Gemini needs no tracking parameter, and Google gives it none — the referrer already does the job. For the bigger picture, read how to track ChatGPT, Perplexity, and Gemini traffic, why AI search needs no convention of its own, and how GA4’s native AI Assistants channel works.