The strongest 2026 agentic-commerce statistics measure AI-attributed orders and traffic, AI-referred shopper behavior, and activity reported by commerce platforms. They show that AI is becoming a material discovery and transaction channel. They do not prove that a specific on-site AI agent causes conversion lift.
This page keeps the measurement layers separate and dates every figure. The distinction is essential because “AI shopping,” “agentic commerce,” and “agent-influenced” can describe different interventions.
The numbers worth carrying forward
| Measurement | Reported figure | Source and interval | Scope limitation |
|---|---|---|---|
| AI-attributed orders to Shopify merchants | 11x growth | Shopify, January 2025 to January 2026 | Shopify-attributed orders over the stated interval; not the whole ecommerce market |
| AI-referral conversion during the 2025 holiday season | 31% higher than other traffic | Adobe Digital Insights, holiday 2025 | Referral cohort, not an on-site-agent experiment |
| Revenue per visit for AI-referred holiday traffic | 254% year-over-year growth | Adobe Digital Insights, holiday 2025 | Year-over-year change within the AI-referred cohort, not “254% higher than all traffic” |
| ChatGPT referrals versus non-branded organic conversion | 1.81% versus 1.39% | Reported Visibility Labs analysis of 94 ecommerce sites in 2025 | About 135,000 ChatGPT-referral sessions versus 9.46 million non-branded-organic sessions; original public methodology was not located |
These figures should not be combined into one growth curve. They use different platforms, cohorts, denominators, and time windows.
1. AI-attributed orders are growing on Shopify
Shopify’s July 2026 guide says AI-attributed orders grew 11x between January 2025 and January 2026.
That statement supports a bounded conclusion: AI channels became a more significant source of attributed orders for Shopify merchants over that period.
It does not tell us:
- the absolute share of all Shopify orders;
- the result for non-Shopify merchants;
- whether an on-site assistant was involved;
- which part of the shopper experience caused the growth;
- the incremental value relative to another acquisition channel.
Keep the source, interval, and attribution definition attached whenever the figure is cited.
2. AI-referred shoppers are a distinct cohort
Adobe’s holiday 2025 analysis reported that traffic referred by generative-AI sources converted 31% higher than other traffic. Adobe also reported 254% year-over-year growth in revenue per visit for the AI-referred cohort.
The second figure is frequently miswritten. It is a year-over-year change in revenue per visit for AI-referred traffic, not a claim that those visits produced 254% more revenue than every other traffic source.
The data supports instrumenting AI referrals as their own cohort. It does not establish why the cohort behaves differently. Possible explanations include stronger pre-visit research, different query intent, changing channel mix, or changes in who uses AI shopping tools. The Adobe analysis does not isolate one mechanism.
3. Smaller conversion comparisons need denominator context
The reported Visibility Labs analysis compared ChatGPT referrals with non-branded organic traffic across 94 ecommerce sites in 2025. The reported conversion rates were 1.81% and 1.39%, respectively.
The session volumes were materially different: roughly 135,000 ChatGPT-referral sessions and 9.46 million non-branded-organic sessions. Non-branded organic was therefore about 70 times larger.
This can be presented as a directional cohort comparison. It should not be generalized into an ecommerce benchmark without the original public methodology.
What “agentic commerce” measurements actually measure
The category needs a measurement taxonomy because a single order can involve several AI layers.
| Layer | Example measurement | What it answers |
|---|---|---|
| External discovery | AI referral sessions, product impressions, attributed orders | Did an AI channel help the shopper find the merchant? |
| Assisted interaction | Conversation starts, guided-search use, recommendation engagement | Did the shopper use an assistance surface? |
| Interface guidance | Visible targets shown, tours completed, guidance understood | Did the interface connect the explanation to the shopper’s working surface? |
| Supported action | Action attempted, accepted, denied, or failed | Did the agent call an allowed capability? |
| Verified state change | Expected state observed after the action | Did the connected system reach the intended result? |
| Commercial outcome | Conversion, AOV, revenue per visitor, return rate | Did the treatment affect the business metric under a valid comparison? |
Public market statistics are strongest at the external-discovery layer. Product demonstrations can establish supported actions and verified state changes. Commercial incrementality requires a separate experimental or quasi-experimental design.
What the protocol layer does—and does not prove
Commerce, payment, tool, and agent-communication protocols make new workflows possible. Their existence and adoption should not be used as evidence that every merchant has a working end-to-end agent experience.
For current protocol roles and status, see Agentic Commerce, Explained: The Protocol Stack. Protocol releases and partner counts move quickly; they should be verified against official repositories and announcements at publication time rather than copied into a general statistics page.
Shopify’s Agentic Storefronts documentation is also useful for the external-channel layer. It describes how eligible merchants can make products available to AI channels and how checkout behavior varies by channel. It should not be treated as documentation for an on-site interface-operating agent.
The important evidence gap
We still lack broad independent evidence that isolates the effect of an interface-operating AI shopping agent.
To measure that intervention, a study would need to define:
- the shopper task;
- state exposed by the host;
- visible guidance shown;
- supported action and permission boundary;
- verification method;
- treatment and comparison cohorts;
- product-reliability metrics;
- commercial outcome and attribution window.
Without that detail, “AI-assisted” can combine external referrals, chat engagement, personalization, search, support, and transaction actions into one label.
This gap is an invitation to measure carefully, not permission to fill it with an outcome claim.
How operators should use these statistics
- Instrument AI referrals separately. Preserve source and channel detail.
- Do not splice intervals. January-to-January, holiday year-over-year, and quarterly growth are different series.
- Keep cohorts attached. Referral traffic, engaged shoppers, and all sessions are not interchangeable.
- Separate product proof from commercial proof. A verified action is not a conversion result.
- Record the denominator. A percentage without traffic volume can obscure commercial significance.
- Re-verify before reuse. Platform attribution and protocol status change quickly.
Methodology
This is a scoped synthesis, not original kn8 research. It retains figures for which the source, interval, cohort, and caveat can be stated concisely. It removes earlier adoption counts and protocol-status claims that require continuous re-verification.
Where kn8 fits in this evidence set
kn8 is a private-beta connected-interface model. A connected host supplies current interface state and visible targets; kn8 guides through the existing interface, invokes only supported actions, and verifies the resulting state.
That mechanism is product-level evidence, not a market statistic or commercial result. The absence of a kn8 outcome in this review is intentional: kn8 has not published a customer conversion, AOV, ROI, or support-deflection dataset.
Further reading
- Does On-Site AI Assistance Drive Conversion? — the evidence hierarchy and proposed study design
- AI Agents in Ecommerce — the agent workspace map
- Why Ecommerce Stores Lose Customers — diagnosing a shopper problem before prescribing AI
Figures verified for this revision on July 11, 2026. Recheck the primary source and interval before citing them later.