Guozhen AIGlobal AI field notes and model intelligence

Realtime AI News

Clarity finds checkout pages in 25% of AI agent sessions, versus 15% for humans

A session-level analysis by Clarity found that checkout pages appeared in 25% of AI agent sessions, compared with 15% of sessions driven by humans. The gap is an early, measurable signal that agentic shopping is reshaping how traffic moves through ecommerce funnels.

Published

Clarity has published a session-level comparison that puts a number on agentic shopping: checkout pages appeared in 25% of AI agent sessions, against 15% of sessions driven by humans. PPC Land reported the finding, which comes from observed session behaviour rather than user surveys.

The metric records whether a session reached the checkout stage at all, not whether a purchase was completed. Read that way, it is a funnel indicator: agents appear more likely than humans to push a task all the way to the payment entry point.

The ten-point gap matters because it moves the agentic commerce debate from demos to measurement. For most of the past year, agent shopping has been discussed through product launches and proofs of concept, with little public behavioural data to compare against.

For retailers, the implication is a possible new layer in traffic structure. Agent sessions tend to be shorter and more goal-directed, which weakens traditional signals such as time on page and browse depth. Reaching checkout, checkout failure rates and payment conversion become the more useful observations.

Analytics and attribution vendors face a definition problem. It is still unclear whether agent traffic should count alongside human sessions, how a single task split across multiple requests should be stitched together, and whether different vendors are measuring the same thing. Ratios published without that context are hard to compare directly.

Caution is warranted. The report offers two percentages but no sample size, time window or industry breakdown. Without those details, claims that agent shopping has already gone mainstream are premature.

Two things to watch next: whether platforms publish their own agent-traffic shares to cross-check the figure, and how fraud controls, risk scoring and return policies adapt once agents routinely reach checkout. Those developments will say more about maturity than any single ratio.

Why it matters

If the gap repeats across other sites, agent sessions will need to be tracked as a separate traffic class in conversion analytics, with direct consequences for attribution and fraud controls.

AI Agent电商数据分析
Back to realtime news

Nearby Updates

All

11/02, 06:30

AI disruption fears hit business models: Reddit falls nearly 30%, ServiceNow drops 24%

Digital Today reports that Reddit fell nearly 30% in a single session while ServiceNow dropped 24%, framing both moves around AI disrupting traditional business models. Two stocks previously pitched as AI beneficiaries sold off together, signalling that investors are repricing AI as a substitute risk.

11/02, 05:55

OpenAI weighs rebranding its data centers as “AI compute campuses”

OpenAI is preparing a public-relations push for after the US midterm elections, and its chief global affairs officer, Chris Lehane, has floated proposals that include recasting data centers as “AI compute campuses”. Lehane also described AI “speed limits”, a US role in global standards, and the data-center debate, which he called “good and healthy”.

11/02, 05:31

Report: Accenture contractor allegedly linked a personal Claude agent to a Pentagon system

The International Business Times UK reports that an Accenture contractor allegedly connected a personal Claude AI agent to a Pentagon system used by intelligence agencies. The claim is still framed as an allegation, but it puts the permission boundaries of enterprise AI agents and access control in classified environments under scrutiny.

11/02, 03:47

Instinct's WhatsApp replies failed, and its AI agent blamed billing

TheStreet reported that replies from Instinct's AI agent were failing on WhatsApp, with the agent itself attributing the problem to billing. For a product whose entire interface is a messaging thread, the incident turns a back-office billing issue into a user-facing service denial.