LoginSign Up
← Back to all sparks
S

Swetrix

ANALYTICS
Velocity5.0

Privacy-focused, open-source web analytics platform

swetrix.com ↗

Swetrix adds user identity and page title tracking as its data model matures

analyticsweb-analyticsprivacysdk
◆Current state
Swetrix has shipped three meaningful tracker updates across its JS and Node SDKs: profile identification with identify/setTraits/reset (4.5.0), selective URL parameter and hash allowlists (4.6.0), and automatic page title collection in both SDKs (4.7.0/3.5.0). These are not independent additions — they collectively expand what a Swetrix user can segment on: URL structure, page name, and user identity.
◆Where it's heading
Swetrix is building a more complete visitor data model, moving from anonymous session tracking toward identified user profiles with richer metadata. Page titles and identity resolve two common analytics gaps. The keepalive flag (events on page unload no longer dropped) and Session Replay bundle reduction in 4.5.0 point to SDK maturity. The identity data model is already in place; the dashboard likely follows with per-user views and cohort tooling.
◆Prediction
The dashboard will surface per-user activity timelines or cohort analysis as a follow-through to the identify API. Further SDK features will likely build on the identity model (e.g., group/org-level tracking, conversion funnels tied to identified users).

◆Recent moves

  1. 1d ago

    [email protected]

    Page title tracking lands in the Node SDK via an optional title field in trackPageView, completing the rollout across both SDKs that began in [email protected]. Server-side tracking now records what page the user actually saw, not just its URL path.

    View source ↗
  2. 1d ago

    [email protected]

    tracker-js now automatically captures document.title with every pageview, including SPA navigation events. The title is overridable via the trackViews callback and can be suppressed by setting it to null — addressing the common gap between URL paths and what users actually see as page names.

    View source ↗
  3. 29d ago

    [email protected]

    Custom events now use the page value modified by the trackViews callback, not the raw path. A consistency fix with no new capability.

    View source ↗
  4. 1mo ago

    [email protected]

    Error tracking in the Node SDK can now capture stack traces up to 64,000 characters, up from 7,500 — an 8× increase that accommodates deep async call stacks from modern Node.js frameworks.

    View source ↗
  5. 1mo ago

    [email protected]

    URL tracking gains allowlists for query parameters and hash fragments. Instead of tracking all or none, operators specify exactly which params and hashes appear in tracked page paths — reducing analytics fragmentation from session tokens, UTM parameters, and unrelated hash routing.

    View source ↗
  6. 2mo ago

    [email protected]

    ⚡ SPARK

    Profile identification (identify/setTraits/reset) lands in [email protected], linking anonymous visitor sessions to a known user ID after authentication. Pre-login activity is retroactively attributed to the identified profile server-side, enabling cross-session analysis against a persistent identity.

    View source ↗