Changelog · Release notes
Pulse changelog
What changed in Pulse, newest first.
November 2026
PulsePulse: plans count events, 10,000 free, prices with VAT
Pulse plans now count every event, pageviews included. Personal is free up to 10,000 events a month, prices are shown with VAT, a year costs the same as ten months, and data is kept for 30 days after a plan ends.
- Pulse
Pulse: try features before they're released
A new Beta tab in Settings lets a team's owner or admin turn on the Pulse features that are still in beta. The first is Google Analytics import.
October 2026
- Pulse
Pulse: a visitor is recognised for one day at most
Pulse no longer recognises a reader from one day to the next. Visitors over a range add up each day's unique visitors, and the figures from 26 August to 26 October 2026 were restated the same way. The tracking script keeps nothing in the browser.
- Pulse
Pulse: exact visitor counts on every surface
For any period up to 31 days, Pulse now counts visitors exactly everywhere you read them, the dashboard, the API, MCP, exports and growth reports, instead of adding up estimates.
September 2026
- Pulse
Pulse: import your history from Plausible, Umami, Simple Analytics or Matomo
Bring in the days before Pulse measured your site from Plausible, Umami, Simple Analytics or Matomo. One import per site, read in your browser, never stored.
- Pulse
Pulse: one view switcher, one memory, realtime in five minutes
The date menu is the same twelve rows on every page, remembers one view for all of them, adds All time, and realtime now counts the last five minutes.
- Pulse
Pulse: messages without a workspace, an icon for every notification, a label for every audit entry
Messages from Pulse, its API and the CLI read right whether or not you work in a team; three notifications gain their own icons; every audit log entry reads as words and can be filtered.
- Pulse
Pulse: light theme
Pulse can now be used in a light theme, or follow your device's light or dark setting. Dark stays the default.