Matomo (fka. Piwik) client for Angular applications
npm install @ngx-matomo/trackerMatomo (fka. Piwik) client for Angular applications









Note: this library has been renamed to ngx-matomo-client, try it now!
- Installation
- Usage
* Tracking page views with Angular Router
* Tracking page views without Angular Router
* Tracking simple click events in template
* Tracking any event in template
* Using other Matomo's tracking features: Ecommerce analytics, Marketing Campaigns...
* Disable tracking in some environments
* Managing user consent: opt-in/opt-out for tracking & cookies
- Configuration reference
- Advanced use cases
* Customizing script tag
* Server-side rendering (SSR) with Angular Universal
* Scripts with pre-defined (embedded) tracker configuration (Tag Manager variable...)
* Deferred (asynchronous) configuration
- Roadmap
- Launch demo app
_The latest version supports Angular 15 and newer. If you need NgxMatomo for an older Angular version,
see compatibility table below._
ng add @ngx-matomo/tracker
This will prompt you for some information such as your Matomo's server address and site ID. You can find your site ID in
Matomo admin panel.
It will also ask if you want to enable automatic page views tracking. This requires @angular/router to be installed.
This command will take care of importing NgxMatomoTrackerModule (and NgxMatomoRouterModule if needed), along with
basic configuration, into your root AppModule. Use the --module [module] flag to specify a different root module.
_Note #1: If you're not using Angular CLI, follow instructions here instead._
_Note #2: NgxMatomo includes Matomo's tracking script for you.
You don't need to copy/paste the tracking code into your application.
If for some reason you want to manually include the script tag yourself, install as described in previous sections then
follow the instructions described here._
Compatiblity table:
| Angular | NgxMatomo | Matomo |
| ----------- | --------------------------------------------------------------------------- | ------------- |
| 9.x to 12.x | 1.x (docs) | Matomo 3 or 4 |
| 13.x | 2.x (docs) | Matomo 3 or 4 |
| 14.x | 3.x (docs) | Matomo 3 or 4 |
| 15.x | 4.x | Matomo 3 or 4 |
| 16.x | >= 4.1 | Matomo 3 or 4 |
As a general rule, either use provided directives and components in your templates, or inject MatomoTracker service
into your components, services... and use its methods. See next subsections for more detailed usage examples.
If you followed installation instructions, NgxMatomoRouterModule automatically tracks page views for you after each
successful Angular Router navigation event. Under the hood, it calls tracker methods such astrackPageView, setCustomUrl and setReferrerUrl for you.
By default, page title is grabbed from DOM document title and page url is built from Router url. This is fully
customizable as described in following subsections.
#### Customize page title
By default, Matomo's router tracks page view _right after_ NavigationEnd event is emitted by Angular router and
retrieves title from Angular Title service. Delay is configurable with the delay
configuration property.
As of Angular 14, and as long as you don't set delay to -1, customizing page title by setting title property of
Angular route config is natively supported. See Angular tutorial
here: Setting the page title.
If you still need more customization, you can define a MatomoRouterInterceptor
calling MatomoTracker.setDocumentTitle() as detailed in
the dedicated section below.
#### Customize page url
By default, the _current_ url will be sent to Matomo. You may provide a service
to return a custom page url:
``typescript
import { PageUrlProvider, MATOMO_PAGE_URL_PROVIDER } from '@ngx-matomo/router';
@NgModule({
// ...
providers: [
{
provide: MATOMO_PAGE_URL_PROVIDER,
useClass: MyPageUrlProvider,
},
],
})
export class AppModule {}
@Injectable()
export class MyPageUrlProvider implements PageUrlProvider {
getCurrentPageUrl(event: NavigationEnd): Observable
return of('Whatever you want as current page url');
}
}
`
#### Customize anything (page title, ecommerce view...)
You may hook into the tracking process right before trackPageView is called. To do so, declare some interceptors usinginterceptors
the router's configuration property (see configuration reference).
A built-in interceptor is provided to collect tracking information from Route data:
`typescript
const routes: Routes = [
{
path: '',
component: HomeComponent,
data: {
matomo: {
title: 'My Home Page Title',
},
},
},
{
path: 'hello',
component: HelloComponent,
data: {
matomo: {
title: 'My Home Page Title',
ecommerce: {
productSKU: '12345',
productName: 'French baguette',
} as MatomoECommerceView,
},
},
},
];
@NgModule({
imports: [
RouterModule.forRoot(routes),
NgxMatomoRouterModule.forRoot({
// Declare built-in MatomoRouteDataInterceptor
interceptors: [MatomoRouteDataInterceptor],
}),
],
})
export class AppModule {}
`
If you need custom logic to extract data, provide custom interceptor implementation:
`typescript
@NgModule({
imports: [
NgxMatomoRouterModule.forRoot({
interceptors: [MySimpleInterceptor, MyAsyncInterceptor],
}),
],
})
export class AppModule {}
@Injectable()
export class MySimpleInterceptor implements MatomoRouterInterceptor {
constructor(private readonly tracker: MatomoTracker) {}
beforePageTrack(event: NavigationEnd): void {
this.tracker.setDocumentTitle('My title');
this.tracker.setEcommerceView(/ ... /);
}
}
@Injectable()
export class MyAsyncInterceptor extends MatomoRouteInterceptorBase
constructor(private readonly tracker: MatomoTracker, router: Router) {
super(router);
}
protected extractRouteData(route: ActivatedRouteSnapshot): string {
return route.paramMap.get('productId');
}
protected async processRouteData(productId: string): Promise
const product = await this.loadProductData(productId);
this.tracker.setEcommerceView(productId, product.name);
}
}
`
Alternatively, declare your interceptors providers using MATOMO_ROUTER_INTERCEPTORS token:
`typescript
import { MatomoRouterInterceptor, MATOMO_ROUTER_INTERCEPTORS } from '@ngx-matomo/router';
@NgModule({
// ...
providers: [
{
provide: MATOMO_ROUTER_INTERCEPTORS,
multi: true,
useFactory: myInterceptorFactory,
},
],
})
export class AppModule {}
`
Call MatomoTracker.trackPageView() from wherever you want (typically from your _page components_). You may have tosetCustomUrl
manually call or setReferrerUrl.
`typescript
import { Component, OnInit } from '@angular/core';
import { MatomoTracker } from '@ngx-matomo/tracker';
@Component({
selector: 'app-example',
templateUrl: './example.component.html',
styleUrls: ['./example.component.scss'],
})
export class ExampleComponent implements OnInit {
constructor(private readonly tracker: MatomoTracker) {}
ngOnInit() {
this.tracker.trackPageView();
// With custom page title
this.tracker.trackPageView('My page title');
}
}
`
`html
type="button"
matomoClickCategory="myCategory"
matomoClickAction="myAction"
matomoClickName="myName"
[matomoClickValue]="42"
>
Example #2
`
`html
type="text"
matomoTracker="change"
matomoCategory="myCategory"
matomoAction="myAction"
matomoName="myName"
[matomoValue]="myValue"
/>
type="text"
[matomoTracker]="['focus', 'blur']"
matomoCategory="myCategory"
matomoAction="myAction"
matomoName="myName"
/>
type="text"
matomoTracker
#tracker="matomo"
matomoCategory="myCategory"
matomoAction="myAction"
matomoName="myName"
[matomoValue]="myValue"
(change)="tracker.trackEvent()"
/>
type="text"
matomoTracker
#tracker="matomo"
(change)="tracker.trackEvent('myCategory', 'myAction', $event.name, $event.value)"
/>
type="text"
matomoTracker
#tracker="matomo"
matomoCategory="myCategory"
matomoAction="myAction"
(focus)="tracker.trackEvent('focus')"
(blur)="tracker.trackEvent('blur')"
/>
`
Other Matomo tracking features are available through MatomoTracker service. Please refer
to Matomo documentation for details.
`typescript
import { Component } from '@angular/core';
import { MatomoTracker } from '@ngx-matomo/tracker';
@Component({
/ ... /
})
export class ExampleComponent {
constructor(private readonly tracker: MatomoTracker) {}
myMethod() {
// Example of using e-commerce features:
this.tracker.setEcommerceView('product-SKU', 'My product name', 'Product category', 999);
this.tracker.addEcommerceItem('product-SKU');
this.tracker.trackEcommerceCartUpdate(999);
this.tracker.trackEcommerceOrder('order-id', 999);
// ... many more methods are available
}
}
`
Please note that some features (such as setEcommerceView) must be called beforetrackPageView, so be careful when using router adapter!
You may want to look at how to use interceptors.
You may want to disable tracker in dev environments to avoid tracking some unwanted usage: local dev usage, end-to-end
tests...
To do so just set the disabled configuration switch:
`typescript
import { NgModule } from '@angular/core';
import { NgxMatomoTrackerModule } from '@ngx-matomo/tracker';
import { environment } from './environment';
@NgModule({
imports: [
// ...
NgxMatomoTrackerModule.forRoot({
disabled: !environment.production,
// include here your normal Matomo config
}),
],
// ...
})
export class AppModule {}
`
Matomo supports multiple options to allow requiring user consent for tracking.
To identify whether you need to ask for any consent, you need to determine whether your lawful basis for processing
personal data is "Consent" or "Legitimate interest", or whether you can avoid collecting personal data altogether.
#### Do not track
The _do not track_ feature is supported, just set the acceptDoNotTrack configuration option.
Please note that _do-not-track_ setting is configured server-side! You should likely set this setting here to match you
server-side configuration. In case users opt-in for _do-not-track_:
- If set to true here, users will not be tracked, independently of you server-side setting.false
- If set to here (the default), users will be tracked depending on your server setting, **but tracking requests
and cookies will still be created!**
#### Consent opt-in
By default, no consent is required. To manage consent opt-in, first set dedicated configuration option requireConsentMatomoConsentMode.COOKIE
to either MatomoConsentMode.TRACKING
or :
- In the context of tracking consent no cookies will be used and no tracking request will be sent unless consent
was given. As soon as consent was given, tracking requests will be sent and cookies will be used.
- In the context of cookie consent tracking requests will be always sent. However, cookies will be only used if
consent for storing and using cookies was given by the user.
For integration with a consent opt-in form, you may want to use following MatomoTracker methods:
- isConsentRequired()setConsentGiven()
- / setCookieConsentGiven()rememberConsentGiven(hoursToExpire?: number)
- / rememberCookieConsentGiven(hoursToExpire?: number)forgetConsentGiven()
- / forgetCookieConsentGiven()hasRememberedConsent()
- / areCookiesEnabled()getRememberedConsent()
-
See also example below on how to create a consent form. Example below is about creating an opt-in form, but it may be
easily adapted using methods listed above.
#### Consent opt-out
To manage consent opt-out, use dedicated methods MatomoTracker.optUserOut() and MatomoTracker.forgetUserOptOut().
A (very) simple form is provided through component.
For more advanced integration with a custom form, you may want to define your own component and use MatomoTracker
methods:
` To opt-out, please activate the checkbox below to receive an opt-out cookie.html`
`typescript
@Component({
selector: 'my-opt-out-form',
templateUrl: '...',
})
export class MatomoOptOutFormComponent {
optedOut$: Promise
constructor(private readonly tracker: MatomoTracker) {
this.optedOut$ = tracker.isUserOptedOut();
}
handleChange(optOut: boolean) {
if (optOut) {
this.tracker.optUserOut();
} else {
this.tracker.forgetUserOptOut();
}
this.optedOut$ = this.tracker.isUserOptedOut();
}
}
`
This example is adapted from
official guide
about how to create a custom opt-out form
By default, Matomo's script is injected using a basic script tag looking
like