-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heads up: Plausible site verification tool #24
Comments
This is related to the plausible integration not finding the Plausible snippet. I have followed the documentation for the integration, but Plausible seems to struggle with detecting the "snippet", which I guess gets auto-injected by the module? |
@Bcdo yup, since there is no snippet and no support for the callback I mentioned, our headless browser test can't tell if the test event was sent, thus making verification fail. |
@aerosol Is there a workaround? Or do I need to install it manually outside the module for now? |
There is no workaround at the moment, because this package no longer uses the official `plausible-tracker' package, which seems to have been abandoned years ago. Instead, we use a maintained Plausible tracker rewrite by @Barbapapazes. |
Is there any documentation page related to this new feature? |
@Barbapapazes hi, what sort of documentation do you require? I described the implementation details in the top post of this thread. Let me know if anything's unclear. Thanks. |
After reading it again, I think it's clear. I will update my fork accordingly. |
Hey, could you tell me if I well understand the site verification process? Thanks 🙌 |
Merged |
Hey,
just wanted to notify you about a new feature we'll be soon introducing in Plausible - a site verification tool allowing you to verify the integration.
It will employ a headless agent that visits the site and seeks for
window.plausible()
function being defined.The signature is
plausible(eventName, options)
whereoptions
must be able to accept acallback
key with a value offunction({status})
- status is the HTTP status of/api/events
response. The agent will send a custom event using that function. Otherwise the verification will be marked as failing.Our tracker has been updated accordingly, as well as the npm package. If you like the nuxt module to be verifiable, please consider applying similar changes.
Many thanks!
The text was updated successfully, but these errors were encountered: