You can add additional code to the matomo.js JavaScript tracker. This allows you for example to:
To enrich the tracker create a file named tracker.js in your Matomo plugin directory. The base template for this file looks like this:
(function () {
function init() {
// Add your plugin code here. For example to enforce disabling cookies:
window._paq = window._paq || [];
winodw._paq.push(['disableCookies']);
}
if ('object' === typeof window.Matomo) {
init();
} else {
// tracker might not be loaded yet
if ('object' !== typeof window.matomoPluginAsyncInit) {
window.matomoPluginAsyncInit = [];
}
window.matomoPluginAsyncInit.push(init);
}
})();
In order to test your tracker integration, execute the following console command within your root Matomo directory.
./console custom-matomo-js:update --ignore-minified
This will merge the content of your tracker.js file with the JS tracker template from $matomoRootDir/js/piwik.min.js and save the
output in the regular $matomoRootDir/matomo.js tracker file. Make sure to always clear your browser cache when you test changes.
When a user installs your plugin, Matomo will automatically update the matomo.js tracker file.
You can add additional tracking methods for example to disable your feature, to send a tracking request or to trigger any other code within your plugin.
function init() {
var enableTracker = true;
Matomo.MyPlugin = {
disableTracking: function () {
enableTracker = false;
}
};
Matomo.on('TrackerSetup', function (tracker) {
tracker.MyPlugin = {
trackme: function () {
if (enableTracker) {
tracker.trackEvent('category', 'action', 'name');
}
}
};
});
}
Above code allows you to trigger the static disableTracking method like this:
_paq.push(['MyPlugin::disableTracking']);
and the tracker specific method like this (using a dot instead of a double colon):
_paq.push(['MyPlugin.trackme']);
Most of the time you will want to use a tracker specific tracking method like trackme. This allows you for example to send tracking requests and it allows a user to configure each tracker instance separately (when using multiple JS trackers on the same page).
If you want to provide for example an option to disable your feature across all trackers, then you may want to add a static method like disableTracking.
We recommend to always namespace your tracker methods with your plugin name as done above with the MyPlugin namespace.
You may hook into events to add additional tracking parameters to tracking requests by adding a plugin. Your plugin can then access these added tracking parameters server side, store the value in a dimension and provide new reports based on this data.
function init() {
Matomo.addPlugin('MyPlugin', {
log: function () {
// add additional tracking parameters to a page view tracking request
var canvas = document.createElement('canvas');
if(canvas.getContext('webgl')) {
return '&webgl=1';
}
return '&webgl=0';
},
event: function () {
// lets you add additional tracking parameters for an event tracking request
},
goal: function () {
// lets you add additional tracking parameters for a goal tracking request
},
unload: function() {
// executed when the user is leaving the page
// can be useful to send for example any not yet sent tracking request
var trackers = Matomo.getAsyncTrackers();
for (var i = 0; i < trackers.length; i++) {
trackers[i].trackRequest('ping=1');
}
}
});
}
Other event names are ecommerce, sitesearch, link, contentInteraction, contentImpressions and contentImpression.
Matomo triggers a few events on specific actions. You can listen to these events using the Matomo.on(eventName, callback) method like this:
<script>
if ('object' !== typeof window.matomoPluginAsyncInit) {
window.matomoPluginAsyncInit = [];
}
// register a callback to be executed as soon as Matomo JS Tracker is loaded.
window.matomoPluginAsyncInit.push(function () {
// listen to the Matomo event whenever a new tracker instance has been created
Matomo.on('TrackerSetup', function (trackerInstance) {
console.log('a tracker has been added', trackerInstance);
trackerInstance.disableCookies();
});
});
</script>
List of events:
TrackerSetup - (trackerInstance). The tracker setup event is triggered as soon as the tracker instance has been created and all the core tracker methods have been defined. At this stage, typically the tracker instance hasn't been configured yet in any way and tracker methods from other non-core plugins like FormAnalytics, MediaAnalytics, and others may not be defined yet. At this stage, the idSite and tracker URL is typically not configured yet. If you need to modify the tracker using such an event, then you typically want to use this event.TrackerAdded - (trackerInstance). The tracker added event is typically triggered when the tracker configuration is completed and the tracker methods by all custom JS tracker plugins have been defined. Use this event if you need to get configuration information like idSite, or need to configure a custom JS tracker plugin like FormAnalytics or MediaAnalytics.MatomoInitialized. This event is triggered when Matomo JS tracker has been loaded and the first tracker has been created. No tracker instance may exist yet under circumstances if the tracker instance is created manually and _paq.push is not used.You can use these events for example to write Matomo plugins or browser extensions to ensure that cookies are disabled, to change behaviour of tracking methods by overwriting them, and more.
Matomo.JSON get access to the JSON objectMatomo.DOM.onReady(callback) calls the callback method when the DOM is ready but not yet loadedMatomo.DOM.onLoad(callback) calls the callback method when the DOM is fully loadedMatomo.DOM.isNodeVisible(htmlNode) checks if the given HTML element is visible within the viewport right nowMatomo.DOM.addEventListener(element, eventType, callback, useCapture) listen to an event without needing to worry about cross browser supportMatomo.on(eventName, callback) listen to a Matomo JS tracker eventMatomo.off(eventName, callback) stop listening to a Matomo JS tracker eventMatomo.trigger(eventName, params, context) Triggers the given event and passes the parameters to all handlers. If no context is given, the callback will be executed in the window context.Matomo.addPlugin(pluginName, pluginObject) listen to tracker plugin events see example aboveMatomo.getAsyncTrackers() get an array of all created async tracker instancesYou can optionally create a minified version of your tracker file. However, you will need to make sure to always keep
it up to date whenever you change the tracker.js file. To provide a minified version simply create a file named tracker.min.js in your plugin directory.
Read more about JavaScript Tracker tests.