# EventDash documentation (full) Canonical HTML docs: https://www.eventda.sh/docs Index: https://www.eventda.sh/llms.txt --- # AGENTS.md You are helping a developer add EventDash (cookieless product analytics) to their project, or query EventDash analytics. ## Product - Tracker: `https://www.eventda.sh/tracker.js` (~11 KB gzip) - Tracking keys start with `ed_` and belong in the public snippet. - MCP: sign in at https://www.eventda.sh/api/mcp. `edt_` / `edr_` only when the client cannot open a browser. Never put those in the tracker. - Docs: https://www.eventda.sh/llms.txt · https://www.eventda.sh/llms-full.txt · https://www.eventda.sh/docs/ai.md ## Install (user's repo) 1. Do not invent API keys. Ask the user to create a tracking key in EventDash app settings, or read `NEXT_EVENTDASH_API_KEY` / existing script tags. Do not echo the full secret in chat. 2. Detect the stack and include the crawl preload link from the install docs (``). Next.js can also send `POST https://www.eventda.sh/api/crawl/report` from middleware with `EVENTDASH_SERVER_KEY` so unnamed crawlers are named. HTML installs only see known agents: - Next.js App Router → `app/layout.tsx` + `.env.local` `NEXT_EVENTDASH_API_KEY` (see https://www.eventda.sh/docs/installation/nextjs.md) - Next.js Pages Router → `pages/_app.tsx` - React / Vue SPA → script in `public/index.html` - Other → HTML script tag in `` 3. Ensure `.env.local` is gitignored. Tracker keys still appear in HTML by design. 4. Page views are automatic. Add `data-ed-goal` on 1–3 primary CTAs. Use `data-ed-scroll` only if they asked for section views. 5. Optional: `data-allow-localhost="true"` for local testing. ## Query analytics If the user wants numbers, drop-off, or top pages: use MCP, not inventing a REST read API. Prefer OAuth sign-in. Account tokens need `appId` (call `eventdash_apps_list` first). Do not invent write actions. Do not ask the user to paste tokens into chat. ## Do not - Mix tracking keys and MCP tokens - Send emails, names, or other PII in goal params - Use `track()` for conversions (that is a custom event, not a goal). Use `trackGoal` / `data-ed-goal` --- --- 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 is sign-in. `edt_` / `edr_` never go in the tracker and are only for clients that cannot open a browser. - 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, or from `npx @eventdash/cli start`. 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`, and the crawl line under it: ``. Next.js: `NEXT_EVENTDASH_API_KEY` + `next/script` `afterInteractive`, plus that same link in the layout. For Next.js network names, also add the middleware report on https://www.eventda.sh/docs/installation/nextjs (`EVENTDASH_SERVER_KEY`, `POST https://www.eventda.sh/api/crawl/report`). HTML installs only see known agents. 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 tell them to add the URL and sign in. MCP is read-only. Do not paste tokens into chat. Details: https://www.eventda.sh/skills/eventdash/reference.md --- # Quick Start Four steps from signup to live analytics. Free plan: 100,000 events/month and 1 app. Or run `npx @eventdash/cli start` (https://www.eventda.sh/docs/cli.md). 1. Create an app at https://www.eventda.sh/signup (no card). 2. Generate a tracking API key in app settings → Tracker API keys. It starts with `ed_`. Copy it once. 3. Install the tracker (~11 KB gzip): ```html ``` 4. Page views start automatically. Optionally tag a CTA: ```html ``` Do not use `edt_` or `edr_` keys in the snippet. Those are MCP credentials. Next: https://www.eventda.sh/docs/installation.md · https://www.eventda.sh/docs/features/funnels.md --- # Installation Guides Choose your platform. Start with the script tag; add goals when you need conversions. - Next.js: https://www.eventda.sh/docs/installation/nextjs.md - React: https://www.eventda.sh/docs/installation/react.md - Vue.js: https://www.eventda.sh/docs/installation/vue.md - HTML: https://www.eventda.sh/docs/installation/html.md Any site that can load a script works — use the HTML guide as a universal approach. Tracker: `https://www.eventda.sh/tracker.js` Tracking key prefix: `ed_` only. --- # Next.js Installation Never commit API keys. Put `.env.local` in `.gitignore`. Use a server env var. The key is still emitted on the script tag (tracker keys are public by design). ## App Router ```bash # .env.local NEXT_EVENTDASH_API_KEY=ed_your_api_key_here ``` ```tsx // app/layout.tsx import Script from 'next/script' export default function RootLayout({ children }: { children: React.ReactNode }) { return ( ``` Page views are tracked automatically. Prefer HTML attributes: ```jsx ``` Or `window.eventDash.trackGoal('signup_clicked', { page: 'homepage' })`. Custom `track()` events are available on all plans but are not conversion goals. --- # Vue.js Installation Add the tracker to `public/index.html`: ```html ``` In templates: ```html ``` Or call `window.eventDash.trackGoal(...)` from a click handler. Custom `track()` events are available on all plans but are not conversion goals. --- # HTML Installation ```html ``` The crawl preload counts known agents. It does not name an unnamed network. That needs a server report, documented on the Next.js install page. Optional attributes: - `data-domain` — domain being tracked - `data-allow-localhost="true"` — enable localhost (default false) - `data-debug="true"` — debug logging ```html
Pricing
``` --- # Tracking Methods All browser options require the tracker script and an `ed_` tracking key. - HTML attributes: https://www.eventda.sh/docs/tracking/html-attributes.md — `data-ed-goal`, `data-ed-scroll` - JavaScript SDK: https://www.eventda.sh/docs/tracking/javascript-sdk.md — `window.eventDash` - REST ingest: https://www.eventda.sh/docs/tracking/api.md — `POST /api/events`, `POST /api/goals` Prefer attributes for common CTAs. Use the SDK when you need to fire a goal from logic. Use REST from backends and workers. --- # HTML Attributes The tracker script must be installed first. ## Goals ```html View Pricing ``` Kebab-case `data-ed-goal-*` params become snake_case properties. Alias `data-fast-goal` works for goals only; prefer `data-ed-*`. ## Scroll ```html
…
…
``` Threshold is 0–1 (default ~0.5). There is no `data-fast` alias for scroll. --- # JavaScript SDK After the script loads, use `window.eventDash`. Use `trackGoal()` for conversions. `track()` is a custom event (all plans). Trusted revenue uses `POST /api/server/events` with an `eds_` key. ```javascript window.eventDash.trackGoal('signup', { plan: 'pro', source: 'pricing_page' }) window.eventDash.trackPageView('/custom-page', 'Custom Page Title') // optional virtual page window.eventDash.identify('user-123') // opaque id, no email window.eventDash.trackError(error, { context: 'payment_processing' }) await window.eventDash.flush() ``` Queue before the SDK loads: ```html ``` Then `window.eventdash('signup', { plan: 'pro' })`. Methods: `trackGoal`, `track`, `trackPageView`, `identify`, `trackError`, `flush`. --- # REST API Server-side ingest only. Not a read API. Query analytics via MCP (https://www.eventda.sh/docs/mcp.md). ## Endpoints - `POST https://www.eventda.sh/api/events` - `POST https://www.eventda.sh/api/goals` - `POST https://www.eventda.sh/api/server/events` (`eds_` key, Standard+ revenue) - `POST https://www.eventda.sh/api/crawl/report` (`eds_` key). Bot-like document fetches. The address names the network and is not stored. Auth: `X-API-Key: ed_...` or `Authorization: Bearer ed_...`. Server ingest: `Authorization: Bearer eds_...` ## Events batch ## Events batch ```json { "id": "batch_123", "sessionId": "session_abc", "anonymousId": "anon_xyz", "timestamp": 1234567890000, "compressed": false, "events": [ { "type": "pageview", "timestamp": 1234567890000, "pageUrl": "https://example.com/page", "pageTitle": "Page Title", "referrer": "https://google.com" } ] } ``` ## Goal payload ```json { "goal_name": "signup", "anonymous_id": "anon_xyz", "page_url": "https://example.com/pricing", "metadata": { "plan": "pro" } } ``` Responses: 200 ok (or sampled at quota), 400 invalid, 401 bad key, 403 plan restriction, 429 rate limit. Trusted revenue: `POST https://www.eventda.sh/api/server/events` with `identifiedUserId`, `amount` or `revenue_cents`, and ISO `currency`. Public `/api/events` strips amounts. --- # Features - Goals: https://www.eventda.sh/docs/features/goals.md — `data-ed-goal` / `trackGoal()` - Share: https://www.eventda.sh/docs/features/share.md — public links, iframe embed, `data-ed-stat` tags - Search Console: https://www.eventda.sh/docs/features/seo.md — ranked SEO opportunities from EventDash events, GSC, and up to 50 live pages (Standard+); indexing checks resubmit a known sitemap and re-inspect; page×query cannibalization and title mismatch - Ecommerce: https://www.eventda.sh/docs/features/ecommerce.md — search, view_item, add_to_cart, purchase goals - Funnels: https://www.eventda.sh/docs/features/funnels.md — dashboard conversion paths, last 90 days of raw events - Scroll: https://www.eventda.sh/docs/features/scroll-tracking.md — `data-ed-scroll` - Performance: https://www.eventda.sh/docs/features/performance.md — Web Vitals (Standard+ details) - Privacy: https://www.eventda.sh/docs/features/privacy.md — no cookies, PII filter, DNT --- # Goal Tracking Prefer `data-ed-goal` or `trackGoal()`. `track()` creates a custom event, not a goal. ```html ``` ```javascript window.eventDash.trackGoal('signup_clicked', { page: 'homepage' }) ``` Use clear names. Wire important goals into funnels in the dashboard. --- # Ecommerce tracking Use `trackGoal()` or `data-ed-goal`, not `track()`. Custom events do not count as conversions. Trusted revenue (Standard+) is `POST /api/server/events` with an `eds_` key after `identify()`. Recommended names: `search` (query, results_count), `view_item_list` (list_name), `view_item`, `add_to_cart`, `begin_checkout`, `purchase` (amount, currency, order_id). Alias: `purchase_completed`. Fire `purchase` on the thank-you page after payment succeeds. Send a flat order total, not nested line items. HTML: https://www.eventda.sh/docs/features/ecommerce --- # Funnels Create funnels in the dashboard from page views and goals. Stats use the last 90 days of raw events. This is not cohort retention analytics. 1. Open an app → Funnels → create. 2. Add ordered steps matching page URLs, goals, or other tracked events. 3. View conversion and drop-off between steps. Agents can query an existing funnel with MCP `eventdash_funnels_list` then `eventdash_analytics_funnel`. Do not invent write tools; funnel create/update is dashboard-only. --- # Share & Embed Create a public URL from an app dashboard (Share). Viewers see rollup stats — visitors, page views, a timeline — never visitor IDs, IPs, cities, or click element text. Revoke the link anytime. Free includes core metrics with EventDash branding. Paid plans can show more: attribution (campaign sources and referrer hostnames) and a sanitized events feed (type, name, path). ## Iframe ```html ``` ## Live stat tags ```html — — — ``` Stats: `visitors`, `pageviews`, `clicks`, `goals`, `conversion_rate`, `bounce_rate`. HTML: https://www.eventda.sh/docs/features/share --- # Search Console Every plan, including Free. Connect the Google Search Console property that matches the app domain. - Performance chart: clicks, impressions, CTR, position (web search, ~28 days). GSC daily totals lag ~2 days; GSC last 24 hours is delayed several hours - Needs attention: EventDash pages with traffic that GSC shows as not indexed or zero impressions. EventDash views are current to this hour - Recommendations: ranked from EventDash page events, Search Console, and live HTML on up to 50 priority URLs (not a full crawl). Index gaps, CTR, conversions, errors, noindex, canonicals, titles, query cannibalization, title/query mismatch. Converting URLs outrank blogs for the same issue. GSC daily totals lag ~2 days; inspect is sampled (25 URLs) - Page × query: Search Console `page` + `query` pairs. Used to flag competing URLs for one query, and titles that do not cover the top query (synonyms allowed). The SEO tab lists query landings with EventDash views and goals on that URL. Goals are landing-page events, not query-attributed conversions. Not an Ahrefs keyword database. EventDash does not invent titles. - Country and device: Search Console totals for the sync window. Not used in recommendation scores. - Inspect: URL Inspection API (coverage only; does not submit the URL) - Indexing checks: preflight a URL, resubmit the sitemap Search Console already lists, re-inspect around 24 hours, day 5, and day 14. Google still decides. Included on every plan - Request indexing: opens Search Console — that button has no API - Sitemap: submit /sitemap.xml for the connected property. Converting URLs, and URLs with impressions or visits, are flagged when the live sitemap leaves them out - AI search: robots.txt access for ChatGPT, Claude, Gemini (Google-Extended, not AI Overviews), Perplexity, and Copilot, plus visits from those referrer hosts. Not citations. Google AI Overview and AI Mode impressions stay inside the Search Console web totals; they are not visits or crawler hits, and the API does not return that report as its own series unless a generative search appearance is present. Works from an app domain before Search Console is connected. Zero referrers is common. - Change markers: pin a note on any plan; GitHub default-branch commits and releases (Standard+) overlay the Performance chart and Overview timeline. GSC lag ~2 days. EventDash does not claim a commit caused a ranking move. Human docs: https://www.eventda.sh/docs/features/seo SEO checks: https://www.eventda.sh/docs/features/seo-checks Long-form: https://www.eventda.sh/blog/join-search-console-to-product-analytics Search Console clicks, no signup: https://www.eventda.sh/blog/search-console-clicks-with-no-signup AI referral traffic: https://www.eventda.sh/blog/ai-referral-traffic-and-signups GitHub / notes on charts: https://www.eventda.sh/blog/github-commits-on-analytics-charts --- # SEO checks Plain-language notes for the rows on AI Recommendations. Pass means the latest sync looked and did not find the problem. Fail means it did. Not checked means that measurement never ran. A missing measurement is not a pass. Live HTML is a sample of up to 50 URLs. Search Console daily totals lag about two days. - Sitemap: missing, unused, or a visited or converting URL left off the list - Index coverage: crawled and not indexed, or visits with zero search impressions - Stale crawl: last reported crawl older than 90 days (EventDash's line, not a Google rule) - Noindex: a URL with traffic is marked noindex - Canonical: the canonical points at a different URL. A glossary definition and its blog stay both indexable - Title: missing, or under 15 or over 65 characters, only when the URL has search demand - Description: meta description missing - H1: no H1 - Duplicate titles: two sampled URLs share a title - Thin content: under 150 visible words when the URL already has impressions. A glossary definition of at least 100 words is enough - Schema: no JSON-LD - Internal links: too few links to other pages on the site - Cannibalization: two indexable URLs for one query. Do not point rel=canonical between a glossary and its long-form - Title mismatch: the title does not cover the query. EventDash does not invent a title - Striking distance: a query near page 1 needs more depth on the URL that already exists - Clicks with no goal: search clicks land on a URL with no signup or other goal. Goals are EventDash events on that landing URL. A card names the query when one query accounts for most of the clicks - llms.txt: /llms.txt is missing. It is a site map for models, not a Google ranking signal - AI crawler blocks: robots.txt blocks a known AI crawler. That is access, not a citation count Human docs: https://www.eventda.sh/docs/features/seo-checks Search Console: https://www.eventda.sh/docs/features/seo --- # Scroll Tracking ```html
…
…
…
``` Threshold is 0–1. Delay is milliseconds. Extra `data-ed-scroll-*` params are allowed (for example `data-ed-scroll-section-name`). --- # Performance Metrics The tracker can collect Core Web Vitals (LCP, INP, CLS, FCP, TTFB) after install. Detailed performance storage and exports are Standard and Pro. Query averages via MCP `eventdash_analytics_performance`. --- # Privacy & Security - No cookies. Anonymous session ID in localStorage. - PII filter strips emails, phones, SSNs, and card numbers from URLs and form data. - Respects Do Not Track. - Crawler reports may send a connecting address once. It is used for an ASN and RDAP network lookup, then dropped. Stored fields are ASN, organization, country, and network name. - Do not send emails, names, or other PII in goal params or `identify` traits. See also https://www.eventda.sh/privacy --- # EventDash MCP Query EventDash analytics from Cursor, Claude Code, Codex, VS Code, and ChatGPT. Read-only. Endpoint: https://www.eventda.sh/api/mcp HTML docs: https://www.eventda.sh/docs/mcp ChatGPT plugin: https://www.eventda.sh/docs/chatgpt.md Long-form: https://www.eventda.sh/blog/ask-analytics-from-cursor ## Auth - IDEs (Cursor, VS Code, Claude Desktop, Claude Code, Codex): add the endpoint and sign in with EventDash. Do not put a token in the config. - Clients that cannot open a browser: `edt_` account token (Settings → API / MCP) or `edr_` app read key. - `ed_` tracking keys: ingest only. They cannot call MCP. Never put MCP tokens in the tracker snippet. Never paste secrets into chat. ## Connect (editors) Cursor / VS Code `mcp.json`, then click Connect and sign in: ```json { "mcpServers": { "eventdash": { "url": "https://www.eventda.sh/api/mcp" } } } ``` Claude Code: ```bash claude mcp add --transport http eventdash https://www.eventda.sh/api/mcp ``` Codex: ```bash codex mcp add eventdash \ --url https://www.eventda.sh/api/mcp ``` Or install the EventDash plugin in ChatGPT: https://chatgpt.com/plugins/plugin_asdk_app_6ace4208941081918144a70f2cbec3b8 (https://www.eventda.sh/docs/chatgpt.md). stdio-only clients: `npx -y mcp-remote https://www.eventda.sh/api/mcp` (same sign-in). Bearer fallback, only when the client cannot sign in. Keep `edt_` out of git: ```json { "mcpServers": { "eventdash": { "url": "https://www.eventda.sh/api/mcp", "headers": { "Authorization": "Bearer edt_xxx" } } } } ``` Claude Code with a token: ```bash claude mcp add --transport http eventdash https://www.eventda.sh/api/mcp \ --header "Authorization: Bearer edt_xxx" ``` Codex with a token stored in `EVENTDASH_TOKEN`: ```bash codex mcp add eventdash \ --url https://www.eventda.sh/api/mcp \ --bearer-token-env-var EVENTDASH_TOKEN ``` Tool reference: https://www.eventda.sh/docs/mcp/tools.md For agents (install tracker): https://www.eventda.sh/docs/ai.md --- # EventDash MCP tools Read-only. Account tokens need `appId` on analytics tools unless you use an `edr_` key. ## Apps - `eventdash_apps_list` (apps:read): List apps this token can access. Use this first with an account token to get appId values. - `eventdash_apps_get` (apps:read): Get one app (id, name, domain). Account tokens need appId; app read keys do not. ## Analytics - `eventdash_analytics_overview` (analytics:read): KPI totals for a date range: events, pageviews, unique visitors, bounce rate, sessions. Prefer this over listing individual events. - `eventdash_analytics_timeseries` (analytics:read): Hourly or daily timeline of events, pageviews, and unique visitors. - `eventdash_analytics_realtime` (analytics:read): Active sessions in the last 5 minutes (country and device only, no identifiers). - `eventdash_analytics_pages` (analytics:read): Top pages by views for a date range. - `eventdash_analytics_referrers` (analytics:read): Traffic referrer breakdown for a date range (raw events, last 90 days). - `eventdash_analytics_campaigns` (analytics:read): UTM source / medium / campaign breakdown for a date range. - `eventdash_analytics_countries` (analytics:read): Country breakdown by event volume. - `eventdash_analytics_devices` (analytics:read): Device, browser, and OS breakdown. - `eventdash_analytics_performance` (analytics:read): Average Web Vitals (LCP, INP, FCP, load time) from daily rollups. - `eventdash_analytics_events` (analytics:read): Recent event rows (max 100). Filter by type, name, page, or country. Does not include IP addresses. - `eventdash_analytics_goals` (analytics:read): Goal completions grouped by event name for a date range. - `eventdash_analytics_funnel` (funnels:read): Step-by-step conversion and drop-off for one funnel. Pass funnelId from eventdash_funnels_list. ## Funnels - `eventdash_funnels_list` (funnels:read): List funnels and steps for an app. ## Account - `eventdash_account_get` (any token): Plan tier and monthly event usage versus quota. - `eventdash_profile` (any token): Return the profile for the current credentials. Opaque id is stable across token refresh; used by ChatGPT multi-account. Setup: /docs/mcp.md --- # EventDash ChatGPT plugin Install EventDash from the ChatGPT / Codex Plugin Directory. Sign in with EventDash OAuth. Read-only analytics. MCP endpoint: https://www.eventda.sh/api/mcp HTML docs: https://www.eventda.sh/docs/chatgpt Editor Bearer setup: https://www.eventda.sh/docs/mcp.md Tools: https://www.eventda.sh/docs/mcp/tools.md ## Install 1. Open the EventDash plugin: https://chatgpt.com/plugins/plugin_asdk_app_6ace4208941081918144a70f2cbec3b8 2. Install, then connect when prompted (OAuth consent). 3. Optionally allowlist apps on the consent screen. Do not paste `ed_` tracker keys or `edt_` / `edr_` secrets into chat. ## Ask - Top pages / referrers / campaigns for a date range - Funnel drop-off - Realtime visitors - Goal completions and account usage ## Privacy Tools are read-only. Revoke from EventDash Settings → API / MCP (delete the OAuth-labeled token) or disconnect the plugin in ChatGPT. Policy: https://www.eventda.sh/privacy --- # EventDash for coding agents Install the tracker in the user's repo. Query analytics over MCP. Do not invent keys. ## Files - Index: https://www.eventda.sh/llms.txt - Full docs: https://www.eventda.sh/llms-full.txt - Repo instructions: https://www.eventda.sh/AGENTS.md - Skill: https://www.eventda.sh/skills/eventdash/SKILL.md - CLI: https://www.eventda.sh/docs/cli.md - MCP: https://www.eventda.sh/docs/mcp.md - ChatGPT plugin: https://www.eventda.sh/docs/chatgpt.md - API catalog: https://www.eventda.sh/.well-known/api-catalog - MCP Server Card: https://www.eventda.sh/.well-known/mcp/server-card.json - Agent Skills index: https://www.eventda.sh/.well-known/agent-skills/index.json - ARD AI catalog: https://www.eventda.sh/.well-known/ai-catalog.json ## Markdown for agents Request any public page with `Accept: text/markdown` to receive a formatting-stripped markdown representation (`Content-Type: text/markdown`). HTML remains the default for browsers. Docs also have `.md` twins (example https://www.eventda.sh/docs/quickstart.md). ## Install the skill Copy https://www.eventda.sh/skills/eventdash/SKILL.md to `.cursor/skills/eventdash/SKILL.md` (and optionally `reference.md`). For Claude Code, use `.claude/skills/eventdash/`. ## Rules - Tracking key `ed_` goes in the public snippet only. - MCP tokens `edt_` / `edr_` stay in the MCP client. Never in the tracker. - Do not echo full secrets in chat. Read from `.env.local` or the dashboard. - MCP is read-only. --- # CLI `npx @eventdash/cli start` Device login, create an app, write `ed_` to `.env` (refuses if `.env` is not gitignored), install the skill into `.cursor/skills/eventdash/` and `.claude/skills/eventdash/`. No `eventdash.yaml` required. HTML docs: https://www.eventda.sh/docs/cli --- # Plans & limits | Plan | Price | Events / month | Apps | Raw detail | | --- | --- | --- | --- | --- | | Free | $0 | 100,000 | 1 | 30 days | | Standard | $19/mo | 1,000,000 | 5 | 90 days | | Professional | $99/mo | 2,000,000 | 25 | 90 days | Annual: Standard $190/year, Professional $999/year. Free: page views, clicks, scrolls, goals, custom events, and funnels. Standard & Pro: error tracking, performance details, exports, revenue by source, ranked SEO recommendations from Google Search Console. Raw event rows follow the plan window. Dashboard charts use rollups. Quota exceeded → ingest keeps 1 in 10 whole sessions (soft cap). Revenue/server events are always kept. --- # API Reference HTML: https://www.eventda.sh/docs/api-reference ## Event types - `pageview` — all plans (pageUrl, pageTitle, referrer) - `click` — all plans - `form_submit` — all plans (PII filtered) - `scroll` — all plans - `goal` — all plans (`data-ed-goal`, `trackGoal`, `POST /api/goals`) - `performance` — Standard+ - `custom` — all plans - `error` — Standard+ Ingest: `POST /api/events`, `POST /api/goals` with `ed_` key. Read analytics: MCP https://www.eventda.sh/docs/mcp.md