Sign In
BFCM2026
Install on Shopify
Aimerce Data Report

What looks like an AI order and is not

The quick way to count AI orders is to search order records for the names of AI products. We ran that search and then checked what it caught. Of 32,828 orders that matched, 7,406 were not AI orders. Counting them would have overstated the channel by 29%.

Published 18 November 2026 · Order window 2026-05-19 to 2026-11-16
29%
Over-count from matching AI names alone
32,828 matched, 25,422 were AI orders
7,406
Matched orders that were not AI orders
22.6% of everything the search caught
30 to 1
Non-AI server-created orders for every real in-assistant checkout
Three unrelated apps, over 31 days
143
Orders in 30 days from a search engine mistaken for an AI
One referring domain

Key findings

  • Searching Shopify order records for the names of AI assistants matched 32,828 orders between 2026-05-19 and 2026-11-16; 25,422 of them were AI orders.
  • Counting every match would have overstated AI-attributed orders by 29%.
  • Over 31 days, three server-side apps unrelated to AI created 5,679 orders with no shopper browser, against 191 real in-assistant checkouts, about 30 to 1.
  • One search engine that is easy to mistake for an AI assistant accounted for 143 orders in 30 days.
  • A tag on the landing link should override the browser: a shopper who arrives from an ad while using an AI app is an ad click, not an AI referral.
Finding 01

A name match catches a lot that is not AI

The search looked for assistant names anywhere in an order’s landing link, referring site, browser string and sales channel. That is deliberately generous, and it is roughly what a first attempt at an AI report does.

Figure 1
Orders matching an AI name, and how many were AI orders
Orders in the window whose record contains the name of an AI assistant in any field, against those that passed the rules described below.
Figure 1 data: Orders matching an AI name, and how many were AI orders
GroupOrders
Matched an AI name32,828
Were AI orders25,422
Were not7,406

The orders that fell out did so for a small number of reasons.

Why it matchedWhy it is not an AI order
A different tag on the landing linkThe shopper came from an ad or an email, and happened to be using an AI app as their browser. The tagged source is the source.
An AI app browser with an ordinary referrerThe shopper followed a link from another site while inside the app. The assistant did not send them.
An assistant name inside an unrelated valueA campaign name, a product handle or a search query that contains the word.
A Google click inside the Gemini appAn ad click carries its own click identifier and belongs to the ad.
Finding 02

Server-created orders are mostly not agents

Orders placed inside an assistant have a recognisable shape: created by a server, no shopper browser, no landing page. It is tempting to treat every order with that shape as an AI checkout. That would be wrong by a wide margin.

Over 31 days, three of the largest sources of such orders across the stores we measure produced 5,679 orders between them. They turned out to be an app for sending product samples, an app for replacement shipments and an app for gifting products to creators. Real in-assistant checkouts over the same days: 191.

Figure 2
Orders created by a server with no browser, 31 days
Three unrelated server-side apps, against orders checked out inside an AI assistant over the same 31 days to 15 November 2026.
Figure 2 data: Orders created by a server with no browser, 31 days
SourceOrders in 31 days
Three non-AI server-side apps5,679
In-assistant checkouts191

The safe rule is the dull one. An order source counts as an AI assistant only after its name has been read off real orders. Growth, timing and shape are not evidence.

The rules we ended up with

A tag on the link wins. If the landing link names a source, that is the source, whether or not the browser belongs to an AI app.

A referrer is matched on the host, exactly. Not on any text in the address, and not on a name that appears somewhere in the path or query.

A browser string counts only without a competing source. An AI app’s browser identifies the assistant when there is no tag and no other referrer.

A sales channel counts only once confirmed. New server-side sources are reviewed by name before any of their orders are counted.

These rules under-count in places. That is the trade we chose: a smaller number that holds up is more useful than a larger one that includes sample requests.

Methodology

How this was measured

Every figure comes from the order records of Shopify stores running Aimerce, read as one fleet. An order counts as AI-attributed when Shopify’s own record of it names an assistant in one of four ways: the sales channel that created it, a tag on the landing link, the referring site, or a browser that identifies itself as an assistant’s app or agent. Each order is counted once.

What this does not measure. Shoppers who asked an assistant and later came back another way, clicks that arrive with neither a tag nor a referrer, visits from Google’s AI Mode and AI Overviews (they arrive as ordinary Google traffic), and agents that run in the shopper’s own browser without identifying themselves. All four make the numbers here a floor.

Privacy. Only fleet-level aggregates are published. Store counts are rounded to the nearest ten, and no store, brand, product or order is identified anywhere on this page.

Questions and answers

How do you identify an AI-attributed order accurately?
Use four signals in order of strength: the sales channel that created the order, a source tag on the landing link, the exact referring host, and a browser that identifies itself as an assistant’s app or agent. A tag naming another source overrides the browser, and a new sales channel is counted only after its name is confirmed on real orders.
Why do AI traffic reports over-count?
Because matching AI product names catches orders that only mention them. In our data that over-counted by 29%: shoppers using an AI app as a browser after clicking an ad, campaign names and search queries that contain an assistant's name, and a search engine filed as an assistant.
Is every order created by a server with no browser an AI agent order?
No. Over 31 days such orders from three ordinary apps (product samples, replacement shipments, creator gifting) outnumbered real in-assistant checkouts about 30 to 1.
Is traffic from an AI app always an AI referral?
No. If the landing link carries a tag for another source, or the visit has an ordinary referrer, the assistant did not send the shopper. The AI app was only the browser.

More from this series