# Do coding agents recommend Vercel Analytics?

> Vercel Analytics was chosen in 8% of 359 judged product analytics sessions, ranking second. Measured with Claude Code, Codex and Cursor.

Source: https://armature.tech/library/do-coding-agents-recommend-vercel-analytics
Published: 2026-09-03
Publisher: Armature, Inc. (https://armature.tech)

---

> Vercel Analytics was chosen in 8% of 359 judged product analytics sessions, ranking second. It was also raised as a candidate in 39 further sessions without being chosen.

This page reports what happened when Claude Code, Codex and Cursor 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 | 359 |
| Sessions where Vercel Analytics was chosen | 27 |
| Install share | 8% |
| Rank in category | 2 of 13 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 39 |
| Chosen when considered | 41% |
| Site | vercel.com |

## By agent

The three agents agree closely on Vercel Analytics, choosing it at rates within 1 points of each other.

| Agent | Sessions | Chose Vercel Analytics | Share |
| --- | --- | --- | --- |
| Claude Code | 120 | 9 | 8% |
| Codex | 120 | 8 | 7% |
| Cursor | 119 | 10 | 8% |

## By who was asking

Vercel Analytics does much better with one kind of buyer than another. It won 75% of sessions asked as vibe coder and 0% of those asked as enterprise team.

| Who is asking | Sessions | Chose Vercel Analytics | Share |
| --- | --- | --- | --- |
| Vibe coder | 36 | 27 | 75% |
| Junior developer | 144 | 0 | 0% |
| Senior engineer | 143 | 0 | 0% |
| Enterprise team | 36 | 0 | 0% |

## What Vercel Analytics was up against

The full ranking in product analytics, from the same sessions:

| # | Product | Runs won | Share |
| --- | --- | --- | --- |
| 1 | PostHog | 189 | 53% |
| 2 | Built in-house (no product adopted) | 81 | 23% |
| 3 | Vercel Analytics **(this page)** | 27 | 8% |
| 4 | Segment | 17 | 5% |
| 5 | Amplitude | 14 | 4% |
| 6 | Umami | 6 | 2% |
| 7 | Mixpanel | 5 | 1% |
| 8 | Snowplow | 2 | 1% |

## What this means

Vercel Analytics was raised in 39 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 359 sessions in product analytics are part of a published set of 5,292, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: [how we measured this](/library/how-we-measured-this).

Every product analytics run can be replayed on [the board](/leaderboards/product-analytics).

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 359 judged sessions in product analytics, a 8% install share, ranking second in its category.

### Does Claude Code recommend Vercel Analytics?

In 9 of the 120 sessions in product analytics run with Claude Code, which is 8%.

### Do different coding agents treat Vercel Analytics differently?

Not much. The three agents chose it at similar rates, between 7% and 8% of their runs.

### How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 51 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 39 sessions without being chosen, and chosen in 27. That is a 41% conversion from considered to chosen.

## Read next

- [How to get picked for product analytics by coding agents](https://armature.tech/library/product-analytics-coding-agents-playbook) (Markdown: https://armature.tech/library/product-analytics-coding-agents-playbook.md)
- [Do coding agents recommend PostHog?](https://armature.tech/library/do-coding-agents-recommend-posthog) (Markdown: https://armature.tech/library/do-coding-agents-recommend-posthog.md)
- [Do coding agents recommend Segment?](https://armature.tech/library/do-coding-agents-recommend-segment) (Markdown: https://armature.tech/library/do-coding-agents-recommend-segment.md)
- [Do Claude Code, Codex and Cursor pick the same tools?](https://armature.tech/library/do-claude-code-and-codex-agree) (Markdown: https://armature.tech/library/do-claude-code-and-codex-agree.md)

---

Armature helps software products get discovered and used by coding agents.
Service: https://armature.tech/discoverability · Results: https://armature.tech/leaderboards/sectors · Contact: contact@armature.tech