Guide · AI shoppers
How AI shoppers buy, and why your analytics call them direct
A growing share of shoppers ask an assistant before they buy, and the visit that follows looks nothing like a search visit. Many analytics setups file this traffic under direct, so the channel is invisible in exactly the reports you would use to notice it.
- 4 min read
- Reviewed 6 October 2026
Why it gets misattributed
Assistants often strip or never set a referrer, and they do not always add campaign parameters. With no referrer and no UTM tag, the default bucket is direct: the same bucket as someone typing your address.
Some do leave a trace. ChatGPT, for example, can add utm_source=chatgpt.com to the links it shows. Detecting the channel properly means checking referrer domains and UTM sources together, and being honest about the share you cannot see rather than asserting a number you cannot support.
How the traffic behaves differently
Assistant-referred shoppers usually land deep, straight on a product rather than the home page, because the assistant has already done the browsing.
They arrive with more intent and fewer questions, which tends to make them convert well, and it also makes friction more expensive: a problem that hits this group costs more per session than the same problem elsewhere.
How assistants read your store
There are two routes. Crawlers such as GPTBot, ClaudeBot and PerplexityBot read your pages, subject to your robots.txt. And when a shopper asks an assistant for a product, ChatGPT, Perplexity and Copilot can ask your store directly, through the shopping endpoint Shopify runs for every store, rather than browsing your theme.
Either way, the assistant recommends what it can find and describe, and answers a shopper’s questions from what your store tells it. A product with no description, or a returns policy no page links to, is a product it cannot recommend with confidence.
What to do about it
Make your product data legible. Assistants and search engines lean on structured data for price, availability and variants. If yours is missing or invalid, you are relying on a model parsing your page correctly.
Put plain answers within one click of the home page: shipping, returns and, for apparel, sizing. Check that your robots.txt does not block the AI crawlers you want, and consider an llms.txt that lists your collections, shipping and returns pages.
Check the links assistants already cite. A product that was renamed or removed without a redirect sends a high-intent shopper to your home page or an error. Then segment the traffic: once you can see the group, you can see whether your problems hit it disproportionately, which is the argument for fixing them first.
What Liftable checks and measures
The free scan’s AI checks look at whether product structured data is present and valid, whether shipping and returns answers are within one click of the home page, whether robots.txt blocks AI agents or llms.txt is missing, and whether AI shopping agents asking your store’s own endpoint can find and describe your products. Two more are planned: whether URLs that assistants cite redirect or return a 404, and the share of your sessions referred by AI.
That share stays unknown until the pixel is on, because a crawl cannot see where visits come from. With the pixel on, Liftable classifies each session’s source by referrer domain and utm_source (ChatGPT, Perplexity, Copilot, Gemini and Claude) and flags headless browsers and known AI crawlers, so the channel stops hiding in direct.
Questions
Can I see AI traffic in GA4?
Partly. Assistant referrals that carry a referrer or a utm_source can be filtered for, and a custom channel group for assistant domains makes them visible. Many visits carry neither and land in direct, so treat what you can see as a lower bound.
Is AI traffic worth optimising for?
If it is a meaningful share of your sessions, yes: it tends to arrive with high intent, so friction in that path is disproportionately expensive. Measure your own share first rather than trusting a headline statistic.
Should I block AI crawlers in robots.txt?
That is a business decision, but make it on purpose. A robots.txt written to keep scrapers out years ago can exclude you from assistant answers entirely. Blocking training crawlers while allowing the ones that fetch pages for a shopper’s question is possible, because the major vendors publish separate user agents for each.
The checks that look for this
See whether your own store has the problems this guide describes. The scan is free, takes about a minute, and needs no install.
Scan your storeSolutions
Read next
- AI shoppers · 6 minWhat autonomous agents actually do for a storeNot a chat box on your dashboard: work split into checkable stages, run on a schedule whether or not anyone looked, that stops short of changing your store.Read
- Diagnosis · 5 minTraffic but no sales: how to find out whyHow to diagnose a Shopify store that gets visitors but few orders: the checks to run, from the cheapest to check to the most expensive, and what each one finds.Read
- Diagnosis · 7 minHow to find which pages lose you the most customersExit rate finds your order confirmation page. Ranking pages by lost revenue finds the money. The calculation, in the order that gets there fastest.Read
Terms used
Last reviewed against the product on 6 October 2026.
Find what's holding your Shopify store back
Liftable reads your storefront as a shopper would and shows what looks wrong on your own pages, desktop and mobile: friction, slow pages, missing trust and apps doing nothing, with the evidence for each. Free, in about a minute.
Scan your store.
See where your store is losing revenue and what to fix first. It is free, takes about a minute, and needs no install.