Skip to main content

Plausible analytics

Fix script detection, duplicate integration, and missing feedback events.

Use the Plausible registry integration from @nuxt/scripts through Ginko Docs. Do not add the raw Plausible snippet in a second location.

Plausible cannot detect the site

  1. Confirm the browser is on the canonical production domain.
  2. Inspect the rendered document head for exactly one Plausible script.
  3. Confirm its pa-<script-id>.js value matches the site in Plausible.
  4. Confirm no content security policy or blocker prevents the request.
  5. Check the network response and browser console.
  6. Redeploy production after a configuration change.

The script ID is not the domain name and is not a secret. Commit the exact ID in the documentation configuration. Do not put it in a Vercel environment variable unless a different product has a real runtime need.

Feedback events do not arrive

Use “Was this page helpful?” on the production site. Confirm the browser sends docs-feedback. Confirm the event is available in the correct Plausible site. Check that analytics consent or browser blocking did not prevent the request.

This handbook has analytics disabled until the real oss.lupinum.com Plausible site exists. Add the verified ID once during launch.