Track visits of your Neos site with

1.10.1 2024-01-15 23:07 UTC


Latest stable version Total downloads License GitHub forks GitHub stars GitHub watchers

Carbon.Plausible Package for Neos CMS

Easily integrate Plausible Analytics into your Neos site.


Plausible is a lightweight and open-source website analytics tool. It doesn't use cookies and is fully compliant with GDPR, CCPA, and PECR. This plugin is meant to remove all friction from adding the Plausible Analytics tracking script code to your Neos site. All you need to do is define your Plausible domain in your Neos Settings.yaml file.


  • Multi-site compatibility
  • Backend module
  • Check if the requested domain matches the defined domain to track
  • Enabled per default only on Production environment
  • Embed stats directly into the Neos Backend
  • Proxies the needed JS files (cached for 6 hours) and API from Plausible

Multi-site compatibility

If you run a multi-site setup, we got you covered! You can set different trackings for the sites based on the root node name.

Backend module

This package adds a backend module to your Neos instance, which helps check your configuration and opt-out your browser for tracking.

screenshot of backend module as administrator

If a backend user is not an administrator, he'll get a different view:

screenshot of backend module as editor

It also checks if the resulting javascript path doesn't return a 404 error:

error in the backend module

NodeType mixins for disable tracking on a document or set custom events

This package contains two mixins:

set options in the inspector

Opt out and exclude your visits from the analytics

By default, Plausible Analytics tracks every visitor to your website. When you're working on your site, you might not want to record your own visits and page views. To prevent counting your visits, you can set a special localStorage flag in the browser. Here's how.

  • Go to your-domain.tld/~/disable-tracking. This sets the flag and redirects the visitor to the homepage. Great for people without access to the Neos Backend.
  • As an Editor, you can enable/disable the flag also in the Plausible management module: your-domain.tld/neos/management/plausible
  • Add the component Carbon.Plausible:Component.Toggle to a document and click the button.
  • You can do this also by yourself by following the excluding guide on

Tracking custom event goals with data-analytics

To use this feature, you have to enable the dataAnalyticsTracking setting. Register events in the HTML with the use of an attribute tag data-analytics.

Note: Watch your quotes! Especially in the props as we want to be able to create an object.

<!-- Tracking a form -->
  <button type="submit" data-analytics='"Contact"'>Send Message...</button>

<!-- Tracking a link -->
  data-analytics='"Register", {"props":{"plan":"Navigation"}}'


Run the following command in your site package

composer require --no-update carbon/plausible

Then run composer update in your project root.


Single-site setup

If you have a single site setup, you can adjust the configuration under the key Carbon.Plausible.default in your Settings.yaml:

Key Default Type Description
domain null string Set here the plausible domain. This setting is required
reverseProxy true bool Proxies the needed Javascript (cached for 6 hours) and API calls from Plausible. If set, the settings host has no effect
host null string If you have set a custom domain, you can set it here. Example: For new instances you cannot set up a custom domain, as it is depreciated. To enable this setting, you have to set reverseProxy to false.
sharedLink null string If you have opened up your website stats to the public or created a private and secure link, enter it to enable the embedded view of the stats in the backend
customEvents false string|bool If you want to set custom events in your javascript, set this to true or a string. If set to a string, this whole string gets included on every document. If you set custom events via Fusion or the Carbon.Plausible:Mixin.CustomEvent mixin, you don't have to set it to true. The snippet gets activated automatically if needed. The inline javascript get's minified with JShrink
dataAnalyticsTracking false bool If you want to enable data-analytics for tracking links and form submits set this to true
hashBasedRouting false bool Automatically follow frontend navigation when using hash-based routing
outboundLinks false bool Automatically track clicks on outbound links from your website
fileDownloads false bool|string|array Automatically track file downloads
taggedEvents false bool Allows you to track standard custom events such as link clicks, form submits, and any other HTML element clicks
revenue false bool Allows you to assign dynamic monetary values to goals and custom events to track revenue attribution
exclusions null string|array Exclude certain pages from being tracked
compat false bool Compatibility mode for tracking users on Internet Explorer
local false bool Allow analytics to track on localhost too which is useful in hybrid apps
manual false bool Don't trigger pageviews automatically. Also allows you to specify custom locations to redact URLs with identifiers. You can also use it to track custom query parameters
pageviewProps null array With pageviewProps you can attach custom properties (also known as custom dimensions in Google Analytics) sending a pageview in order to create custom metrics.


Our "File Downloads Tracking" captures a file download event each time a link is clicked with a document, presentation, text file, compressed file, video, audio or other common file type. Both internal and external files downloads are tracked. These file extensions are tracked by default:

.pdf, .xlsx, .docx, .txt, .rtf, .csv, .exe, .key, .pps, .ppt, .pptx, .7z, .pkg, .rar, .gz, .zip, .avi, .mov, .mp4, .mpeg, .wmv, .midi, .mp3, .wav, .wma

You can also specify a custom list of file types to track if you set fileDownloads to a string or an array. Say you only want to track .zip and .pdf files, you can use a snippet like this:

fileDownloads: 'zip,pdf'


  - zip
  - pdf

Multi-site setup

If you run multiple sites on one Neos installation, you can set this under the key Carbon.Plausible.sites in your Settings.yaml. Be aware that if you set one value in Carbon.Plausible.default, these are set as the new fallback value. For example, if you set Carbon.Plausible.default.outboundLinks to true, is outboundLinks set to true per default for all sites. Of course, you can disable this again if you set this to false on your site setting.


        outboundLinks: true
        hashBasedRouting: true
        exclusions: "/blog4, /rule/*, /how-to-*, /*/admin"
        customEvent: "plausible('Download', {props: {method: 'HTTP'}})"
          - /blog4
          - /rule/*
          - /how-to-*
          - /*/admin

The key of the site (e.g. myfirstsite) is the root node name found under Administration » Sites Management.

Fusion Components


The main Fusion component is Carbon.Plausible:Component.TrackingCode. This component gets included into Neos.Neos:Page under the path plausibleTrackingCode. So if you want to add a custom event to a ceratin document, you can do it like this:

prototype(Vendor.Site:Document.NotFound) < prototype(Neos.Neos:Page) {
    plausibleTrackingCode.customEvents = 'plausible("404",{ props: { path: document.location.pathname } });'


With pageviewProps you can attach custom properties (also known as custom dimensions in Google Analytics) sending a pageview in order to create custom metrics You can add up to 30 custom properties alongside a pageview by adding multiple attributes:

prototype(Vendor.Site:Document.NotFound) < prototype(Neos.Neos:Page) {
    plausibleTrackingCode.pageviewProps {
      author = 'John Doe'
      darkmode = true


Carbon.Plausible:Component.Toggle is a small component to let the user if he wants to opt-out from tracking.