django-plausible-iplweb 0.6.0__tar.gz

django_plausible_iplweb-0.6.0/.github/workflows/ci.yml

@@ -0,0 +1,84 @@
+name: CI
+
+on: [pull_request, push]
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        # Derived from requires-python (>=3.10) + Django floor (>=5.2) +
+        # canonical Django x Python compatibility. Django 6.0 needs Python >=3.12.
+        include:
+          # Django 5.2 LTS
+          - { python-version: "3.10", django-version: "5.2" }
+          - { python-version: "3.11", django-version: "5.2" }
+          - { python-version: "3.12", django-version: "5.2" }
+          - { python-version: "3.13", django-version: "5.2" }
+          # Django 6.0
+          - { python-version: "3.12", django-version: "6.0" }
+          - { python-version: "3.13", django-version: "6.0" }
+          - { python-version: "3.14", django-version: "6.0" }
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # full history so setuptools-scm can derive the version
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86 # v5
+
+      - name: Set up Python ${{ matrix.python-version }}
+        run: uv python install ${{ matrix.python-version }}
+
+      - name: Install dependencies (project + Django ${{ matrix.django-version }})
+        run: |
+          uv sync --all-extras
+          uv pip install "django~=${{ matrix.django-version }}.0"
+
+      - name: Run tests
+        run: uv run pytest --verbose --cov plausible/ --cov-report term tests/
+
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86 # v5
+
+      - name: Set up Python
+        run: uv python install 3.14
+
+      - name: Install dependencies
+        run: uv sync --all-extras
+
+      - name: Lint with ruff
+        run: uv run ruff check . || true
+
+      - name: Check formatting with ruff
+        run: uv run ruff format --check . || true
+
+      - name: Type-check with mypy
+        run: uv run mypy plausible tests
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # setuptools-scm needs tags/history
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86 # v5
+
+      - name: Build package
+        run: uv build
+
+      - name: Check package metadata
+        run: uv run --with twine twine check dist/*

django_plausible_iplweb-0.6.0/.github/workflows/deploy.yml

@@ -0,0 +1,30 @@
+name: Upload Python Package
+
+on:
+  release:
+    types: [created]
+
+permissions:
+  contents: read
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # full history + tags so setuptools-scm derives the version
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86 # v5
+
+      - name: Build package
+        run: uv build
+
+      # NOTE: still using a PyPI token (secrets.PYPI_PASSWORD). Consider migrating
+      # to PyPI Trusted Publishing (OIDC) so no token needs to live in repo secrets.
+      - name: Publish to PyPI
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
+        run: uv run --with twine twine upload dist/*

django_plausible_iplweb-0.6.0/.gitignore

@@ -0,0 +1,135 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# uv (library: lockfile not committed)
+uv.lock
+
+# Ruff
+.ruff_cache/
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/

django_plausible_iplweb-0.6.0/.pre-commit-config.yaml

@@ -0,0 +1,28 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-added-large-files
+      - id: detect-private-key
+
+  - repo: https://github.com/asottile/pyupgrade
+    rev: v3.21.2
+    hooks:
+      - id: pyupgrade
+        args: [--py310-plus]
+
+  - repo: https://github.com/adamchainz/django-upgrade
+    rev: 1.30.0
+    hooks:
+      - id: django-upgrade
+        args: [--target-version, "5.2"]
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.15.17
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format

django_plausible_iplweb-0.6.0/LICENSE

@@ -0,0 +1,29 @@
+BSD 3-Clause License
+
+Copyright (c) 2021, Jake Howard
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

django_plausible_iplweb-0.6.0/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.4
+Name: django-plausible-iplweb
+Version: 0.6.0
+Summary: Django module to provide easy Plausible integration, with Wagtail support
+Author: Jake Howard
+Maintainer-email: Michał Pasternak <michal.dtz@gmail.com>
+License-Expression: BSD-3-Clause
+Project-URL: Homepage, https://github.com/mpasternak/django-plausible-iplweb
+Project-URL: Repository, https://github.com/mpasternak/django-plausible-iplweb
+Project-URL: Issues, https://github.com/mpasternak/django-plausible-iplweb/issues
+Keywords: django,plausible,wagtail,analytics
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Web Environment
+Classifier: Framework :: Django
+Classifier: Framework :: Django :: 5.2
+Classifier: Framework :: Django :: 6.0
+Classifier: Framework :: Wagtail
+Classifier: Framework :: Wagtail :: 6
+Classifier: Framework :: Wagtail :: 7
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Internet :: WWW/HTTP
+Classifier: Topic :: Software Development
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: Django>=5.2
+Provides-Extra: wagtail
+Requires-Dist: wagtail>=7.0; extra == "wagtail"
+Provides-Extra: dev
+Requires-Dist: django-plausible-iplweb[wagtail]; extra == "dev"
+Requires-Dist: ruff; extra == "dev"
+Requires-Dist: mypy; extra == "dev"
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: pytest-django; extra == "dev"
+Requires-Dist: pytest-cov; extra == "dev"
+Requires-Dist: pre-commit; extra == "dev"
+Dynamic: license-file
+
+# django-plausible-iplweb
+
+[![CI](https://github.com/mpasternak/django-plausible-iplweb/actions/workflows/ci.yml/badge.svg)](https://github.com/mpasternak/django-plausible-iplweb/actions/workflows/ci.yml)
+![PyPI](https://img.shields.io/pypi/v/django-plausible-iplweb.svg)
+![Python](https://img.shields.io/badge/python-3.10%20%7C%203.11%20%7C%203.12%20%7C%203.13%20%7C%203.14-blue)
+![Django](https://img.shields.io/badge/django-5.2%20%7C%206.0-blue)
+![PyPI - Status](https://img.shields.io/pypi/status/django-plausible-iplweb.svg)
+![PyPI - License](https://img.shields.io/pypi/l/django-plausible-iplweb.svg)
+
+
+Django module to provide easy [Plausible](https://plausible.io/) integration, with [Wagtail](https://wagtail.io/) support.
+
+## Installation
+
+```
+pip install django-plausible-iplweb
+```
+
+Then simply add `plausible` to `INSTALLED_APPS`.
+
+## Usage
+
+`django-plausible-iplweb` provides a `plausible` template tag that emits Plausible's
+current per-site tracking script. Each Plausible site now has its **own script URL**
+(e.g. `https://plausible.io/js/pa-XXXXXXXX.js`) — there is no `data-domain` attribute
+any more. Copy the script URL from your Plausible dashboard (**Site Settings → General →
+Site Installation**) into `PLAUSIBLE_SCRIPT_URL`, then place the tag in your `<head>`:
+
+```html
+{% load plausible %}
+
+{% plausible %}
+```
+
+With `PLAUSIBLE_SCRIPT_URL = "https://plausible.io/js/pa-XXXXXXXX.js"`, this renders:
+
+```html
+<script defer src="https://plausible.io/js/pa-XXXXXXXX.js"></script>
+<script>
+  window.plausible = window.plausible || function () { (window.plausible.q = window.plausible.q || []).push(arguments) };
+  plausible.init({"autoCapturePageviews": false});
+  (function () {
+    var path = window.location.pathname;
+    var masks = [];
+    for (var i = 0; i < masks.length; i++) {
+      path = path.replace(new RegExp(masks[i].pattern, masks[i].flags || "g"), masks[i].replacement);
+    }
+    var url = window.location.origin + path + window.location.search;
+    plausible("pageview", { url: url });
+  })();
+</script>
+```
+
+Automatic pageview capture is **disabled** (`autoCapturePageviews: false`) so the package
+can send a single, optionally-masked pageview itself (see [URL masking](#url-masking)).
+
+If `PLAUSIBLE_SCRIPT_URL` is empty (the default), the tag renders nothing — a convenient
+way to switch analytics off in development.
+
+### Configuration
+
+All configuration lives in `settings.py`:
+
+| Setting | Default | Purpose |
+|---|---|---|
+| `PLAUSIBLE_SCRIPT_URL` | `""` | Full per-site script URL from your Plausible dashboard. Empty → tag renders nothing. |
+| `PLAUSIBLE_INIT_OPTIONS` | `{"autoCapturePageviews": False}` | Dict passed (as JSON) to [`plausible.init(...)`](https://plausible.io/docs/script-extensions). Add any init option here, e.g. `{"autoCapturePageviews": False, "hashBasedRouting": True}`. |
+| `PLAUSIBLE_URL_MASKS` | `[]` | Ordered list of client-side path-masking rules (see below). |
+| `PLAUSIBLE_KEEP_QUERY_STRING` | `True` | Append `location.search` to the reported URL (keeps `utm_*`/`ref` for acquisition reports). Set `False` to drop the query string entirely. |
+
+You can also pass the script URL at call time, e.g. to use a different site on one page:
+
+```html
+{% plausible script_url="https://plausible.io/js/pa-OTHER.js" %}
+```
+
+### URL masking
+
+Plausible records the page URL. If your paths contain identifiers (invitation codes,
+user IDs, UUIDs, …) those would leak into your analytics. `PLAUSIBLE_URL_MASKS` lets you
+redact them **client-side** before the pageview is sent. Each rule is applied to
+`location.pathname` in order via JavaScript's
+[`String.replace(new RegExp(pattern, flags), replacement)`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replace):
+
+```python
+PLAUSIBLE_URL_MASKS = [
+    # Mask invitation/passphrase codes:  /i/<passphrase>  ->  /i/__code__
+    {"pattern": r"^/i/[^/]+", "replacement": "/i/__code__"},
+    # Mask UUIDs anywhere in the path:  /<uuid>  ->  /__id__
+    {"pattern": r"/[0-9a-f-]{36}", "replacement": "/__id__", "flags": "gi"},
+    # Mask numeric ids:  /123  ->  /__id__
+    {"pattern": r"/\d+", "replacement": "/__id__"},
+]
+```
+
+`pattern` and `flags` are **JavaScript** regular-expression syntax (the rules run in the
+browser). `flags` defaults to `"g"`. The patterns above are examples — adapt them to your
+own routes; the default (`[]`) applies no masking.
+
+> **Caveat:** like Plausible's own [redaction guidance](https://plausible.io/docs/custom-locations),
+> this masking runs once when the page loads. It may not behave as expected in
+> single-page applications or with hash-based routing, where `location` changes
+> without a full page load.
+
+### Overriding the rendered markup
+
+The snippet is rendered from the `plausible/plausible.html` template. To fully customise
+it, shadow that path in your own project's templates directory.
+
+## Usage with Wagtail
+
+`django-plausible-iplweb` also provides an optional [Wagtail](https://wagtail.org)
+integration that lets editors set the script URL **per site** through the Wagtail admin.
+Add `plausible.contrib.wagtail` to `INSTALLED_APPS` and run `migrate`.
+
+Configuration is done through the "Plausible Analytics"
+[setting](https://docs.wagtail.org/en/stable/reference/contrib/settings.html):
+
+- `script_url`: the full per-site Plausible script URL. Blank (the default) → nothing is rendered for that site.
+
+Masking (`PLAUSIBLE_URL_MASKS`), init options, and query-string handling are still
+configured globally via the Django settings above.
+
+Load `plausible_wagtail` rather than `plausible`; the tag itself is still `plausible`:
+
+```html
+{% load plausible_wagtail %}
+
+{% plausible %}
+```
+
+## Migrating from 0.5.x
+
+Version 0.6.0 is a clean break to match Plausible's new tracker. Update your settings:
+
+| Old (0.5.x) | New (0.6.0) |
+|---|---|
+| `PLAUSIBLE_DOMAIN` + `PLAUSIBLE_SCRIPT_NAME` | `PLAUSIBLE_SCRIPT_URL` (the full script URL from your dashboard) |
+| `data-domain` (request host / `site_domain`) | *(gone — the site is identified by the script URL)* |
+| `{% plausible site_domain=… plausible_domain=… script_name=… %}` | `{% plausible %}` (optionally `script_url=…`) |
+| Wagtail `site_domain` / `plausible_domain` / `script_name` fields | Wagtail `script_url` field (migration `0002` applies the change) |
+
+## License
+
+This project is licensed under the **BSD 3-Clause License**. See the [LICENSE](LICENSE) file for details.
+
+This is a fork of [`django-plausible`](https://github.com/RealOrangeOne/django-plausible) by Jake Howard.

django_plausible_iplweb-0.6.0/README.md

@@ -0,0 +1,147 @@
+# django-plausible-iplweb
+
+[![CI](https://github.com/mpasternak/django-plausible-iplweb/actions/workflows/ci.yml/badge.svg)](https://github.com/mpasternak/django-plausible-iplweb/actions/workflows/ci.yml)
+![PyPI](https://img.shields.io/pypi/v/django-plausible-iplweb.svg)
+![Python](https://img.shields.io/badge/python-3.10%20%7C%203.11%20%7C%203.12%20%7C%203.13%20%7C%203.14-blue)
+![Django](https://img.shields.io/badge/django-5.2%20%7C%206.0-blue)
+![PyPI - Status](https://img.shields.io/pypi/status/django-plausible-iplweb.svg)
+![PyPI - License](https://img.shields.io/pypi/l/django-plausible-iplweb.svg)
+
+
+Django module to provide easy [Plausible](https://plausible.io/) integration, with [Wagtail](https://wagtail.io/) support.
+
+## Installation
+
+```
+pip install django-plausible-iplweb
+```
+
+Then simply add `plausible` to `INSTALLED_APPS`.
+
+## Usage
+
+`django-plausible-iplweb` provides a `plausible` template tag that emits Plausible's
+current per-site tracking script. Each Plausible site now has its **own script URL**
+(e.g. `https://plausible.io/js/pa-XXXXXXXX.js`) — there is no `data-domain` attribute
+any more. Copy the script URL from your Plausible dashboard (**Site Settings → General →
+Site Installation**) into `PLAUSIBLE_SCRIPT_URL`, then place the tag in your `<head>`:
+
+```html
+{% load plausible %}
+
+{% plausible %}
+```
+
+With `PLAUSIBLE_SCRIPT_URL = "https://plausible.io/js/pa-XXXXXXXX.js"`, this renders:
+
+```html
+<script defer src="https://plausible.io/js/pa-XXXXXXXX.js"></script>
+<script>
+  window.plausible = window.plausible || function () { (window.plausible.q = window.plausible.q || []).push(arguments) };
+  plausible.init({"autoCapturePageviews": false});
+  (function () {
+    var path = window.location.pathname;
+    var masks = [];
+    for (var i = 0; i < masks.length; i++) {
+      path = path.replace(new RegExp(masks[i].pattern, masks[i].flags || "g"), masks[i].replacement);
+    }
+    var url = window.location.origin + path + window.location.search;
+    plausible("pageview", { url: url });
+  })();
+</script>
+```
+
+Automatic pageview capture is **disabled** (`autoCapturePageviews: false`) so the package
+can send a single, optionally-masked pageview itself (see [URL masking](#url-masking)).
+
+If `PLAUSIBLE_SCRIPT_URL` is empty (the default), the tag renders nothing — a convenient
+way to switch analytics off in development.
+
+### Configuration
+
+All configuration lives in `settings.py`:
+
+| Setting | Default | Purpose |
+|---|---|---|
+| `PLAUSIBLE_SCRIPT_URL` | `""` | Full per-site script URL from your Plausible dashboard. Empty → tag renders nothing. |
+| `PLAUSIBLE_INIT_OPTIONS` | `{"autoCapturePageviews": False}` | Dict passed (as JSON) to [`plausible.init(...)`](https://plausible.io/docs/script-extensions). Add any init option here, e.g. `{"autoCapturePageviews": False, "hashBasedRouting": True}`. |
+| `PLAUSIBLE_URL_MASKS` | `[]` | Ordered list of client-side path-masking rules (see below). |
+| `PLAUSIBLE_KEEP_QUERY_STRING` | `True` | Append `location.search` to the reported URL (keeps `utm_*`/`ref` for acquisition reports). Set `False` to drop the query string entirely. |
+
+You can also pass the script URL at call time, e.g. to use a different site on one page:
+
+```html
+{% plausible script_url="https://plausible.io/js/pa-OTHER.js" %}
+```
+
+### URL masking
+
+Plausible records the page URL. If your paths contain identifiers (invitation codes,
+user IDs, UUIDs, …) those would leak into your analytics. `PLAUSIBLE_URL_MASKS` lets you
+redact them **client-side** before the pageview is sent. Each rule is applied to
+`location.pathname` in order via JavaScript's
+[`String.replace(new RegExp(pattern, flags), replacement)`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replace):
+
+```python
+PLAUSIBLE_URL_MASKS = [
+    # Mask invitation/passphrase codes:  /i/<passphrase>  ->  /i/__code__
+    {"pattern": r"^/i/[^/]+", "replacement": "/i/__code__"},
+    # Mask UUIDs anywhere in the path:  /<uuid>  ->  /__id__
+    {"pattern": r"/[0-9a-f-]{36}", "replacement": "/__id__", "flags": "gi"},
+    # Mask numeric ids:  /123  ->  /__id__
+    {"pattern": r"/\d+", "replacement": "/__id__"},
+]
+```
+
+`pattern` and `flags` are **JavaScript** regular-expression syntax (the rules run in the
+browser). `flags` defaults to `"g"`. The patterns above are examples — adapt them to your
+own routes; the default (`[]`) applies no masking.
+
+> **Caveat:** like Plausible's own [redaction guidance](https://plausible.io/docs/custom-locations),
+> this masking runs once when the page loads. It may not behave as expected in
+> single-page applications or with hash-based routing, where `location` changes
+> without a full page load.
+
+### Overriding the rendered markup
+
+The snippet is rendered from the `plausible/plausible.html` template. To fully customise
+it, shadow that path in your own project's templates directory.
+
+## Usage with Wagtail
+
+`django-plausible-iplweb` also provides an optional [Wagtail](https://wagtail.org)
+integration that lets editors set the script URL **per site** through the Wagtail admin.
+Add `plausible.contrib.wagtail` to `INSTALLED_APPS` and run `migrate`.
+
+Configuration is done through the "Plausible Analytics"
+[setting](https://docs.wagtail.org/en/stable/reference/contrib/settings.html):
+
+- `script_url`: the full per-site Plausible script URL. Blank (the default) → nothing is rendered for that site.
+
+Masking (`PLAUSIBLE_URL_MASKS`), init options, and query-string handling are still
+configured globally via the Django settings above.
+
+Load `plausible_wagtail` rather than `plausible`; the tag itself is still `plausible`:
+
+```html
+{% load plausible_wagtail %}
+
+{% plausible %}
+```
+
+## Migrating from 0.5.x
+
+Version 0.6.0 is a clean break to match Plausible's new tracker. Update your settings:
+
+| Old (0.5.x) | New (0.6.0) |
+|---|---|
+| `PLAUSIBLE_DOMAIN` + `PLAUSIBLE_SCRIPT_NAME` | `PLAUSIBLE_SCRIPT_URL` (the full script URL from your dashboard) |
+| `data-domain` (request host / `site_domain`) | *(gone — the site is identified by the script URL)* |
+| `{% plausible site_domain=… plausible_domain=… script_name=… %}` | `{% plausible %}` (optionally `script_url=…`) |
+| Wagtail `site_domain` / `plausible_domain` / `script_name` fields | Wagtail `script_url` field (migration `0002` applies the change) |
+
+## License
+
+This project is licensed under the **BSD 3-Clause License**. See the [LICENSE](LICENSE) file for details.
+
+This is a fork of [`django-plausible`](https://github.com/RealOrangeOne/django-plausible) by Jake Howard.