Referrer residue
Which engines leave a readable trace, which vanish into direct, and which deserve custom channel rules before the quarterly review.
The visits are few. The misread can be expensive.
Tobias Richter tests how AI search referrals appear, disappear, and convert across analytics stacks so teams stop treating high-intent answer-engine arrivals as noise or direct traffic.
AI search referrals rarely arrive like a campaign. They arrive as clipped paths, odd referrers, copied URLs, privacy-filtered sessions, and unusually prepared visitors. If the setup bins them lazily, the funnel looks colder than it is.
Which engines leave a readable trace, which vanish into direct, and which deserve custom channel rules before the quarterly review.
Why ten answer-engine sessions can matter more than ten thousand casual visits when the landing behavior is closer to procurement than browsing.
How analytics defaults, consent tools, URL copying, and CRM handoff gaps make AI referral influence look smaller than it already is.
A hundred chatbot visits will not change a board chart; one quote-ready session can change pipeline. This desk inspects referrer strings, UTM habits, landing-page behavior, botched channel rules, and the quality of the questions that arrive after an answer engine has already done the selling.
This publication is getting ready.