History and credits¶
The project follows the Semantic Versioning specification for its version numbers. Patch-level increments indicate bug fixes, minor version increments indicate new functionality and major version increments indicate backwards incompatible changes.
Version 1.0.0 is the last to support Django < 1.7. Users of older django versions should stick to 1.0.0, and are encouraged to upgrade their setups. Starting with 2.0.0, dropping support for obsolete Django versions is not considered to be a backward-incompatible change.
- Fix a bug with the extra Google Analytics variables also pushing the _gat. flag onto the configuration array.
- Support Rating@mail.ru (Nikolay Korotkiy)
- Support Yandex.Metrica (Nikolay Korotkiy)
- Add support for extra Google Analytics variables (Steve Schwarz)
- Remove support for Reinvigorate (service shut down)
- Support Django 1.9, drop support for Django < 1.7 (Hugo Osvaldo Barrera)
- Support custom user models with an alternative username field (Brad Pitcher)
- Add Piwik user variables support (Alexandre Pocquet)
- Mark package as Python 3 compatible (Martín Gaitán)
- Fix Clickmap tracker id regular expression
- Test with Django 1.8
- Added compatibility with Python 3 (Eric Amador)
- Support Django 1.7 (Craig Bruce)
- Update Mixpanel identity code (Martín Gaitán)
- Identify authenticated users in Uservoice (Martín Gaitán)
- Add full name and email to Olark (Scott Adams)
- Add Piwik integration (Peter Bittner)
- Update HubSpot code (Craig Bruce)
- Fix typo in Intercom.io support (Steven Skoczen)
- Update UserVoice support (Martín Gaitán)
- Add support for Intercom.io (Steven Skoczen)
- Add support for GA Display Advertising features (Max Arnold)
- Add IP anonymization setting to GA tracking pixel (Tinnet Coronam)
- Include Django 1.5 in tox.ini (Tinnet Coronam)
- Add Clickmap integration (Philippe O. Wagner)
- Update mixpanel integration to latest code (Simon Ye)
- Add support for the KISSmetrics alias feature (Sandra Mau)
- Update testing code for Django 1.4 (Piet Delport)
- Add support for the UserVoice service.
- Added support for Gaug.es (Steven Skoczen)
- Fix Spring Metrics custom variables.
- Update Spring Metrics documentation.
- Fix Woopra for anonymous users (Steven Skoczen).
- Added support for the Spring Metrics service.
- Allow sending events and properties to KISSmetrics (Paul Oswald).
- Add support for the Site Speed report in Google Analytics (Uros Trebec).
- Added multiple domains support for Google Analytics.
- Fixed bug in deleted settings testing code (Eric Davis).
- Added support for the SnapEngage service.
- Updated Mixpanel code (Julien Grenier).
- Fixed compatibility with Python 2.5 (Iván Raskovsky).
- Updated Clicky tracking code to support multiple site ids.
- Fixed Chartbeat auto-domain bug when the Sites framework is not used (Eric Davis).
- Improved testing code (Eric Davis).
- Fixed MANIFEST bug that caused GoSquared support to be missing from the source distribution.
- Added support for the GoSquared service.
- Updated Clicky tracking code to use relative URLs.
- Added support for the Woopra service.
- Added chat window text customization to Olark.
MIXPANEL_API_TOKENfor compatibility with Wes Winham’s mixpanel-celery package.
- Fixed the
<script>tag for Crazy Egg.
- Added support for the Reinvigorate service.
- Added support for the Olark service.
- Added support for the Geckoboard service.
- Added support for the Performable service.
- Added support for the HubSpot service.
- Added template tags for individual services.
- First project release.
The django-analytical package was written by Joost Cassee, with contributions from Eric Davis, Paul Oswald, Uros Trebec, Steven Skoczen, Piet Delport, Sandra Mau, Simon Ye, Tinnet Coronam, Philippe O. Wagner, Max Arnold , Martín Gaitán, Craig Bruce, Peter Bittner, Scott Adams, Eric Amador, Alexandre Pocquet, Brad Pitcher, Hugo Osvaldo Barrera, Nikolay Korotkiy, Steve Schwarz, Aleck Landgraf and others.
The application was inspired by and uses ideas from Analytical, Joshua Krall’s all-purpose analytics front-end for Rails.
If you want to help out with the development of django-analytical, by posting detailed bug reports, proposing new features or other analytics services to support, or suggesting documentation improvements, use the issue tracker. If you want to get your hands dirty, great! Clone the repository, make changes and place a pull request. Creating an issue to discuss your plans is useful.