How much of Direct traffic is actually AI?

Varies by site, typically 15–40% for B2B SaaS sites with strong AEO presence. Sites with weak AEO presence have ~5% AI in Direct. The mobile-Direct cut is where the concentration is highest.

Can I just block referrer-stripping browsers?

No — that would block ChatGPT iOS users entirely from your site. The stripping happens client-side in the AI app, not at your server. The heuristic recovery above is the only path.

Will Google fix the referrer-stripping problem?

Unlikely. Google's own AI Overviews, ChatGPT, Perplexity, and Claude all share the no-referrer pattern — it's by design (privacy + reduced trackability). Plan to live with the heuristic for the next 2+ years.

Does Lantern automate this?

Yes — Lantern's HubSpot integration applies the 5-rule heuristic during onboarding and writes the direct-likely-ai tag automatically as new sessions land. Your team gets the recovered population in the dashboard with no manual workflow.

How to tag Direct traffic as likely AEO (2026)

Direct traffic in HubSpot is a graveyard. As of 2026, it includes: people typing your URL (true direct), bookmarks, email-client redirects, mobile app embeds, AND mobile ChatGPT / Perplexity referrals that strip headers. Recovering the AEO portion takes a five-rule heuristic. Here it is.

Required tools

HubSpot Marketing Analytics > Sources export
An AEO monitoring tool to time-correlate citation events vs traffic spikes
A workflow to apply the direct-likely-ai tag
A clear labeling convention so 'estimated' AEO numbers aren't conflated with 'confirmed' in finance reviews

The steps

Pull a 30-day Direct traffic session list with first-page-seen and device type

HubSpot Marketing Analytics > Sources > Direct. Export with columns: timestamp, first-page-seen URL, device type, country. This is the population you're going to subdivide using the heuristic below.

Rule 1: Direct traffic landing on long-tail informational URLs is probably AEO

If first-page-seen is '/learn/aeo-pipeline-attribution/' or '/how-to/track-chatgpt-referrals/', no human types that URL. Either they bookmarked it (rare for first-time visitors) or they came from an AI engine that stripped referrer. Tag these as ai_source = chatgpt-likely.

Rule 2: Direct traffic from mobile devices is more likely AEO than desktop

Mobile is where referrer-stripping is most aggressive (in-app browsers in ChatGPT iOS/Android, Perplexity mobile, etc.). Filter your Direct list to mobile-only and the AEO concentration is 2–3x higher than desktop Direct.

Rule 3: Direct traffic timed to recent AI citations on your prompts is probably AEO

If your AEO monitoring tool shows you were newly cited on a major prompt yesterday and your Direct traffic spiked the same day, the spike is the AI traffic. Time-correlate Direct session count vs new-citation events on a daily resolution chart.

Rule 4: Direct traffic that converts immediately (within 1 page) is more AI-like than human-direct

Human Direct (typed URL, bookmark) usually browses 3+ pages before any conversion intent. AI-referred Direct often goes straight to a comparison page and fills a form within 5 minutes. Single-page-session conversions in the Direct bucket are an AEO smell.

Apply a tagged ai_source = direct-likely-ai for the Direct sessions matching 2+ rules

Build a workflow: Contact created from Direct AND first page seen contains [/learn/, /how-to/, /compare/] AND mobile device → set ai_source = direct-likely-ai. This creates a separate bucket your reports can choose to include or exclude.

Report two AEO numbers: 'confirmed' (UTM-tagged) and 'estimated' (confirmed + direct-likely-ai)

Show both in your CMO dashboard. 'Confirmed AEO ARR: $80K. Estimated AEO ARR (including direct-likely): $112K.' Pairs honesty (we can't confirm everything) with completeness (we know we're undercounting if we ignore Direct).

Common mistakes

Tagging all mobile Direct as AEO without the URL filter — overcounts and triggers a finance audit.
Only tagging confirmed AEO and ignoring the recoverable Direct traffic — undercounts AEO impact by 30–50%.
Conflating 'confirmed' and 'estimated' in the same report number — undermines credibility when a finance reviewer notices.
Forgetting to update the rule set as new AI engines launch — Copilot mobile, You.com, Brave AI all have different referrer behaviors.

Where this fits in the AEO pipeline attribution stack

The steps above are one link in a longer chain. In order: you pick prompts to monitor, you track AI-referred sessions, you tag contacts in your CRM, you roll attribution up to the Deal object, you report pipeline dollars to the CFO. If you skip any link, the chain breaks and the number you quote to finance can't be defended in an audit.

If you're still evaluating which tool to run this workflow on, Lantern's AEO tool comparison hub has honest head-to-head pages for Profound, Scrunch, Peec AI, AthenaHQ, and HubSpot's own AEO product — scored on the dimensions that matter for a CMO buyer (CRM integration depth, reporting quality, prompt-scaling economics).

If you're about to walk this work into a budget review, the CFO's Guide to AEO Budget Defense has the memo template, the five-slide deck structure, the attribution-math cheat sheet, and the three most-common CFO objections with counter-arguments. It's the long-form companion to this how-to and was written for the renewal conversation specifically.

The operational rhythm that works: run the steps above once to set up, then review the output monthly in a 15-minute standing meeting with your Head of Growth and RevOps lead. Quarterly, re-audit your prompt list, your content backlog, and your attribution lookback window. Annual: present the full-year AEO ROI trend to the board. That cadence is what separates teams who ship an AEO dashboard once from teams who run AEO as an ongoing budget-defensible channel.

How to tag Direct traffic as likely AEO