home / skills / andrelandgraf / fullstackrecipes / vercel-analytics-setup

vercel-analytics-setup skill

/.agents/skills/vercel-analytics-setup

This skill helps you set up privacy-focused Vercel Web Analytics to track page views, visitors, and events with zero configuration.

npx playbooks add skill andrelandgraf/fullstackrecipes --skill vercel-analytics-setup

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
535 B
---
name: vercel-analytics-setup
description: Add privacy-focused web analytics with Vercel Web Analytics. Track page views, visitors, and custom events with zero configuration.
---

# Vercel Web Analytics

To set up Vercel Web Analytics, refer to the fullstackrecipes MCP server resource:

**Resource URI:** `recipe://fullstackrecipes.com/vercel-analytics-setup`

If the MCP server is not configured, fetch the recipe directly:

```bash
curl -H "Accept: text/plain" https://fullstackrecipes.com/api/recipes/vercel-analytics-setup
```

Overview

This skill adds privacy-focused web analytics using Vercel Web Analytics to your TypeScript full-stack app. It provides zero-configuration tracking for page views, unique visitors, and custom events while respecting user privacy and avoiding cookies. The integration is designed for production-ready deployments and works out of the box with common frameworks on Vercel.

How this skill works

The skill injects the Vercel Web Analytics snippet or config into your app and wires basic page-view tracking automatically. It also exposes a minimal API to emit custom events from client or server code. No third-party cookies or personal identifiers are stored; metrics are aggregated and exposed through the Vercel dashboard. If your project uses the recipe registry, the skill fetches the installation recipe automatically or falls back to a direct recipe endpoint.

When to use it

  • You want lightweight, privacy-first analytics without adding trackers or cookies.
  • You deploy on Vercel and want zero-config setup for basic metrics.
  • You need simple page-view and visitor counts that respect privacy regulations.
  • You want to instrument custom events (e.g., signups, conversions) with minimal code.
  • You prefer metrics aggregated by the platform instead of managing your own analytics stack.

Best practices

  • Keep event names concise and consistent to simplify dashboards and alerts.
  • Instrument high-value user actions (signups, purchases, form submissions) rather than every interaction.
  • Avoid sending PII or user identifiers in custom events to preserve privacy guarantees.
  • Test analytics on staging with a clear filter to avoid contaminating production metrics.
  • Validate that page-view and event timestamps align with your app timezone for accurate reporting.

Example use cases

  • Automatic page-view and visitor metrics for blog, docs, or marketing sites deployed on Vercel.
  • Track conversion events like signups and purchases in a serverless checkout flow.
  • Measure feature adoption by emitting custom events from client components when users interact with new UI.
  • Add lightweight analytics to internal admin dashboards without impacting user privacy.
  • Onboard analytics quickly for a new SaaS app with zero configuration and platform-managed storage.

FAQ

Do I need to configure cookies or GDPR consent?

No. Vercel Web Analytics is designed to be cookie-free and privacy-focused, reducing the need for cookie consent banners for analytics alone.

Can I track custom events?

Yes. The skill exposes a simple API to emit custom events from client or server code so you can measure conversions and feature usage.

What if my project isn’t on Vercel?

The integration is optimized for Vercel hosting and dashboard metrics. For other hosts, consider a self-hosted privacy-focused analytics solution or review the recipe for adaptation guidance.