Skip to main
← All articles

How to track ChatGPT, Perplexity and Google AI Overviews traffic

Traffic from generative AI is exploding but stays misattributed in GA4. Here's how to identify it, measure it, and tie it to your e-commerce conversions.

· 6 min read · The Walityk Team

To track generative-AI traffic, you need to identify visitors arriving from domains like chat.openai.com, perplexity.ai, gemini.google.com or copilot.microsoft.com, group them into a dedicated channel, then tie them to your conversions with server-side tracking. Otherwise, these visits drown in “Direct” or “Referral” and their impact stays invisible.

Why this traffic is mismeasured

When someone clicks a link inside a ChatGPT or Perplexity answer, several issues arise:

  • No reliable referrer: some AI answers open links without passing the referrer → the visitor lands as “Direct”.
  • No dedicated channel: GA4 has no native “generative AI” channel. ChatGPT often lands in “Referral” or “Unassigned”.
  • Short, cookieless sessions: these visitors often decline or bypass cookies → client-side loses their journey.

The result: a fast-growing channel that your analytics files in the wrong place, or not at all.

The domains to watch

Here are the main generative-AI traffic sources to recognize:

  • ChatGPT: chat.openai.com, chatgpt.com
  • Perplexity: perplexity.ai
  • Google Gemini / AI Overviews: gemini.google.com, and clicks from AI Overviews (often attributed to google organic)
  • Microsoft Copilot: copilot.microsoft.com, bing.com (chat mode)
  • Claude: claude.ai

Method: create a “Generative AI” channel

The idea is to group all these sources under one channel so you can see them at a glance.

  1. In GA4, create a custom channel group that classifies as “Generative AI” all sessions whose source matches these domains.
  2. Add UTM rules to your shared content where possible, to make attribution more reliable.
  3. Watch the channel in your acquisition reports to track its growth and conversion rate.

This helps, but it’s still limited by browser-side losses (missing referrer, blocked cookies).

The real problem is that client-side loses some of these visitors before they’re even counted. That’s where Walityk comes in:

  • Server-side collection: the event is captured on the server, so it survives adblockers, ITP and declined cookies.
  • Multi-touch attribution: Walityk keeps the touchpoints (source/medium) and shows how generative AI weighs in the journey, even when it isn’t the last click.
  • Conversions tied to ad platforms: once the purchase is captured, it flows cleanly to GA4, Meta, Google Ads — with the right source attributed.

In other words: you don’t just see “there’s ChatGPT traffic”, you know how much it earns you.

What to set up

  1. Install Walityk on your store (Shopify, WordPress) — no code.
  2. Connect your analytics and ad destinations.
  3. Create your “Generative AI” channel group in GA4 for reporting.
  4. Track the channel over time: volume, conversion rate, value generated.

FAQ

Does ChatGPT send a referrer? Not always. Depending on context and browser, the referrer can be missing → traffic lands as “Direct”. Server-side tracking with multi-touch attribution limits the damage.

Are Google’s AI Overviews trackable separately? Hardly: clicks from an AI Overview are generally attributed to google organic. You can approximate them via landing pages and behavior shifts, but a clean split stays imperfect.

Why not just look at GA4? GA4 only sees what the browser lets it see. With missing referrers and declined cookies, part of AI traffic is lost or misfiled. Server-side recovers those sessions.

Want to know exactly what generative AI earns your store? Try Walityk free for 14 days or learn what Walityk does.