Vizoalica v0.11.0: campaigns report, exclude your own visits

Deployment support: D1 migrations 0005_campaign_reports.sql (three tables) and 0006_internal_traffic_exclusion.sql (one column with a default, one table). Both are additive. 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 page views that carry campaign labels. Websites that load the SDK from their own backend are unaffected.

On top of v0.10.0:

• Campaigns report. The console has a Campaigns page and the MCP server a get_campaigns tool: page views and visitors by utm_source, utm_medium and utm_campaign, the share of all page views that came from a tagged link, a trend, and the top combinations. Choose a source, medium or campaign to narrow it. Only the three labels are read from the landing address, cleaned in the browser and again by the backend, and only on the first page view of a page load. Nothing else in the query is read, and nothing is stored in the browser. See Campaigns.
• Exclude your own visits. List the IP addresses or ranges you visit from on a website's Edit page and those visits are dropped on arrival and never stored. The website page shows how many events were dropped, per day, with no address kept. For a person on a changing connection, open the site once with ?vizoalica_ignore=1 and that browser sends nothing. See Exclude your own visits.
• Only page views received after the update are counted in the Campaigns report; the report says so when the chosen range starts earlier. Address exclusion is not retroactive.
• Privacy reviews: campaign labels and internal traffic.

Install or update

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