← Back to all sparks
Simple Analytics logo

Simple Analytics

ANALYTICS
Velocity0.0

Privacy-first analytics for websites

Privacy analytics tightening its API and moving IP blocking off the CDN

web-analyticsprivacyapi-versioningself-servedeveloper-experience
Current state
The feed stores each change several times — once with the body text captured as the title, once as a clean headline, sometimes a third time with a date prefix. Behind the duplication, three real changes: API v6 with proper interval support while v5 stays unchanged for compatibility, IP blocking moved off the bunny.net CDN so it works on custom domains and applies per site rather than account-wide, and Events Explorer readability work with column truncation, a full-width toggle and collapsible headers.
Where it's heading
The work is about removing borrowed constraints. IP blocking inherited the CDN's limits and blast radius; moving it in-house made it per-site and custom-domain compatible. API v6 does the same for time handling — hourly data separates day and hour, weeks and months carry explicit start dates — while keeping v5 stable so nobody is forced to migrate. Both are the moves of a product whose users integrate it and stay.
Prediction
With v6 shipped alongside an unchanged v5, expect a deprecation timeline for v5 to be the next API announcement, though the entries do not name one.

Recent moves

  1. 3mo ago

    Events Explorer column handling (duplicate record)

    A duplicate of the Events Explorer readability work, stored with the body text as its title. Cited once on the canonical entry below.

  2. 4mo ago

    API v6 adds interval support, v5 unchanged

    A new API version with real interval semantics — hourly data separating day and hour, week and month buckets carrying explicit start dates — shipped without touching v5. The most consequential change in the window for anyone building on the data.

  3. 4mo ago

    IP blocking moves off the CDN

    IP blocking lived at the CDN provider, which capped it, broke it on custom domains and applied it across every site at once. Bringing it in-house makes it per-site and domain-agnostic — a constraint removed rather than a feature added.

  4. 4mo ago

    Events Explorer improvements (duplicate record)

    A second duplicate of the same Events Explorer release under a date-prefixed title. Flagged so the timeline does not read as three separate changes.

  5. 4mo ago

    Events Explorer improvements

    The canonical Events Explorer record: wide fields truncate instead of forcing horizontal scroll, a full-width toggle, and collapsible column headers. Table ergonomics for accounts with many event properties.

  6. 4mo ago

    Events Explorer improvements (duplicate record)

    A third record of the Events Explorer change, dated a day earlier. Same release, different capture.