angulartics
Advanced tools
Changelog
1.0.0 (2015-12-28)
<a name="0.20.3"></a>
Changelog
0.20.3 (2015-12-23)
<a name="0.20.2"></a>
Changelog
0.20.2 (2015-11-17)
Add setting to exclude specific routes from pageview tracking
<a name="0.20.0"></a>
Changelog
0.20.0 (2015-07-27)
<a name="0.20.0"></a>
Changelog
0.19.3 (2015-07-27)
This is just a maintenance release so people who had their builds broken by 0.19.2 can safely upgrade 0.19.x.
<a name="0.19.2"></a>
Changelog
0.19.0 (2015-06-27)
Changelog
0.18.0 (2015-05-22)
<a name="0.17.2"></a>
Changelog
0.17.2 (2015-01-15)
hashbang
mode 8543ef8d8cf6a933af78d9a5737c327042913a34bower cache clean
) e68531de81526101aedca91e9721c9f0d2de322f
event, properties, options, callback
developerMode: true
in $analyticsProvider
to stop sending data (https://github.com/tomasescobar) a0cce769f569dfb46f765eda1a97eccc2748c3f9$analyticsProvider.settings.ga
object for configuration, which after initing multiple analytics accounts like this: ga('create', 'UA-XXXXXX-XX');
ga('create', 'UA-XXXXXX-XY', 'auto', {'name': 'additionalTracker1'});
ga('create', 'UA-XXXXXX-XZ', 'auto', {'name': 'additionalTracker2'});
allows to configure the additional providers on startup:
config(function ($analyticsProvider) {
$analyticsProvider.settings.ga.additionalAccountNames = ['additionalTracker1', 'additionalTracker2'];
});
You can also change the configuration while running the app which, while not the most elegant solution, allows sending only some events to multiple accounts by:
$analyticsProvider.settings.ga.additionalAccountNames = ['additionalTracker1'];
$analytics.eventTrack('eventName');
$analyticsProvider.settings.ga.additionalAccountNames = [];
<a name="0.17.1"></a>