Agent revenue: what AI agents bought on your store
Tactical reads every order your store sends it and labels it: an agent order (an AI agent placed it), an AI-referred order (a person placed it after arriving from an AI assistant), or neither. Agent orders include the ones placed in an agent checkout, which never load your storefront, so no browser pixel ever sees them. Each label says how sure it is, and the two kinds are never added together. Order data comes from WooCommerce today.
The labels
| Label | What it means | How sure |
|---|---|---|
| Agent order | The platform marked the order as placed by an agent, for example WooCommerce's Stripe agentic checkout | Deterministic |
| Agent order (session match) | The buyer's browser matches a storefront session from the last 24 hours that Tactical classified as an agent browser | High when that session viewed a product on the order; estimated when it only reached the cart |
| AI-referred order | A person bought after arriving from ChatGPT, Perplexity, Gemini, Copilot or another assistant | Estimated (last touch) |
The first rule that fits wins, in that order, and the label is stored with the order.
What you see
- Agent orders and agent revenue, by agent and by product, with a daily trend. The totals include estimated session matches and say how many there are.
- Invisible to pixels: the agent orders placed in an agent checkout, which Google Analytics and other browser tags could not have recorded.
- AI-referred orders, next to the agent numbers and never added to them. One is an agent buying; the other is a person buying after AI discovery.
- An email the first time your store gets an agent order.
Why pixels miss agent checkouts
A browser pixel fires when a page loads in a browser. An order placed inside an AI platform's own checkout never loads your storefront. Shopify says Google Analytics and custom pixels don't fire in Meta's direct checkout; on WooCommerce, Stripe's agentic checkout creates the order on the server. The order still reaches your store, and Tactical reads it from the order webhook.
An agent browser that checks out on your storefront is different: it loads the pages, so Google Analytics does record it, as a person. The session-match label is how Tactical tells you otherwise.
Where it works
| Platform | Order data |
|---|---|
| WooCommerce | Yes, from the order webhooks the plugin registers |
| Shopify | Not yet: it needs Shopify order access, which the app doesn't have. Shopify's own Agentic report in your admin shows orders per AI channel. |
| Custom sites | Not yet: there is no order feed from a custom site |
Evidence for every agent order
When an order is labelled an agent order, Tactical makes an evidence pack there and then: the order, how it was attributed and how sure that is, the agent's declared identity, its session when there is one, any Tactical Gate decisions, and what the record can't prove. Download it as PDF and JSON from the Agent revenue page, for when an agent's purchase is disputed, charged back or returned. It holds no buyer name, email, address, IP address or payment details. What's in it.
What an order record holds
The order ID, total, currency, the line items (product, SKU, name, quantity, price) and the label with its method. The buyer's user agent is used to match the order to a session and isn't stored; nor is their IP address, name, email, address or payment details. Order records are kept while your store is connected. Privacy policy.
Plans
Agent revenue is on every plan, with the plan's history: 7 days on Scout, 90 days on Radar and Command.