# Agent Win Rate: Definition & How to Measure

> Agent win rate is the share of agent shopping sessions in which your product is the one recommended or bought, a metric we define here and measure with an open protocol.

<!-- Agent win rate = the share of agent shopping sessions where your product is recommended or bought: here's how to define and measure it honestly. -->
<!-- Canonical: https://agentmint.net/glossary/agent-win-rate/ · By Abdalsalaam Halawa · Published 2026-07-07 -->
<!-- Evidence tags below are load-bearing: <Claim type="spec-fact|reported|hypothesis"> marks how each factual claim is sourced. -->

<KeyTakeaways
  items={[
    "Agent win rate is a selection metric: the fraction of an AI agent's shopping sessions, over a fixed query set, that end with your product chosen rather than a competitor's.",
    "It is not click-through, impressions, or share of voice: those measure exposure, while win rate measures the agent's final decision.",
    "There is no industry-standard definition yet, so the framing on this page is ours, labeled as such rather than presented as established fact.",
    "To measure it, fix a query set, run repeated sessions per engine, and count the share your product wins. The full protocol lives in the methodology.",
    "There is no single win rate: it varies by engine and shifts when models update, so report it per engine, with error bars, and a measurement date.",
  ]}
/>

## Definition (our framing)

There is no settled, vendor-neutral definition of *agent win rate* in circulation. <Claim type="hypothesis">A scan of the practitioner and vendor literature turned up no credible, non-marketing source that defines the term, so the framing below is ours, offered as a working definition, not an established standard</Claim>.

<Claim type="hypothesis">We define **agent win rate** as the share of an AI shopping agent's sessions, for a given shopping task or query, that end with your product being the one the agent recommends or buys, rather than a competitor's</Claim>. The unit of analysis is a completed agent session; the outcome in each session is binary (your product was selected, or it was not); the win rate is the fraction of sessions you won across a defined set of queries. It is the outcome that [agent selection](/glossary/#agent-selection) (why an agent picks one store or offer over another) resolves into for a specific catalog.

Because it is a decision metric, agent win rate is meant to be read alongside a denominator and a scope: *win rate on which queries, on which engine, over how many sessions.* A number without that scope is not a measurement.

## Not click-through or impressions

Agent win rate answers "how often does the agent *choose* me?", not "how often am I *seen* or *clicked*?" Keeping it separate from web-analytics metrics matters, because agents collapse the funnel that those metrics were built to describe:

- **Impressions or share of voice** count how often you appear in an agent's consideration set or its answer. That is exposure, not outcome: necessary to win, but not the same as winning.
- **Click-through rate** is a human-funnel metric. An agent may compare, decide, and even transact without a human ever clicking a result, so CTR can miss the event that actually matters.
- **Agent win rate** is the terminal decision: of the sessions where a choice was made, in how many was your product the pick.

<Callout variant="warning" title="High visibility is not a win">
  A large impression share with a low win rate is a specific, diagnosable failure: the agent sees you and still selects someone else. That gap points at the selection signals (data completeness, price, ratings, description text) rather than at reach.
</Callout>

## How to measure

Agent win rate is measured, not estimated from intuition. The high-level recipe (this is our method, not a standard):

1. **Define a representative query set** for your category: the shopping tasks a real buyer would hand an agent.
2. **Run repeated, independent sessions** on each engine you care about (for example ChatGPT, Gemini, Perplexity).
3. **Record the outcome per session**: whether your product is the recommendation or the purchase.
4. **Compute win rate = wins ÷ sessions, per engine**, and attach the sample size and a date.

The reproducible protocol (prompt sampling, how many sessions, and how to control for position and presentation order so the number reflects your product and not its slot) is written up in [the methodology](/research/methodology/). We publish no win-rate figures here: the point of the metric is that you measure it on your own catalog.

## Honest error bars

A win rate is an estimate from a finite sample of sessions, so it carries sampling uncertainty like any survey. <Claim type="hypothesis">Report it as a range with a confidence interval rather than a single decimal: "38% from 20 sessions" and "38% from 2,000 sessions" are not the same claim, and the first has error bars wide enough to be nearly uninformative</Claim>. Small samples produce wide intervals; that is a fact about the measurement, not a detail to hide.

There is a second source of drift beyond sampling: the thing being measured moves. Because agent behavior changes when the underlying model is updated, any win rate is a snapshot tied to a date and a model version, not a permanent property of your product. Stating the interval and the date is the difference between an honest metric and a vanity number. It is why this site refuses point estimates presented without error bars.

## Per-engine win rate varies

There is no single agent win rate to report, because the engines do not agree. <Claim type="reported" source="ACES, Allouah et al., arXiv:2508.02630" date="2025-12-17" href="https://arxiv.org/abs/2508.02630">In the ACES study (a controlled simulation of frontier shopping agents, not a record of live sales), selection behavior was model-specific, and a model update could drastically reshuffle which products an agent picks</Claim>. The practical consequence is that the same product can win often on one engine and rarely on another, and that a comfortable win rate can decay after a model release you did not control.

So a win rate is only meaningful per engine and per date: measure each engine separately, and re-measure after major model updates rather than trusting a figure indefinitely. The [platform playbooks](/platforms/) track where ChatGPT, Gemini, and Perplexity currently diverge, and [how AI agents choose products](/how-ai-agents-choose-products/) covers the signals that move the number in the first place.

For the rest of the agentic-commerce vocabulary, return to the [glossary](/glossary/).