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.
The Postmark module allows the administrator to switch the standard SMTP library over to use the third party Postmark API to send out emails from their site. An account with Postmark is required to use this module.
IMPORTANT NOTICE FOR DRUPAL 7 USERS
On April 5, 2013, version 0.5 of the Postmark PHP library was released. Currently only the 7.x-1.x-dev version of Postmark supports the 0.5 library. If you download the 7.x-1.2 release of Postmark, use the 0.4.5 library available here:
Bit.ly for Drupal provides a rich API that other modules can use to access bit.ly functionality. This module integrates with bit.ly's OAuth 2.0 implementation, and requires a simple application to bit.ly for access.
This release contains only basic functionality, I am looking to the community to help with extending and expanding this module.
This project introduces a vendor independent framework for deeply monitoring Drupal and all its projects / modules. It provides a 360 degree perspective on Drupal system health, being a critical piece for true enterprise Drupal platforms.
Our goal is to make monitoring an affordable and well established standard feature. These days, every website is somehow mission critical and the era of lazy-/unmonitored enterprise applications need to have an end.
With this vendor independent definition, we recommend every contrib module to provide own sensors that allow us to measure module health by default.
The project monitoring is no monitoring application on its own. It provides a lightweight sensor definition framework with a set of sensors that can be collected by any monitoring product. Integrations into the most popular Open Source products Nagios / Icinga (monitoring system) and Munin (trends monitoring grapher) will be available out of the box. Integrating additional monitoring products is easy.
The base platform for sensor definition is production ready. Publishing of the integration into products and contrib modules will follow soon. Contact us if you need it NOW and want to support development.
There are no known major issues.
A list will follow.
This module has a pre-release version for Drupal 8. To find out more, follow this issue or download below.
The User Visits Advanced module is a contrib module for the User Visits module. It is extremely useful for social networking sites who wish to provide their users with statistics about the number of times a the users profile page is being viewed and by which other users. See the provided screen shot how the block of this module can look like.
This module comes with its own database table to store statistics per user profile (uid). At cron time, the data from the user_visits table is collected, aggregated and stored in the user_visits_adv table. It stores
the total number of visits per uid
the number of visits of the X past days per uid
the most recent visitors uids of the past Y hours
Enable the user_visits_adv module
Go to admin/user/user_visits and the advanced fieldset
You can choose to enable the two blocks: My recent visitors adv & My visitors history adv
Configure each block for the amount of data which should be handed over to the theming functions
The My visitors history adv block can be themed by overriding the following function
* Theme function for history block
* @param $history is array with the views data of the past X days.
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).
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.
A simple module that tracks downloads of files added through CCK/Fields by asking anonymous users to enter their email address. Returning anonymous users are tracked using a cookie. A tracking interface shows email address and user account information for tracked files downloaded on the site.
Why only have users enter their email address? Email addresses are a unique and easy way to identify users, and the barrier for entry is lower than actually registering for the site.
This module provides "like" and "dislike" widgets for contents inside Drupal, making it easiers to promote features as the one seem on many social network websites.
Technically speaking, the module provides 2 tags for Voting API, "like" and "dislike", working in a different way from Vote Up/Down, that is like a "plus or minus" approach. Likes are separate from Dislikes here.
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).
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.
Bounce Convert allows you to run "exit-intent" campaigns to show modal webforms to visitors who are leaving your website (determined by mouse cursor position and velocity). This allows you to get an extra pageview from visitors that would otherwise have been lost, and provides an opportunity to make offers, collect email addresses, poll visitors, or ask them why they are leaving. One common technique is to provide a special offer which requires the user to sign up for your newsletter, thereby "capturing" the visitor as they are leaving, instead of losing them.
The LiveInternet module integrates Drupal with LiveInternet statistic service, which most popular in Russia and post-Soviet states. This service allows to track visitors, page views, referring sites, the most popular pages, etc. The image with LiveInternet logotype have to be on every tracking page in free version of counter.
Syslog Access compliments the core Syslog module by routing access statistics and logs to syslog (in addition to Syslog's routing of Watchdog), allowing you to use your favorite log management software or service (like Splunk, Loggly, etc.) to visualize, analyze, and manage your access log.
You can also disable database logging to help scale your Drupal installation.