Do coding agents recommend Vercel Analytics?
Vercel Analytics was chosen in 5% of 598 judged product analytics sessions, ranking third.
Vercel Analytics was chosen in 5% of 598 judged product analytics sessions, ranking third. It was also raised as a candidate in 54 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in product analytics inside a realistic codebase. Not what a chat assistant says about Vercel Analytics. What an agent actually installed.
One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about product analytics in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Product analytics |
| Sessions in the category | 598 |
| Sessions where Vercel Analytics was chosen | 27 |
| Install share | 5% |
| Rank in category | 3 of 20 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 54 |
| Chosen when considered | 33% |
| Site | vercel.com |
By agent
Claude Code, Codex, Cursor and Muse Code land within 7 points of each other on Vercel Analytics, which is closer than most products in this experiment manage. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose Vercel Analytics | Share |
|---|---|---|---|
| Claude Code | 150 | 9 | 6% |
| Codex | 180 | 8 | 4% |
| Cursor | 149 | 10 | 7% |
| Grok Build CLI | 29 | 0 | 0% |
| Muse Code | 90 | 0 | 0% |
By who was asking
Vercel Analytics does much better with one kind of buyer than another. It won 45% of sessions asked as vibe coder and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose Vercel Analytics | Share |
|---|---|---|---|
| Vibe coder | 60 | 27 | 45% |
| Junior developer | 240 | 0 | 0% |
| Senior engineer | 238 | 0 | 0% |
| Enterprise team | 60 | 0 | 0% |
What Vercel Analytics was up against
The full ranking in product analytics, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | PostHog | 332 | 56% |
| 2 | Built in-house (no product adopted) | 82 | 14% |
| 3 | Metabase | 37 | 6% |
| 4 | Vercel Analytics (this page) | 27 | 5% |
| 5 | Mixpanel | 19 | 3% |
| 6 | Amplitude | 19 | 3% |
| 7 | Segment | 18 | 3% |
| 8 | Looker Studio | 12 | 2% |
What this means
Vercel Analytics was raised in 54 sessions and chosen in 27. That ratio is balanced enough that the ceiling is presence rather than integration: the product converts reasonably when it is on the table, and it is not on the table often enough.
Where these numbers come from
The 598 sessions in product analytics are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every product analytics run can be replayed on the board.
If you work on Vercel Analytics: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Vercel Analytics?
Yes. Vercel Analytics was chosen in 27 of the 598 judged sessions in product analytics, a 5% install share, ranking third in its category.
Does Claude Code recommend Vercel Analytics?
In 9 of the 150 sessions in product analytics run with Claude Code, which is 6%.
Do different coding agents treat Vercel Analytics differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 0% and 7% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 110 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Vercel Analytics considered but not chosen?
It was raised as a candidate in 54 sessions without being chosen, and chosen in 27. That is a 33% conversion from considered to chosen.
Where this comes from
Armature ran 15,287 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.