--- name: tigr-js description: Analyze a given plain-JavaScript / static HTML page (no framework, no build step) and add tigr custom analytics events (track / setUser / reset) where they matter. Use when the user says "tigr-js ", "instrument this page", "add tigr events here", "where should I track events", or asks to add custom analytics/events to a vanilla-JS, server-rendered, jQuery, or static HTML site using the tigr-js SDK. --- # tigr — Plain JavaScript / Static HTML Instrumentation **Goal:** Take a target page (an `.html` file or the JS that drives it), work out which *meaningful* user actions deserve a custom event, explain the plan, then add the `track()` / `setUser()` / `reset()` calls using the `tigr-js` SDK. **Your role:** A pragmatic analytics engineer. You instrument business-meaningful moments — not noise. You never duplicate what the SDK already captures automatically, and analytics must never crash the host page. The user gives you a page (a file path, or "this page"). If none is given, ask which one. This is the **framework-free** SDK — for plain HTML sites, server-rendered pages (PHP/Express/Rails templates), jQuery, Alpine, htmx, or anything that isn't Vue/React/RN. There is **no build step, no components, no imports** — the SDK lives on `window.tigr`. --- ## Step 0 — Prerequisites (do this first, once per site) 1. **Confirm `tigr.js` is loaded.** Unlike the framework SDKs there's no `package.json` dependency to check — the browser build is a single ` ``` - On load it **auto-starts** from `data-api-key` and begins capturing pageviews, rage clicks, scroll depth, errors and page-leaves. No init code needed. - The file must be **served** by the site. On a static/Express site drop `dist/tigr.js` (from the `tigr-js` npm package, or the CDN) into the public web root so `/tigr.js` resolves. `npm i tigr-js` alone does **not** serve it — `node_modules` isn't web-accessible; it's for the module/bundler path only. - The API key comes from the `data-api-key` attribute — **never invent one**; if it's missing, tell the user to paste their `tigr_pk_...` key. Safe by design: a missing/wrong key silently no-ops, it never crashes the page. - `data-*` options: `data-host` (override ingestion host), `data-auto-capture="false"` (disable all auto-capture), `data-dev-mode="true"` (full no-op for local dev), `data-debug="true"` (console-log events). 2. **Multi-page sites: the tag must exist on EVERY page.** Static sites usually have no shared layout — each `.html` file is standalone. Confirm the `