← ClaudeAtlas

installlisted

Install WireBoard analytics in a codebase, or debug an existing WireBoard integration that isn't working. Covers the tracking script for pageviews, client-side (SPA) navigation tracking, custom events (declarative or programmatic), cookie consent, the official Google Tag Manager template, the dataLayer bridge, and a step-by-step troubleshooting flow.
wireboard/wireboard-claude-plugin · ★ 2 · Data & Documents · score 78
Install: claude install-skill wireboard/wireboard-claude-plugin
# WireBoard integration ## Working rules 1. **Never invent values.** The `appId`, the collector hostname and the Publisher UUID come from the user's WireBoard dashboard. Ask the user to paste their snippet; never write one with placeholder IDs. 2. **Paste the snippet unchanged.** Same quotes, same spacing (see [`tracking-script.md`](tracking-script.md), "Paste it exactly as given"). 3. **In DevTools, filter by the collector hostname** (the value in the user's `newTracker` call, e.g. `pipeline-0.collector.wireboard.io`). The request paths do not matter for debugging. 4. **Call the script "the WireBoard tracker" or `wireboard.js`.** 5. **Use this skill as the API reference.** It documents every option and message a developer needs; reading the minified `wireboard.js` or `events.min.js` does not help. 6. **Test in a visible browser.** Headless browsers (Playwright or Puppeteer in headless mode) are filtered as bots: their hits get HTTP 200 and are never counted. If you test with a browser tool, launch it with `headless: false`, or ask the user to click through the site. 7. **Always verify after implementing** (Step 5). Don't call it done before a real visit shows up in WireBoard. ## What WireBoard ships Two scripts, both from `https://static.wireboard.io/`: - **`wireboard.js`**: the tracking script. Pageviews, sessions, visitors. One per site. - **`events.min.js`**: optional. Custom events (clicks, form submits, purchases). Two identifiers the user must provide (never inve