Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
ClickTale is used to collect user experience analytic data, which can be used to enhance the users experience of the site. ClickTale records videos of the users movement on the site based on the users mouse movements. ClickTale also generates heatmaps based on where the user clicks and hover their mouse on the pages.
This module creates an integration with Recline.js to visualize user-submitted data.
This creates grid, graph, and map data previews for CSV and XLS files based off of the following mechanisms.
It first checks to see if the DKAN Datastore module is installed, and if a datastore has been created for the file. If the datastore is available it uses that to visualize the data. This is extremely scalable since it only queries the first 50 rows of the table in the database. It has been tested with files up to 500 GB and a million+ rows.
jStats allows you to aggregate statistics about visitors on your site, without breaking the cache-ability of your pages.
At its core, jStats could be seen as a bridge between the core Statistics module, that stores its data in Drupal but is incompatible with aggressive and external caching, and Google Analytics, that only adds a small JS fragment to the page and thus makes them perfectly cachable, but can't easily be accessed by Drupal modules (in order for example to sort a listing of node by the number of node views): it's a lightweight way to keep your statistic data in your database, that still works when the page you want to have statistics on is stored in cache.
FireStats is a web statistics system. This module allow FireStats to monitor access to your Drupal site. A live demo of FireStats is available here. Please report Firestats integration module's problems in the project issue tracker and the statistics system's problems to http://firestats.cc/
Visibility API (Optional):
Firestats module is integrated with Visibility API module to set stats collection from specific parts of the website only; just like the block visibility setup.
Decounter is a small module which decreases content view counter each time a user matching criteria is viewing a node. User with access to administration can set rules for excluding users by roles, uids and authorship.
Google Analytics Sync allows to synchronize information from Google Analytics to Drupal saving information in node_counter table.
Information is synchronized in periodic intervals (via Drush or Cron) and after being available in Drupal can be used for generic statistics, or for
creating views representing most popular items.
The module is specially useful for sites using a CDN or a Reverse Proxy in front of Drupal that can not use the normal statistics module.
Configure correctly Google Analytics Reports to connect to GA API using your key.
Enabling the recording and presentation of statistics for the Search API module. There are plans to implement usage and performance statistics in the near future. For now this module gives your Drupal site a top search phrases block for all the Search API indices on your site.
Allows your Drupal site to gather statistics on how many times your content (and other entity types) have been "shared" with social/sharing services like Twitter, Google+, Facebook, etc. Also provides an API for other modules to hook into and provide their own share counts.
Also provides views integration so you can easily create a 'Most shared' block listing the most popular shared content.
This module tracks, by Ajax, how long a registered user took to read a page and the amount of time he spent on the entire site.
You can configure which content type and role should be tracked and view the report, exhibiting the total hours (or minutes/seconds) a user spent reading a page and at the entire site.
This module just track node pages and registered users. Taxonomy or views pages aren't tracked, but can be if the code is edited.
If you need to track anonymous visits, consider using Google Analytics (GA can't track registered users by its privacy terms).
What is Snoobi
Snoobi is a visitor tracking tool as well as a web analytics service. The visitor tracking collects information about your website, providing the insight necessary to ensure that your website supports your business objectives and helps in achieving them. With the guidance of Snoobi's professionals, this knowledge can be turned to action and action into results. (Source: www.snoobi.com)
Provides integration with the Mixpanel real-time analytics service.
Unlike Google Analytics, Mixpanel isn't for tracking aggregate data about page views. Instead, you send specific events to Mixpanel when users perform certain actions. This allows you to examine how users interact with your site in real-time and connects all events to the individual user who performed them (so you can contact them).
Mixpanel is great for finding ways to improve usability, studying how existing features are actually used and is especially good for startups who are trying to refine their MVP (Minimum Viable Product).
The Mail Tracking module tracks the number of recipients that read your e-mail message, click on a link in it or unsubscribe (if used in combination with Simplenews).
And there's even more: if the Simplenews and Google Analytics module have been installed you can define a source for your newsletters. This source (and some other values) will be added as utm_ parameters to all website links in your newsletter.
Visitor path module [visitorpath] tracks external referrer and onsite path information for visitors to your site (actually, extracts it from the Drupal core statistics module's accesslog table), including time on each page and an attempt at parsing what search keywords, if any, brought a person to your site.
Visitor path integrates with Webform module by automatically creating hidden webform fields for path tracking and search keyword information from the moment a user (anonymous or authenticated) enters your site to the point where they submit a form.
Specifically, Visitor path makes available for recording:
Entrance page title and URL (page on which a visitor first landed on your site)
Previous page title and URL (page on which a visitor was before recording this information, such as before submitting a form or reaching another conversion goal)
Conversion page title and URL (page on which recording ends, such as where a form is submitted and this path information is captured)
Full history (the page title, URL, and duration of time before moving to the next page for each step of the visitor's path through your site)
Source (URL that the visitor's browser reports as having been the source of sending the visitor to you – that is, the referrer aka referer, if any