Admob server-side verification for Django projects
Project description
Django Admob server-side verification (SSV)
A Django app providing a view for handling Admob server-side verification callbacks. Successfully verified callbacks trigger a custom Django signal. Apps in your project may listen to that signal and reward the user based on the information received via the callback.
Taken from the Admob SSV documentation:
Server-side verification callbacks are URL requests, with query parameters expanded by Google, that are sent by Google to an external system to notify it that a user should be rewarded for interacting with a rewarded video ad. Rewarded video SSV (server-side verification) callbacks provide an extra layer of protection against spoofing of client-side callbacks to reward users.
Installation
pip install django-admob-ssv
Add a path
for the admob_ssv.views.AdmobSSVView
view to your urlpatterns
.
from django.urls import path
from admob_ssv.views import AdmobSSVView
urlpatterns = [
path('admob-ssv/', AdmobSSVView.as_view()),
]
Listen to the admob_ssv.signals.valid_admob_ssv
signal and make sure
you connect your receiver properly, otherwise it won't
get called. Take a look at the "Where should this code live?" box.
from django.dispatch import receiver
from admob_ssv.signals import valid_admob_ssv
@receiver(valid_admob_ssv)
def reward_user(sender, query, **kwargs):
ad_network = query.get('ad_network')
ad_unit = query.get('ad_unit')
custom_data = query.get('custom_data')
# ...
Reference the official Admob SSV documentation for a list of all SSV callback parameters.
Settings
You may optionally set the following options in your Django settings.py
file.
The code snippet below shows the default values used.
from datetime import timedelta
ADMOB_SSV_KEY_SERVER_URL = "https://www.gstatic.com/admob/reward/verifier-keys.json",
ADMOB_SSV_KEYS_CACHE_TIMEOUT = timedelta(days=1)
ADMOB_SSV_KEYS_CACHE_KEY = "admob_ssv.public_keys"
Usage without Django signals
If you don't want to use Django signals, you may subclass the
admob_ssv.views.AdmobSSVView
view and override the handle_valid_ssv
method.
Note that unless you call super().handle_valid_ssv(request)
,
the admob_ssv.signals.valid_admob_ssv
signal won't be sent.
from admob_ssv.views import AdmobSSVView
class MyAdmobSSVView(AdmobSSVView):
def handle_valid_ssv(self, request) -> None:
query = request.GET.dict()
ad_network = query.get('ad_network')
ad_unit = query.get('ad_unit')
custom_data = query.get('custom_data')
# ...
Finally add a path
for your custom view to your urlpatterns
.
from django.urls import path
from my_app.views import MyAdmobSSVView
urlpatterns = [
path('admob-ssv/', MyAdmobSSVView.as_view()),
]
Using a custom ECDSA library
This project uses the ecdsa Python package to verify the signature of incoming Admob SSV callbacks.
If you want to use a different ECDSA library, you may subclass the
admob_ssv.views.AdmobSSVView
view and override the verify_signature
method.
from admob_ssv.views import AdmobSSVView
class MyAdmobSSVView(AdmobSSVView):
def verify_signature(
self, public_key: str, signature: bytes, content: bytes
) -> bool:
# Verify the signature using your custom ECDSA library.
# Return True if the signature is valid, False otherwise.
pass
Finally add a path
for your custom view to your urlpatterns
.
from django.urls import path
from my_app.views import MyAdmobSSVView
urlpatterns = [
path('admob-ssv/', MyAdmobSSVView.as_view()),
]
Verify that callbacks are coming from Google
According to the AdMob SSV FAQ section one could do the following:
Use reverse DNS lookup to verify that SSV callbacks originate from Google.
Depending on your setup, possibly behind a reverse proxy, it's not trivial to determine the origin IP address of a callback.
Checking the wrong IP address could lead to callbacks being ignored. That's why we decided to leave callback origin verification up to you.
Tip: It appears to be sufficient to check whether the callback contains one of your ad unit ids, which is covered by the signature.
Example project
Take a look at our Django example project under tests/project
.
You can run it by executing these commands:
poetry install
poetry run python tests/project/manage.py migrate
poetry run python tests/project/manage.py createsuperuser
poetry run python tests/project/manage.py runserver
Live testing
The example project can be used to test Admob server-side verification
live from your local machine. You may use a service like
ngrok to forward requests from the internet to
your local machine and the Django webserver running at port 8000
.
ngrok http 127.0.0.1:8000
You are now ready to send test Admob server-side verification callbacks from the Admob console.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file django_admob_ssv-3.2.0.tar.gz
.
File metadata
- Download URL: django_admob_ssv-3.2.0.tar.gz
- Upload date:
- Size: 5.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: poetry/1.8.4 CPython/3.12.7 Linux/6.11.6-arch1-1
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 295c6272af4acab733ff94f5425bcd9decfbd6d058aaa79c12c36332a1b726d0 |
|
MD5 | ac2b07f9b623a770ab975571c789e006 |
|
BLAKE2b-256 | 606ce9a349cbc436652998b294bc19eb3685040672853ed507028b0151398c9c |
File details
Details for the file django_admob_ssv-3.2.0-py3-none-any.whl
.
File metadata
- Download URL: django_admob_ssv-3.2.0-py3-none-any.whl
- Upload date:
- Size: 6.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: poetry/1.8.4 CPython/3.12.7 Linux/6.11.6-arch1-1
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 6c21c6bf074baffce95573987e19342d7cb266008255a59da7840eb0da616b42 |
|
MD5 | 332772e2e45093c9e1cd20c204f028cc |
|
BLAKE2b-256 | b3faa233fae004a09d4ab4e69908ce08d5c8718fa1c660460e64fedcc41abd9c |