This is simply a list of features that I would like to implement in Google Analytics Lite. Patches are welcome for these features, just create the issue if one doesn't already exist, post the patch and then post a link to the issue in a comment here.

Role-based tracking
Track only users of a particular role
Path based tracking
White or Black list tracking pages based on path
Google Analytics Code choice
Allow options of code type (async, app, etc)

Comments

baluertl’s picture

Issue summary: View changes
  • Role-based tracking
    and
  • Path-based tracking
    Personally I not really support these ideas as they would cause overlapping in feature set with the major Google Analytics module. As Lite's project page promises this module should keep that only one single configuration option (Tracking ID) and no any more. Otherwise it would compete with the other one and competition is against our Drupal values.
  • Google Analytics Code choice
    If I understand your intention properly, the module would provide options to select from which version of GA tracking code should be inserted? If yes, then I think it is not a future-proof direction as Google sunsets the Legacy tracking code, thus no reason to risk website owners/maintainers to stick with an out-of-date version of tracking. Instead I'd suggest this module should support always only one single, the latest version of tracking code (see issue #2342431: Universal Analytics support) to make sure that websites' traffic is continuously measured as GA changes it mind.
frob’s picture

@Balu, I agree with you.

When this was written there was no support for Drupal 8 and the Google Analytics module. I would want to keep any settings like this as simple as possible to allow for simple things like disabling tracking of Admins/Content creators or just blacklisting the entire /admin path. I haven't come up with any good solutions to these issues, which is why nothing has been done to tackle these.

frob’s picture

If anyone works on these, please apply patches to 2.x branch or use the issue fork mechanism.

frob’s picture

Version: 8.x-1.x-dev » 2.x-dev
baluertl’s picture

Issue summary: View changes