Tim Elfelt

Not intentional, PR is welcome. Sorry for delay

@angulartics/core is this a symptom of a deeper issue? @lazychino that's a [nice quick hack](https://github.com/lazychino/angulartics/commit/e4388006d980ee78d522edc476cf1bd0b7fc9f4c) but I'd like the find the real issue if possible. Are you using [angulartics-google-analytics](https://github.com/angulartics/angulartics-google-analytics) latest?

PR welcome, this was done to remove the JQ dep

Angulartics is commonJs friendly afaik I can do `import 'angulartics'` with webpack

Did you guys figure out a workaround for this? ``` if ($injector.has('$state')) { $rootScope.$on('$stateChangeSuccess', function (event, current) { var url = $analytics.settings.pageTracking.basePath + $location.url(); setTimeout($analytics.pageTrack(url), 1000) }); } ``` Here...

It looks like the solution from like @coreylight is the only workaround right now. For anyone with a dynamic title setter service, can you try to inject your title setting...

Nice. This works great if you are predefining the title as a `$routeProvider` prop, but wouldn't solve the problem if the title is set dynamically via a service/ajax call

It'd be nice if Angulartics was usable for most cases out of the box, without having to use a workaround. @raphaelluchini can you share some more info about your setup...

This is what I plan on doing ``` //directive that sets titles and fires `$titleChangeSuccess` //in app.config $analyticsProvider.virtualPageviews(false); //somewhere else $rootScope.$on('$titleChangeSuccess', function(event, route) { $analytics.pageTrack($location.path()); }); ``` Still need to...

See https://github.com/angulartics/angulartics-google-analytics/issues/30#issuecomment-249239196 for one possible solution using the dreaded rootScope. @ProLoser I'd appreciate your opinion and alternative solutions