~ Nick
This module tracks the numbed of times a view, and each of its displays, is rendered.
The need for this module arose in a large site using multiple Views that had changed drastically over the years. Short of going over every single page of the site, we had no idea which Views were actually being used. This module was the answer.
By enabling this module, every Views display render is tracked. Yes, be careful using it on Production. You can then review and see which Views are actually in use.
This module started out in life as a tool for cleanup, but ultimately proved its worth in optimization. I’m a huge fan of implementing third party integration through XML and JSON feeds output by Views. You get some great cache control, easy access to any space servers, and of course easy management. Using Views Analytics you can review which parts of your API get used the most and focus your optimization efforts there. In previous cases this has meant adding a CDN, but it could also mean optimizing those specific queries.
Views Analytics is installed in the usual way. See Installing contributed modules.
Stats are displayed in the Views interface (so make sure Views UI module is also enabled).
This module is fairly simple, but it does write to the database. So just like most Drupal statistic modules it will have a performance impact. How much impact depends on your setup.
Views previews are excluded so you don’t throw the count by editing the Views.
Caching can cause inaccuracies however.
Again, this module is not intended for traffic analytics. It’s designed to tell an administrator if a View is actively used and give a rough idea of how much.
If you find any issues, or would like to contribute, please visit my GitHub page.