analytics-best-practices

Track custom events and conversions via Vercel Web Analytics track() calls.

20|3|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/andrelandgraf/fullstackrecipes --skill analytics-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analytics-best-practices
Source: https://github.com/andrelandgraf/fullstackrecipes/tree/main/templates/fullstackrecipe/.agents/skills/analytics-best-practices
Command: npx skills add https://github.com/andrelandgraf/fullstackrecipes --skill analytics-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track custom events and conversions with Vercel Web Analytics via the track() call, to measure user actions and form submissions.

Core Features & Use Cases

  • Track events with track(name) or track(name, properties) from client code.
  • Instrument conversions and key actions, then view metrics in the Vercel dashboard.
  • Use development mode to iterate locally before rolling out to production.

Quick Start

Log a conversion event by calling track with the event name and optional properties in your UI code.

Frequently Asked Questions about analytics-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track custom events and conversions with Vercel Web Analytics?

To track custom events and conversions with Vercel Web Analytics, call the track(name) or track(name, properties) function directly from your client-side UI code to emit user action data.

What's the best way to instrument form submissions in a Vercel application?

The best way to instrument form submissions is to use the track() call within your client code, logging the event name and optional properties to measure the action and view metrics in the Vercel dashboard.

Can I test Vercel Web Analytics events locally before deploying to production?

Yes, you can use Vercel Web Analytics development mode to iterate locally and test your track() calls before rolling out event instrumentation to production.

Does Vercel Web Analytics track() work on the client side?

Yes, the track() call works specifically within client-side UI code to emit user actions, conversions, and form submissions, ensuring events are properly captured in production.

Where do I view metrics after instrumenting user actions with Vercel Web Analytics?

After instrumenting user actions with the track() call in your code, you can view the resulting event and conversion metrics directly within your Vercel dashboard.