---
name: eventdash
description: Adds the EventDash cookieless analytics tracker to a site (Next.js, React, Vue, or HTML), marks conversions with data-ed-goal, and points at read-only MCP for querying analytics. Use when the user asks to add EventDash, cookieless analytics, data-ed-goal, product analytics, or a Google Analytics alternative tracker.
---

# EventDash tracker

Install EventDash in the current project. Querying live analytics is MCP (https://www.eventda.sh/docs/mcp.md), not this skill.

## Rules

- Tracking key prefix `ed_` only in the snippet. MCP tokens `edt_` / `edr_` never go in the tracker.
- Do not generate keys. Have the user set `NEXT_EVENTDASH_API_KEY` (or the HTML `data-api-key`) from EventDash app settings → Tracker API keys. Read the env file if it already exists. Do not echo the full key in chat.
- Prefer `data-ed-goal` over custom JavaScript. `track()` is not a goal.
- Follow https://www.eventda.sh/docs/installation/nextjs.md (or react/vue/html) exactly for the detected stack.
- Keep `.env.local` out of git.

## Steps

1. Detect Next.js (App vs Pages), React, Vue, or plain HTML.
2. Add the script from https://www.eventda.sh/tracker.js with `data-api-key`. Next.js: `NEXT_EVENTDASH_API_KEY` + `next/script` `afterInteractive`.
3. Confirm page views need no extra code.
4. Add `data-ed-goal` on 1–3 primary conversion buttons or links. Use snake_case names like `signup_clicked`.
5. If they want editor queries, show https://www.eventda.sh/docs/mcp.md and say MCP is read-only.

Details: https://www.eventda.sh/skills/eventdash/reference.md