Django Email Analytics adds Google Analytics tracking to emails sent with Django. It provides a wrapper for Django’s standard email backends.
Installation and Setup
Install with pip:
pip install django-email-analytics
Then set the email backend in the settings.py file.
EMAIL_BACKEND = 'emailanalytics.backends.AnalyticsEmailBackend'
Set EMAIL_ANALYTICS_BACKEND to the value you previously used for EMAIL_BACKEND. Or if EMAIL_BACKEND was unset, you can leave EMAIL_ANALYTICS_BACKEND unset as well. This will chain the email backends so that django-email-analytics will use your original backend to send messages.
Options
By default, URLs will be replaced only when the mimetype is text/html and the URL occurs within a href attribute.
Set EMAIL_ANALYTICS_REPLACE_TXT to True if you would like to also replace urls occuring in text emails.
Tracking details
If a URL already contains tracking parameters, they are left unchanged.
Otherwise, URLs are tagged with the following parameters:
utm_source is set to the subject of the email
utm_medium is set to email
utm_campaign is set to webapp
See here for a description of the tracking parameters.
Metadata
Release files for django-email-analytics 0.4
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 | |
|---|---|---|---|---|
| django-email-analytics-0.4.tar.gz | 4.4 kB | Without provenance | Details |
Release files / django-email-analytics-0.4.tar.gz
| Download URL | django-email-analytics-0.4.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0a951237a53ba32a3a4731940f7a1b528e36fa14c413a1e1938d36b8dcc24f4
|
|
BLAKE2b-256 checksum How to use checksums |
df37980dc8e9918b93370316934bd53928cdec6d747a2ba40ba2c2d78520f02d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-email-analytics 0.4
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.