Agent-Built Order – Definition and How to Measure It
An agent-built order is an order whose cart an AI agent built. The agent found the products and filled the cart through an interface the store offers. The buyer may still place the order on the normal checkout.
Not “a visit from ChatGPT” but “an order the agent put together” – counted at the cart, where the agent’s work is visible.
Why referral data misses it
Web analytics count visits. An agent that shops through an API makes no visit until the very end, and often not even then:
- A UCP agent creates a checkout session over REST. The buyer only appears when they open
continue_url, and that visit looks like direct traffic. - An MCP assistant fills a cart server to server. No page view, no referrer.
- A WebMCP agent works inside the shopper’s tab. The visit is real, but the analytics tool cannot tell which items the agent added.
So the GA4 AI Assistant channel and referrer rules see part of AI-referred traffic, and almost none of the agent’s work in the cart.
How to attribute it
Mark the cart at the moment the agent builds it, and check that mark when the order is placed:
| Route | The mark |
|---|---|
| UCP checkout | The checkout session that created the quote |
| MCP | The cart created by the agent’s create_cart tool |
| WebMCP | The add-to-cart request made by the browser agent’s tool |
When an order is placed, look for the mark on its cart. If it is there, the order is agent-built. Add the revenue, and keep the agent’s name (for example the host of its UCP platform profile).
What to report
- Agent-built orders and revenue per period, compared with the period before.
- By route — UCP, MCP, WebMCP — so you know which interface earns.
- The checkout funnel for UCP: sessions created, updated, handed off with
continue_url, completed. - Error rate of agent calls. A failing tool loses orders silently.
Keep it honest: an agent-built order is a strong signal, not proof that the agent “caused” the sale. The buyer may have chosen the store before asking the agent.
A Magento example
AI Agent Activity listens to checkout_submit_all_after. When an order is placed, it checks if the quote came from a UCP checkout session, an MCP cart or a WebMCP add to cart, and records the order number and total. The report under Reports → Marketing → AI Agent Activity shows agent-built orders and revenue next to calls per channel and the UCP funnel. No IP address or customer data is stored.
Questions
- Is an agent-built order the same as an AI-referred visit?
- No. A referred visit is a person arriving from an AI assistant. An agent-built order means the agent filled the cart itself, often without any visit.
- Why does GA4 not show these orders?
- GA4 counts visits and referrers. An agent that works over an API makes no visit until the buyer opens the checkout link, and that visit often looks like direct traffic.
- Does the buyer have to place the order for it to count?
- In most setups, yes. The agent builds the cart and the buyer pays. The order counts as agent-built because the cart carries the agent’s mark.
- Can I measure this without an MCP or UCP setup?
- Only partly. Without an interface for agents there is no cart the agent built, so you can only see crawler visits and referred traffic.
Related
- Measuring AI visibility
- GA4 AI Assistant channel
- Agentic checkout – definition
- UCP checkout – definition
- AI Agent Activity module
- Glossary