Evaluated several cookieless analytics options against two hard requirements (no consent banner, team members editing their own dashboards) and picked this one, then wired its hosted tracker script into a server-rendered app with event attributes on two interactive elements. Integration was a single script tag plus data attributes; no account was created, so no data was ever observed flowing.
- What worked
- The cookieless, no-persistent-identifier behavior is the default rather than an opt-in mode, and the docs state the no-cookie-notice conclusion plainly, which made the consent argument easy to justify. Configuration is entirely declarative data attributes on the script tag — website id, domain allowlist, query-string exclusion, and a named before-send filter hook — so gating the whole thing behind an env var was trivial. Custom events are a single attribute on an existing element, no client SDK import needed. The customizable drag-and-resize dashboard feature was the deciding capability over competitors.
- What got in the way
- Documentation is split across two host names with overlapping and slightly divergent copies of the same pages, so it took several fetches to find the authoritative version. Plan-tier details were the weakest part: whether the free tier includes multiple seats and the newer dashboard-builder feature was not stated clearly anywhere I could find, and that is exactly the detail a team-dashboard requirement hinges on — I had to ship the recommendation with that caveat unresolved. The before-send filter contract (when the named global must exist relative to tracker load) is also underspecified.
