How to Track ChatGPT Traffic and AI Referrals in 2026

Shoppers now ask ChatGPT, Perplexity, Gemini, Copilot and Claude which product to buy, then click through to a store. Whether you can track ChatGPT traffic and the orders it produces depends on how each assistant hands the visitor over, and on whether your analytics knows what to do with it. This guide covers what each one leaves in your data as of September 2026, how GA4 and Shopify now report it, and where the numbers still run out.

The short answer: read the referrer and the UTM tag, and use Arktis to tie them to orders

ChatGPT adds utm_source=chatgpt.com to the links it cites, so those visits are identifiable in any analytics tool. Other assistants are recognised by their referrer when the click happens in a browser. In GA4, since 13 May 2026, visits from recognised assistants land automatically in a channel called AI Assistant; for periods before that, or for a stricter definition, you build a custom channel group with a regular expression. Visits from apps that drop the referrer arrive as direct traffic, and orders completed inside an assistant's own checkout never reach your site at all.

For an online store, Arktis is the clear winner for turning that traffic into revenue numbers. Its AI referrer report counts sessions, visitors and conversions for each assistant, and because Arktis keeps the first source on each visitor's profile, you can see when a shopper who bought days later first arrived from ChatGPT, although the report itself counts conversions made in the assistant-referred session. Plans are $49, $149 and $349 a month, with a 7-day free trial on Growth.

Key takeaways

Tracking AI referral traffic comes down to two signals, the referrer and the URL tags, and ChatGPT is the easiest source because it tags its own links. GA4 has classified recognised assistants as AI Assistant since 13 May 2026, but it only sees what the referrer tells it. Shopify reports AI channel orders in its Agentic section, including direct checkouts that no on-site tracker can see. Everything else, the app clicks without a referrer and the shopper who read an answer and typed your name later, lands in direct or branded search, and no tool recovers it perfectly.

How AI assistants show up in your data

A visit carries two clues about where it came from. The referrer is the address of the previous page, which a browser passes along when someone clicks a link, unless the app or the page stops it. The URL itself can carry UTM parameters, which survive whatever happens to the referrer because they are part of the link.

ChatGPT uses the second. OpenAI's publisher FAQ says ChatGPT automatically includes utm_source=chatgpt.com in referral URLs, which makes ChatGPT the easiest assistant to count: even when an in-app browser withholds the referrer, the tag is still in the address. It is also why paid ChatGPT Ads deserve their own UTM tags, such as utm_source=openai with a paid medium, so they stay out of the organic row.

The other assistants mostly rely on the referrer. That works when someone clicks a cited link in a desktop browser and works less well in mobile apps. Treat any single month's split between assistants as indicative rather than exact.

GA4: the AI Assistant channel

Google added AI Assistant to GA4's Default Channel Group on 13 May 2026. When the referrer matches Google's list of recognised assistants, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant), and the session appears under AI Assistant in the acquisition reports with no setup. Google's documentation names ChatGPT, Gemini, DeepSeek, Copilot and Grok as examples in one place and Claude in its announcement, and states that the channel excludes Google's own AI Overviews and AI Mode, which stay inside Google traffic. It does not publish the full list, so check where Perplexity lands in your property before assuming.

Two things follow. The channel only captures what GA4 can identify through the referrer, as Search Engine Journal put it when the change shipped, so it undercounts rather than overcounts. And if you compare periods across 13 May, use a dimension that is consistent over time. Google's Source Group dimension, added on 11 June 2026, is populated retroactively and has built-in grouping for ChatGPT and Perplexity.

A regex channel group for older setups

If you need your own definition, for a period before May or a stricter list, build a custom channel group. Google says custom channel groups can be applied to reports retroactively, and a standard property can have two of them with up to 50 channels each.

In Admin, under Data display, open Channel groups and create a new group, which starts as a copy of the default. Add a channel called AI assistants with the condition Source matches regex and a pattern such as .*(chatgpt|openai|perplexity|claude|gemini|copilot|deepseek).*, then reorder the list so the new channel sits above Referral and Organic Search, because GA4 files each session in the first channel it matches. Adjust the pattern to your own referral report: the word copilot can also match developer tools, and gemini can match unrelated sites, so check the rows it catches before trusting the total.

Shopify: agentic storefronts and AI channel orders

Shopify sells merchants' products inside AI channels through what it calls agentic storefronts, active by default for eligible stores, covering ChatGPT, Google AI Mode and Gemini, Microsoft Copilot and Meta. The channels behave differently, and the difference decides what you can track.

ChatGPT is a discovery channel. Shopify's help centre says ChatGPT users complete the purchase in your own online store checkout, in ChatGPT's in-app browser or in a new tab on the web, so your analytics and pixels see the visit and the order. Selling there requires selling to customers in the United States, though the store itself can be based elsewhere.

Google AI Mode and Gemini, Copilot and Meta can use a Shopify-powered direct checkout inside the AI channel. For those, Shopify states that Google Analytics and custom pixels do not fire; only server-to-server checkout started and completed events do. The order still appears in your admin with channel or referrer attribution, and Sales channels, then Agentic, reports sales, orders, online store sessions and conversion for each AI channel. For direct-checkout sales, Shopify's own reporting is the record to use.

Why so much AI traffic arrives as direct

Direct is where visits go when a tool cannot find a source. For AI assistants that happens in three ordinary ways. Mobile apps and in-app browsers often send no referrer. People copy a link out of an answer and paste it somewhere else. And many people read a recommendation, close the app, and come back later by typing your address or searching your brand name, which shows up as direct or branded search with no trace of the assistant at all.

Only the first two leave anything to catch. ChatGPT's UTM tag survives both. For the rest, Arktis files a visit that lands on a deep page with no referrer and no UTM tag as dark social rather than direct, on the reasoning that someone shared or pasted the link. That separates it from people typing your homepage, but it cannot tell you which assistant or messaging app the link came from. The third case needs a different instrument, usually a post-purchase question asking customers how they found you.

The limits, including ours

No assistant tells you the conversation behind a click. OpenAI keeps conversations private from advertisers, and there is no prompt data in any referrer, so claims of prompt-level attribution should be read as modelling. Direct checkouts inside Gemini, Copilot or Meta are invisible to every on-site tracker. And where AI referrals are a small share of a store's traffic, a single widely seen answer can swing a month's numbers.

Arktis has limits of its own, and the product is ours, so here they are. The AI referrer report recognises ChatGPT, Perplexity, Copilot, Gemini, Claude, You.com, Poe and Phind by their referring host, and ChatGPT also by its utm_source tag, so a visit that arrives with no referrer at all, which is common from desktop apps and copied links, still lands in direct, or in dark social if it opens a page other than the homepage. Claude, Gemini and You.com visits recorded before 24 September 2026 are not reclassified. Shopify direct-checkout orders reach Arktis through the order webhook, but the shopper never visited your storefront, so unless their email matches a visitor seen before, the order is stored as unattributed. Arktis does not import AI channel data from Shopify's Agentic reports.

Within those limits, it answers the question GA4 leaves half-open: not just how many sessions an assistant sent, but which of them turned into orders, matched to Shopify on email or on the UTM tags of a recent visit. To try it, start the 7-day Growth trial or see the tiers on the pricing page. Our guides to Shopify attribution setup and UTM best practices cover the rest of the setup.

Sources

OpenAI Help: Publishers and developers FAQ, ChatGPT adds utm_source=chatgpt.com to referral URLs, accessed 24 September 2026

Google Analytics: What's new, AI Assistant traffic measurement on 13 May 2026 and Source Group on 11 June 2026

Google Analytics: Default channel group, AI Assistant definition and exclusion of AI Overviews and AI Mode, accessed 24 September 2026

Google Analytics: Custom channel groups, retroactive application, limits and the AI assistants example, accessed 24 September 2026

Search Engine Journal: Google Analytics adds AI Assistant as default channel group, 14 May 2026

Shopify Help: Agentic storefronts, AI channels and order attribution, accessed 24 September 2026

Shopify Help: Selling on ChatGPT, checkout on your own store and US eligibility, accessed 24 September 2026

Shopify Help: Selling on Microsoft Copilot, direct checkout and pixels that do not fire, accessed 24 September 2026