Appearance

Vizoalica v0.10.0: custom events report ​

Deployment support: D1 migration 0004_custom_event_reports.sql (additive: four tables). The backend (Worker) changed. Update a running backend with vizoalica deploy <name> --update, or all of them with vizoalica deploy --update --all. Update the backend before bundling the new @vizoalica/browser-sdk: a backend older than this release rejects custom events that carry the new page field. Websites that load the SDK from their own backend are unaffected.

On top of v0.9.1:

  • Custom events report. The console has an Events page and the MCP server a get_custom_events tool: each event with its count, distinct visitors, and pages, a trend, the top pages of one event, and its most common property values (text and true/false only, redacted, 64 characters). Filter by event or page. Only events received after the backend update are counted; the report says so for an earlier range. See Custom events.
  • Custom events carry their page. The SDK adds the page key to track() events, so the report can show the top pages of an event.
  • Fixed: a website with no token is no longer reported as misconfigured on the website page, in Health, or by the MCP website_status tool.
  • Fixed: the console started from a source checkout accepts backends at the current schema; a leftover apps/cli/package/dist from an older build no longer sets the expected schema.

Install or update ​

sh
npm install -g vizoalica      # or: npm update -g vizoalica
vizoalica --version           # 0.10.0
vizoalica deploy --update --all