How do I see whether AI agents buy on my site?

Why a tool call is not a sale

A tool can complete technically while the business operation still fails. Browser goal markers are attempts, and only a matching site-server receipt can confirm a created inquiry or booking. The counts have different denominators.

Step 1: mark the attempt

Put data-agent-goal on the relevant action. A click or submit records an observed attempt with its goal name. It is not a completed sale or proof of an agent actor.

<button type="submit" data-agent-goal="order_placed">Place order</button>

Step 2: observe supported tools

If the browser exposes supported WebMCP APIs while the snippet is active, calls yield technical outcomes and duration. Argument values and arbitrary key names are not stored. Remote MCP calls need a server adapter.

await navigator.modelContext.registerTool({
  name: "add_to_cart",
  description: "Add a product to the cart by SKU.",
  inputSchema: { type: "object", properties: { sku: { type: "string" }, qty: { type: "integer" } }, required: ["sku"] },
  execute: async ({ sku, qty }) => { /* your code */ },
});

Step 3: compare separate states

The overview shows tool technical outcomes, browser goal attempts and server-confirmed receipts separately. Their difference is not a conversion rate without individually linked attempts and outcomes.

What you will not see

The standard receipt excludes customer, order and payment contents. A browser marker cannot establish revenue or an agent actor. Do not attribute revenue by matching timestamps alone.

In short