// the take
Angulartics2 is an Angular wrapper that lets you send page views and custom events to 20+ analytics providers through a single API. You add the directive or inject the service, wire up one provider, and all your tracking calls stay provider-agnostic. Useful if you need to swap analytics vendors without touching every component.
The directive-based tracking (`angulartics2On`, `angularticsAction`) is genuinely clean — no imperative tracking calls scattered through component logic. Automatic route change tracking works out of the box with Angular Router and handles the common URL-cleanup cases (strip IDs, query params, hashes). The provider list is wide enough to cover most real-world stacks. Each provider has its own spec file, so the abstraction isn't just aspirational.
The version table stops at Angular 15 and the last push was January 2026, but Angular 19 is current — you'd be adopting something that's either quietly abandoned or at best unmaintained for two major versions. The library still uses the NgModule pattern with no signals or standalone-component support, which is where new Angular code is going. Several listed providers (Kissmetrics, IBM Digital Analytics, Woopra) are dead or sunset services, which tells you something about the project's upkeep cadence. There's also no built-in batching or queue — if a provider script hasn't loaded yet, events are silently dropped.
We read the README, the directory tree and a key source file in July 2026. Nobody pays to be listed. How we judge →