📌 | Plausible tracking | All functions defined in a module file must be prefixed with the module's name
🇩🇰Denmark RoWaBo
🐛 | Plausible tracking | t() calls should be avoided in classes, use \Drupal\Core\StringTranslation\StringTranslationTrait and $this->t() instead
🇩🇰Denmark RoWaBo
📌 | Plausible tracking | All functions defined in a module file must be prefixed with the module's name
🇩🇰Denmark RoWaBo
🐛 | Plausible tracking | t() calls should be avoided in classes, use \Drupal\Core\StringTranslation\StringTranslationTrait and $this->t() instead
🇩🇰Denmark RoWaBo
🇩🇰Denmark RoWaBo
I apologize for the delayed response.
We developed our own module because we needed more advanced features, including:
- Tracking custom events: We have implemented our own JavaScript that can record events using data attributes in the markup.
- Tracking custom query parameters: This functionality is enabled with our custom JavaScript, and we use the Plausible manual script.
Additionally, considering that we are a web bureau managing multiple sites, this is a convenient way for us to ensure that our Plausible script stays updated across all sites.
I hope this addresses your questions.