This module allows specifying tracking codes through settings (and therefore through the environment). It currently supports Google Tag Manager and Google Analytics tracking codes, but pull requests for adding support for additional trackers is very welcome!
Usage variant 1
Install the module using pip install django-privacy-killer
Add privacy_killer to INSTALLED_APPS and add the list of tracking IDS to your settings as PRIVACY_KILLER_IDS = ['GTM-****', 'UA-****', ...] (Note! This is a stupid example – specifying both GTM and UA codes is probably not what you want
Load the template tag library ({% load privacy_killer %}) and add the two tags, {% privacy_killer_head %} near the <head> of your site, and {% privacy_killer_body %} near the <body> element.
Usage variant 2
Do not use this module, and also do not use any trackers at all.
Supported trackers
Google Tag Manager (GTM-****)
Google Universal Analytics (UA-****)
Facebook Pixel (Prefix the **** code with FBQ- when specifying PRIVACY_KILLER_IDS)
Metadata
Release files for django-privacy-killer 0.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-privacy-killer-0.3.0.tar.gz | 5.2 kB | Without provenance | Details for django-privacy-killer-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_privacy_killer-0.3.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for django_privacy_killer-0.3.0-py2.py3-none-any.whl |
Total release size: 12.4 kB
Release files / django-privacy-killer-0.3.0.tar.gz
| Download URL | django-privacy-killer-0.3.0.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
588030b8f8e7d6df9de38ce036b3800243aac40997eb621230d7a30e41acda10
|
|
BLAKE2b-256 checksum How to use checksums |
3356f9830767bcaafb115b7504f1ad7364f7ab8ff892864adc973393822ac4e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.6.8
|
Release files / django_privacy_killer-0.3.0-py2.py3-none-any.whl
| Download URL | django_privacy_killer-0.3.0-py2.py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
6e271e647cf1c21190f009ae31edeb2d589d84de2d5ae4b75646790c89d74a96
|
|
BLAKE2b-256 checksum How to use checksums |
4382e4536b9da6ad4e003cac9be98c49820146839601da3d451253aec646f3bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.6.8
|
Security for django-privacy-killer 0.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.