django-sitemetrics
https://github.com/idlesign/django-sitemetrics
What's that
Reusable application for Django providing easy means to integrate site metrics counters into your sites.
Built-in site metrics providers
-
Yandex Metrika — https://metrika.yandex.ru/
Provider alias:
yandex -
Google Analytics — https://www.google.com/analytics/
Provider alias:
google -
Openstat — https://www.openstat.com/
Provider alias:
openstat
How to use
- Add the
sitemetricsapplication toINSTALLED_APPSin your settings file (usuallysettings.py) - Add
{% load sitemetrics %}tag to the top of a template (usually base template, e.g._base.html)
Then you have two options to add metrics counter code to your page:
-
Use
four argumentssitemetrics tag notation:{% sitemetrics by google for "UA-000000-0" %}Here:
googleis a metrics provider alias;UA-000000-0— metrics counter keycode.That is how you put Google Analytics counter code (with
UA-000000-0keycode) into page. -
Use
no argumentssitemetrics tag notation:{% sitemetrics %}That is how you put all counter codes registered and active for the current site.
Client codes are registered with sites through Django Admin site interface.
Admin site and Sites from Django contribs are required for this approach to work.
Use
./manage.py migrateto install sitemetrics tables into your database.
Documentation
Metadata
Release files for django-sitemetrics 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_sitemetrics-1.3.0.tar.gz | 9.0 kB | Without provenance | Details for django_sitemetrics-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_sitemetrics-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for django_sitemetrics-1.3.0-py3-none-any.whl |
Total release size: 23.2 kB
Release files / django_sitemetrics-1.3.0.tar.gz
| Download URL | django_sitemetrics-1.3.0.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1324b16af54a62c234cb7b7ac27fb3f3a891bff92a2b96058359877a5f09c4d
|
|
BLAKE2b-256 checksum How to use checksums |
b0a56c150bb46d28bb04e189d04cb75ebcf1a66a9a2aa2eb187104d8b83ecbe2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / django_sitemetrics-1.3.0-py3-none-any.whl
| Download URL | django_sitemetrics-1.3.0-py3-none-any.whl |
|---|---|
| Size | 14.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
263b0b06431f4c74d7c10908d089587cc5a9aa2d2b9f2fdbb7a749481da5baf7
|
|
BLAKE2b-256 checksum How to use checksums |
121e8014625282fa414dffeaabb7031b51b8b118985cf353127ad25ee467dabc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for django-sitemetrics 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.