perpetuum-analytics

Roadmap

Where Perpetuum Analytics is heading. Each item becomes a GitHub issue under its milestone, and each release lists what it delivered in the changelog. Ideas and votes are welcome in issues. The quarters are targets; the timeline shows them on one page.

Now: 3.0, Q4 2026

SSR-safe GA4 and Google Tag Manager with provideAnalytics(), custom events, Consent Mode v2, a manual start after consent, the 2.x Tag Manager names for existing containers, a CSP nonce, 100 % coverage and an end-to-end SSR test on every pull request.

Next: 3.1, cleaner addresses, Q4 2026

• Clean addresses: a pageLocation option that removes query parameters or masks parts of the path before they reach Google, e.g. an e-mail in ?email= or an order id in /orders/:id.

Then: 3.2, richer measurement, Q1 2027

• Typed GA4 events: recommended and ecommerce events (purchase, add_to_cart, begin_checkout…) with typed parameters and items.
• User id and user properties for signed-in visitors.
• Debug mode as an option, without a browser extension.
• Route data: a route can rename its page view, set its own title or skip it.

Later: under consideration

• A testing helper that records events in specs of the apps that use the package.
• Server-side tagging (a custom transport_url).
• Events sent from the server through the GA4 Measurement Protocol, for example a purchase confirmed on the backend, with the visitor’s consent from the browser and the API secret kept on the server.
• Other measurement tools behind the same API, if users ask for them.

Support policy

Perpetuum Analytics is maintained for the long run: the two newest Angular majors, a new one within 30 days of its release, a weekly, monthly and quarterly maintenance rhythm, and at least 6 months’ notice before anything is removed. 2.x gets security fixes until 30 April 2027. The whole policy: Support and maintenance.

This site is open source. Improve this page.