--- title: "What is AI referral traffic? | daily.dev Ads glossary" url: https://business.daily.dev/glossary/ai-referral-traffic/ description: "AI referral traffic is visitors who arrive from an AI assistant (ChatGPT, Perplexity, Claude, Gemini) after it cited your page. It is small, high-intent and badly measured, because many visits arrive with no referrer and count as direct." lastUpdated: "2026-10-20" llmsTxt: https://business.daily.dev/llms.txt --- ## What is AI referral traffic? AI referral traffic is visitors who arrive from an AI assistant (ChatGPT, Perplexity, Claude, Gemini) after it cited your page. It is small, high-intent and badly measured, because many visits arrive with no referrer and count as direct. Also called: AI assistant referrals, LLM referrals. When an assistant cites a page, some readers click through. The visit sometimes carries the assistant's domain as the referrer and sometimes a tag the assistant added to the link; often it carries nothing, because the click came from an app or a copied link, and analytics files it under direct. The traffic you can see is a floor, not the total. The visitors are unusually qualified. They asked a specific question, read a composed answer, and chose your page from the sources, which makes them closer to a decision than a search visitor. Developer sites see this in conversion rates well above their average. Measure it three ways at once: a channel group in analytics for assistant referrers, tagged links where you control them, and a question on your sign-up form ("how did you hear about us?") with an AI option. Then treat the total as a minimum and watch the trend. ## How does AI referral traffic show up in analytics? Three ways, unevenly. Some visits carry the assistant's domain as the referrer and land in the referral channel. Some carry a tag the assistant appended to the link, which can be captured with a rule. Many carry nothing, because the click came from a desktop app, a copied link or a browser that strips the referrer, and they are filed under direct. The traffic you can see is a floor; the real total is somewhere above it, and nobody outside the assistant knows by how much. The one thing you can count exactly is the citation itself, by tracking prompts and recording which pages each assistant cites. ## How do you measure it as well as it can be measured? - **A channel group** in analytics for assistant referrer domains and their tagged parameters. - **Tagged links** wherever you control the link an assistant might quote. - **A "how did you hear about us" question** at sign-up with an AI-assistant option. - **Prompt tracking:** which pages are cited for which prompts, weekly. - **Landing-page comparison:** pages assistants cite against their search rankings. Report the total as a minimum and watch the trend and the conversion rate, which is where the channel shows its value. ## Why are these visitors worth more than their volume? They asked a specific question, read a composed answer, and chose your page from the sources, which puts them closer to a decision than a search visitor who clicked the first result. Developer sites see this in conversion rates well above their average and in the questions those visitors ask, which are about fit and price rather than what the product is. Small numbers of them are worth tracking because each one is a shortlist you were on. ## How do you get more of it? Earn the citation: pages that answer a real question in the first paragraph, with specifics, comparisons, named alternatives and a visible date; agent-readable formats (markdown twins, llms.txt); consistent facts everywhere; and presence on the developer platforms assistants already cite, which is what agentic advertising adds. Then make the landing worth the click: the visitor arrives with the answer and wants the next step, so give them the quickstart, the price and the comparison, not a hero statement. On this site, each visitor an assistant sends is recorded, tagged on bookings, and shown a welcome offer, because the channel is small enough to treat each visit as a lead. **Common mistakes** - Reading the referral report as the total and concluding the channel is tiny. - No AI option on the "how did you hear about us" question. - Landing a visitor who already has the answer on a page that restates it. - Optimising for the citation and forgetting the page the citation opens. **How developers experience it** - They asked the assistant, got a shortlist with links, and opened yours. - They arrive wanting the next step, not the pitch. - They copy the link into a team chat, which is why your referrer is missing. ## On daily.dev This site records which assistant sent each visitor, tags it on bookings and shows those visitors a welcome offer. daily.dev itself is among the most-cited sources on developer prompts, which is what [Agent Ads](https://business.daily.dev/agent-ads.md) build on. ## AI referral traffic vs organic search traffic | | AI referral traffic | Organic search traffic | | --- | --- | --- | | **Visitor arrives** | With an answer and a shortlist | With a query | | **Volume** | Small, growing | Large | | **Measurability** | A floor; referrers often stripped | Good | | **Conversion** | Usually above site average | Average | | **Earned by** | Citations: specific, agent-readable pages on trusted sources | Rankings: authority, relevance, links | ## Go deeper - [Measuring AI assistant referrals to developer docs](https://business.daily.dev/resources/measure-ai-assistant-referrals-developer-docs.md) - [Developer marketing when AI Overviews take the clicks](https://business.daily.dev/resources/developer-marketing-ai-overviews-search-clicks-fall.md) - [Getting recommended by ChatGPT and Claude](https://business.daily.dev/resources/get-developer-tool-recommended-by-chatgpt-claude-cursor.md) Related terms: [Answer engine optimization](https://business.daily.dev/glossary/answer-engine-optimization.md) | [Agentic advertising](https://business.daily.dev/glossary/agentic-advertising.md) | [UTM parameters](https://business.daily.dev/glossary/utm-parameters.md) ### Frequently asked questions **Why is AI referral traffic undercounted?** Because many assistant clicks come from apps, copied links or browsers that strip the referrer. Only part of the traffic carries the assistant's domain or a tag on the link; the rest is indistinguishable from someone typing the address. **How do I measure AI referral traffic?** Create a channel for assistant referrer domains in analytics, keep tagged links where you control them, ask new users how they found you with an AI option, and compare landing pages that AI cites against their search rankings. Report the result as a floor. **Is AI referral traffic worth optimising for?** Yes, for its quality more than its volume: these visitors arrive with a question answered and a shortlist made. The work to earn it, answer engine optimization, also improves the pages for everyone else. **Which assistants send the most developer traffic?** It changes month to month and by audience; the ones that search live and cite sources send the most visible referrals. Track them all in one channel group and watch the mix rather than betting on one. **What should the landing page do for an AI-referred visitor?** Give the next step. They arrive with the answer and a shortlist, so show the quickstart, the price, the comparison and a way to start, not a restatement of what the product is. [All terms](https://business.daily.dev/glossary.md) | [Explore your options](https://business.daily.dev/schedule/?ref=glossary-ai-referral-traffic) | [How pricing works](https://business.daily.dev/pricing.md)