django-pixels
=============================
Tracking pixels made easy
Features
----------
* Built-in view to serve a pixel response
* Compose pixel tracking urls with different type IDs
* Route tracking requests to functions using type IDs
Implementation Notes with Short Examples
----------
Install django-pixels::
pip install django-pixels
Mount pixel tracking URL patterns:
.. code-block:: python
urlpatterns = [
...
url(r'^tracker/', include('django_pixels.urls', namespace="pixels")),
...
]
Get the general pixel tracking url (This serves a transparent pixel as the response):
.. code-block:: python
from django.core.urlresolvers import reverse
tracking_url = reverse('pixels:pixel') # given you have mounted django_pixels urls with namespace='pixels'
Get the tracking url with no-content(204) response (This serves an empty response with code 204):
.. code-block:: python
from django.core.urlresolvers import reverse
tracking_url = reverse('pixels:pixel-204') # given you have mounted django_pixels urls with namespace='pixels'
Generate a pixel tracking url with type 1:
.. code-block:: python
from django_pixels import utils
utils.compose_pixel_url(tracking_url, 1)
Write a function to handle tracking calls with type 1:
.. code-block:: python
def track_emails(request):
# handle tracking with the passed HttpRequest instance
Register the function to handle tracking calls with type 1:
.. code-block:: python
from django_pixels import handlers
handlers.register(1, track_emails)
Or mark a function to handle tracking calls with type 2:
.. code-block:: python
from django_pixels import handlers
@handlers.track(type_id=2)
def track_emails(request):
# handle tracking with the passed HttpRequest instance
Settings
----------
* PIXELS_TYPE_PARAMETER_NAME - Change the parameter name used for tracking type
Credits
-------
Tools used in rendering this package:
* Cookiecutter_
* `cookiecutter-djangopackage`_
.. _Cookiecutter: https://github.com/audreyr/cookiecutter
.. _`cookiecutter-djangopackage`: https://github.com/pydanny/cookiecutter-djangopackage
History
-------
0.1 (2016-12-10)
++++++++++++++++++
* First release on PyPI.
Metadata
Release files for django-pixels 0.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 |
|---|---|---|---|---|
| django-pixels-0.2.tar.gz | 4.8 kB | Without provenance | Details for django-pixels-0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_pixels-0.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for django_pixels-0.2-py2.py3-none-any.whl |
Total release size: 11.4 kB
Release files / django-pixels-0.2.tar.gz
| Download URL | django-pixels-0.2.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
555f2948a3a40f890eb3b9218e2fce5cd7b51f9a7644f04d914589820c55d146
|
|
BLAKE2b-256 checksum How to use checksums |
efd5b82074473ad2b06e7015fe6b4c242f6af96414caa3a3e73140f33611deb6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_pixels-0.2-py2.py3-none-any.whl
| Download URL | django_pixels-0.2-py2.py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
fb469d27351a996a17788944498e1f7e0b244f64699a8154acc718e71995f86a
|
|
BLAKE2b-256 checksum How to use checksums |
cb045ecab13a5e08ef6a07293b31cd1d08df30f12632fa18bdb9526260e5ae92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-pixels 0.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.