Django Amplitude
Integration between Django and Amplitude.com to help send events via the Amplitude HTTP API (v2)
Quick start
Installation
pip install django-amplitude
Add amplitude to your INSTALLED_APPS. If they are not already the Django sessions app must also be added:
INSTALLED_APPS = [
...
'django.contrib.sessions',
...
'amplitude',
]
If you do not have it already you must also add the Django django.contrib.sessions.middleware.SessionMiddleware. Then add the ampliturde SessionInfo middleware after the SessionMiddleware:
MIDDLEWARE = [
...
'django.contrib.sessions.middleware.SessionMiddleware',
...
'amplitude.middleware.SessionInfo',
]
Now set your Amplitude API key and user / group options in your settings.py:
# Settings > Projects > <Your project> > General > API Key
AMPLITUDE_API_KEY = '<amplitude-project-api-key>'
# You can also choose if you want to include user and group data (Default False)
AMPLITUDE_INCLUDE_USER_DATA = False
AMPLITUDE_INCLUDE_GROUP_DATA = False
Note: If you want to include user or group data you must ensure the Django auth is setup correctly. This includes adding django.contrib.auth and django.contrib.contenttypes to INSTALLED_APPS and django.contrib.auth.middleware.AuthenticationMiddleware to MIDDLEWARE.
For more information on the above settings see the configuration settings section.
Usage
Page view events
If you want to send an event to Amplitude on every page view you can use the django-amplitude SendPageViewEvent middleware to your MIDDLEWARE in your Django settings.
This will automatically create an event called Page view with all the information it's possible to pull from the Django request object such as URL path and parameters, user agent info, IP info, user info etc.
It must be placed after the amplitude.middleware.SessionInfo middleware:
MIDDLEWARE = [
'django.contrib.sessions.middleware.SessionMiddleware',
...
'amplitude.middleware.SessionInfo',
'amplitude.middleware.SendPageViewEvent',
]
While using SendPageViewEvent if there are certain URLs that you do not want to update Amplitude with you can use the AMPLITUDE_IGNORE_URLS setting. This setting take a list of relative urls or URL names. Relative URLS most match exactly so need to start with a forward slash (/)
AMPLITUDE_IGNORE_URLS = ['my_url_name', '/testurl']
Sending events manually
If you want to send your own events:
from amplitude import Amplitude
amplitude = Amplitude()
event_data = amplitude.build_event_data(
event_type='Some event type',
request=request,
)
amplitude.send_events([event_data])
The above request will include URL and HTTP header info in the event_properties. If you want to override the event properties you can pass them through to build_event_data:
event_data = amplitude.build_event_data(
event_type='User purchase',
request=request,
event_properties={'products': ['laptop', 'phone']}
)
build_event_data missing event data keys
The build_event_data method (and in extension the SendPageViewEvent middleware) currently does not send the following keys from UploadRequestBody type in Amplitude HTTP API (v2):
- event_id
- app_version
- carrier
- price
- quantity
- revenue
- productId
- revenueType
- idfa
- idfv
- adid
- android_id
- dma
- insert_id
If you want to record an event in Amplitude with any of these keys you must use build and send your own event data using amplitude.build_event_data where you can pass any of the above as kwargs:
amplitude = Amplitude()
event_data = amplitude.build_event_data(
event_type='Some event type',
request=request,
app_version='1.0.0',
)
amplitude.send_events([event_data])
Building you own event
If you are not happy with the data from build_event_data you can build you own event data based on the UploadRequestBody type in Amplitude HTTP API (v2). If you want to do this There are a few helper functions to build different parts of the event data from the Django request object:
amplitude.event_properties_from_request(request) # Gets URL and HTTP header data
amplitude.device_data_from_request(request) # Gets device info from user agent
amplitude.user_properties_from_request(request) # Gets info from user model
amplitude.group_from_request(request) # Gets the list of groups a user is in
amplitude.location_data_from_ip_address(ip_address) # Gets location data from IP if GeoIP2 is setup
user_properties_from_requestwill return an empty dict ifAMPLITUDE_INCLUDE_USER_DATAisFalsegroup_from_requestwill return an empty dict ifAMPLITUDE_INCLUDE_GROUP_DATAisFalse
Configuration settings
Below are the different settings that can be overridden. To do so place the setting into your settings.py.
# This variable is required when amplitude is added to INSTALLED_APPS
AMPLITUDE_API_KEY = '<amplitude-project-api-key>'
# If the users Django user information is included in the Amplitude event.
# This includes - username, email, full_name, is_staff, is_superuser
AMPLITUDE_INCLUDE_USER_DATA = False
# If the groups the user is a member of is included in the Amplitude event.
# A list of the group names will be sent in the request.
AMPLITUDE_INCLUDE_GROUP_DATA = False
# A list of URLs which `SendPageViewEvent` middleware should not run for.
# Each item in the list can be either a URL or url name
AMPLITUDE_IGNORE_URLS = ['home', '/please/ignore/']
# The minimum permitted length for user_id & device_id fields
# https://developers.amplitude.com/docs/http-api-v2#properties-2
AMPLITUDE_MIN_ID_LENGTH = None
Metadata
Release files for django-amplitude 0.8.1
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_amplitude-0.8.1.tar.gz | 9.2 kB | Without provenance | Details for django_amplitude-0.8.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_amplitude-0.8.1-py3-none-any.whl | Python 3 | none | any | Details for django_amplitude-0.8.1-py3-none-any.whl |
Total release size: 18.4 kB
Release files / django_amplitude-0.8.1.tar.gz
| Download URL | django_amplitude-0.8.1.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
01644b7c45ef94a377c0149f0e6787e5b856c63b0bbe994291644d10c9954a64
|
|
BLAKE2b-256 checksum How to use checksums |
d6562e4fb0498b4e085a9525510959a102968835de88ae2ec8e4350ef5e42184
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.10.5 Darwin/22.5.0
|
Release files / django_amplitude-0.8.1-py3-none-any.whl
| Download URL | django_amplitude-0.8.1-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be472ba6be88b8679219ddcfcb8532b476edb5c4241453d823f3c30d109904ea
|
|
BLAKE2b-256 checksum How to use checksums |
5842e08af7451eb9c131dc13878a5b21de74238c0166943e90701f7602ebf57f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.10.5 Darwin/22.5.0
|
Security for django-amplitude 0.8.1
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.