Jmbo Analytics
Jmbo analytics brings the power of Google Analytics to your Django projects
Required
You have to add jmbo_analytics to you INSTALLED_APPS
You have to specify a Google Analytics tracking code.
where xxx is your tracking code:
JMBO_ANALYTICS = {
'google_analytics_id': 'xxx',
}
Usage
jmbo-analytics offers you two ways to add tracking to your pages.
1. HTML tag
Using <img /> and putting it in your base.html:
{% load jmbo_analytics_tags %}
<div style="display: none;">
<img src="{% google_analytics %}" width="0" height="0" />
</div>
2. Middleware and Celery
Using Django’s middleware you can process every request and use Celery to make the request to Google Analytics. Note that this does not work behind a reverse caching proxy:
MIDDLEWARE_CLASSES = ( 'jmbo_analytics.middleware.GoogleAnalyticsMiddleware', )
You may have to add jmbo_analytics to your CELERY_IMPORTS:
CELERY_IMPORTS = ('jmbo_analytics.tasks')
You may also specify paths that will be excluded when tracking:
GOOGLE_ANALYTICS_IGNORE_PATH = ['/health/', ]
Changelog
0.2.2
Fixed incorrect header key.
0.2.1
Send correctly named header.
0.2
Use requests library because it can drill through HTTP proxies.
0.1
Simplify dependencies.
Make transparent GIF method asynchronous.
0.0.4
Better packaging.
0.0.3
Fork, rename, re-license from panomena-analytics.
Metadata
Release files for jmbo-analytics 0.2.2
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 |
|---|---|---|---|---|
| jmbo-analytics-0.2.2.tar.gz | 11.0 kB | Without provenance | Details for jmbo-analytics-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jmbo_analytics-0.2.2-py2.7.egg | Legacy Egg format | - | - | Details for jmbo_analytics-0.2.2-py2.7.egg |
Total release size: 28.5 kB
Release files / jmbo-analytics-0.2.2.tar.gz
| Download URL | jmbo-analytics-0.2.2.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ac04e4032bac27b622eb7ed941b4bf2a7c695bfae61830f8ef40a9be7b1176d
|
|
BLAKE2b-256 checksum How to use checksums |
3f023ed82c068b9ff75ab03419389ebc8cd91e0cf4699b7f2e0738dcf6b64e0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / jmbo_analytics-0.2.2-py2.7.egg
| Download URL | jmbo_analytics-0.2.2-py2.7.egg |
|---|---|
| Size | 17.5 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
bc00a5de6085f506e662d83275f62d833f09622b8052435c69716a0a19e7d344
|
|
BLAKE2b-256 checksum How to use checksums |
bc1bdeab44887492e17bc7f4e0a913694fe67495e1b4b6056239208b482e1cc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for jmbo-analytics 0.2.2
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.