Compare
Revtrail vs Vercel Web Analytics
If you deploy on Vercel, analytics is one component import away, and for a lot of projects that's the correct amount of effort to spend. Two details are worth knowing before you standardise on it: how it's metered, and which tier UTM parameters live behind.
Revtrail vs Vercel Web Analytics, feature by feature
| Capability | Revtrail | Vercel Web Analytics |
|---|---|---|
| Install | One script tag on any host, or a first-party proxy through your own domain. | An <Analytics /> component; Vercel-hosted projects only. |
| UTM campaign tracking | Captured automatically from every landing URL, on every plan. | Requires the Web Analytics Plus add-on at $10/mo per team. |
| Custom events | revtrail('signup') on every plan. | Pro and above; 2 properties per event, or 8 with Plus. |
| Revenue attribution | The product. Payments join the visitor's first-touch journey and every channel is ranked by the money it produced. | Not a feature — no payment-provider integration. |
| Reporting window | Rolling dashboard windows with API access to the underlying events. | 1 month on Hobby, 12 months on Pro, 24 months with Plus. |
| Metering | A monthly event allowance per plan; over the cap the dashboard locks but events keep recording. | 50k events/month on Hobby, then $0.03 per 1K events on Pro. |
Vercel Web Analytics pricing: 50k events/month on Hobby, then $0.03 per 1K events on Pro; custom events need Pro, and UTM parameters need the Web Analytics Plus add-on at $10/mo per team. Read off their own pricing page in August 2026 — check it before you decide, because plans move and we don't control that page.
Read the meter before you scale
$0.03 per 1,000 events sounds like nothing, and at 100k monthly pageviews it is — about $3. At 5M events it's $150/month for a traffic dashboard, and events are shared across every project on the team. It's worth pricing your actual volume against a flat-rate tool before the traffic arrives rather than after.
UTMs behind an add-on is the surprising one
UTM parameters — the mechanism every campaign, newsletter, and sponsored link uses to identify itself — require the Web Analytics Plus add-on at $10/mo per team. If you're running campaigns, that's not an optional extra, it's the feature. Revtrail parses utm_source, utm_medium, utm_campaign, and utm_content from every landing URL on both plans, because a marketing tool that can't read a UTM isn't one.
Where the built-in panel genuinely wins
Zero-config install, no extra vendor, no extra script from a third-party domain (so ad blockers mostly leave it alone), and it's right there next to your deploys. For a side project, a docs site, or an app whose growth doesn't run through campaigns, that's the right call and adding another tool is overhead you don't need.
Using both on Vercel, properly
Revtrail runs fine alongside it, and on Vercel we recommend the first-party proxy: rewrite /rt/track.js to our script and relay beacons through a route handler on your own origin, forwarding user-agent, x-forwarded-for, and the Vercel geo header. Plain external rewrites lose visitor geography on Vercel — the install guide has the exact config.
So which one should you use?
Keep Vercel Web Analytics if you want pageview counts with zero setup and you don't run campaigns. Add Revtrail when you need UTM campaign tracking without an add-on, conversion events on the cheapest plan, or revenue attributed back to the channel that earned it.
Questions people actually ask
- Does Vercel Web Analytics track revenue?
- No. It counts pageviews and custom events, with no payment-provider integration, so revenue per channel isn't something it reports.
- Will running both double my Vercel bill?
- Revtrail events are billed by us, not by Vercel. If you keep both enabled, Vercel still meters its own events; disabling their component stops that meter.
- Does Revtrail work on Vercel's edge runtime and with the App Router?
- Yes. The snippet is a plain script tag with no framework coupling, and SPA route changes are tracked automatically. See the Next.js install guide for the recommended first-party proxy setup.
Comparisons