v3.0.0-rc.0

[aerosol]

Warning

In order to test the pre-release, please use https://github.com/plausible/analytics/releases/tag/v3.0.0-rc.4 patch.

The highlights of this release are:

• Create teams, manage users and permissions
• Scroll depth, engagement time and (reworked) time on page metrics
• Segments feature: group filters into persistent, named presets

Upgrade

Update the image used for plausible

_compose.yml

plausible:
- image: ghcr.io/plausible/community-edition:v2.1.5
+ image: ghcr.io/plausible/community-edition:v3.0.0-rc.0

and restart the containers

_console

$ docker compose up -d

This will boot up the new version of the app.

Changelog

The following changes have been made since 2.1.5:

Added

• Add top 3 pages into the traffic spike email
• Two new shorthand time periods 28d and 90d available on both dashboard and in public API
• Average scroll depth metric
• Scroll Depth goals
• Dashboard shows comparisons for all reports
• UTM Medium report and API shows (gclid) and (msclkid) for paid searches when no explicit utm medium present.
• Support for case_sensitive: false modifiers in Stats API V2 filters for case-insensitive searches.
• Add text version to emails Autogenerate text emails #4674
• Add acquisition channels report
• Add filter is not for goals in dashboard Excluding goals in dashboard #4983
• Add Segments feature
• Support ["is", "segment", [<segment ID>]] filter in Stats API
• Time on page metric is now sortable in reports
• Plausible tracker script now reports maximum scroll depth reached and time engaged with the site in an engagement event. These are reported as sd and e integer parameters to /api/event endpoint respectively. If you're using a custom proxy for plausible script, please ensure that these parameters are being passed forward.
• Plausible tracker script now reports the version of the script in the v parameter sent with each request.
• Add support for creating and managing teams owning multiple sites
• Introduce "billing" team role for users
• Introduce "editor" role with permissions greater than "viewer" but lesser than "admin"
• Support behavioral filters has_done and has_not_done on the Stats API to allow filtering sessions by other events that have been completed.
• time_on_page metric is now graphable, sortable on the dashboard, and available in the Stats API and CSV and GA4 exports/imports

Removed

• Internal stats API routes no longer support legacy dashboard filter format.
• Dashboard no longer shows "Unique visitors" in top stats when filtering by a goal which used to count all users including ones who didn't complete the goal. "Unique conversions" shows the number of unique visitors who completed the goal.

Changed

• Increase decimal precision of the "Conversion rate" metric from 1 to 2 (e.g. 16.7 -> 16.67)
• The "Last 30 days" period is now "Last 28 days" on the dashboard and also the new default. Keyboard shortcut T still works for last 30 days.
• Last 7d and 30d periods do not include today anymore
• Filters appear in the search bar as ?f=is,page,/docs,/blog&f=... instead of ?filters=((is,page,(/docs,/blog)),...) for Plausible links sent on various platforms to work reliably.
• Details modal search inputs are now case-insensitive.
• Improved report performance in cases where site has a lot of unique pathnames
• Plausible script now uses fetch with keepalive flag as default over XMLHttpRequest. This will ensure more reliable tracking. Reminder to use compat script variant if tracking Internet Explorer is required.
• The old /api/health healtcheck is soft-deprecated in favour of separate /api/system/health/live and /api/system/health/ready checks
• Changed top bar filter menu and how applied filters wrap
• Main graph now shows revenue with relevant currency symbol when hovering a data point
• Main graph now shows - instead of 0 for visit duration, scroll depth when hovering a data point with no visit data
• Make Stats and Sites API keys scoped to teams they are created in
• Remove permissions to manage sites guests and run destructive actions from team editor and guest editor roles in favour of team admin role
• Time-on-page metric has been reworked. It now uses engagement events sent by plausible tracker script. We still use the old calculation methods for periods before the self-hosted instance was upgraded. Warnings are shown in the dashboard and API when legacy calculation methods are used.

Fixed

• Fix fetching favicons from DuckDuckGo when the domain includes a pathname
• Fix visitors.csv (in dashboard CSV export) vs dashboard main graph reporting different results for visitors and visits with a time:minute interval.
• The tracker script now sends pageviews when a page gets loaded from bfcache
• Fix returning filter suggestions for multiple custom property values in the dashboard Filter modal
• Fix typo on login screen
• Fix Direct / None details modal not opening
• Fix year over year comparisons being offset by a day for leap years
• Breakdown modals now display correct comparison values instead of 0 after pagination
• Fix database mismatch between event and session user_ids after rotating salts
• /api/v2/query no longer returns a 500 when querying percentage metric without visitors
• Fix current visitors loading when viewing a dashboard with a shared link
• Fix Conversion Rate graph being unselectable when "Goal is ..." filter is within a segment
• Fix Channels filter input appearing when clicking Sources in filter menu or clicking an applied "Channel is..." filter
• Fix Conversion Rate metrics column disappearing from reports when "Goal is ..." filter is within a segment
• Graph tooltip now shows year when graph has data from multiple years

---

This discussion was created from the release v3.0.0-rc.0.

[Debcharon]

Congratulations, I'd like to try first.

[flayks]

Exciting! Gave it a try and upgraded but I get this error when launching the docker instance:

tool-plausible         | Loading plausible..
tool-plausible         | Starting dependencies..
tool-plausible         | Starting repos..
tool-plausible         | Plausible.Repo database already exists
tool-plausible         | Plausible.IngestRepo database already exists
tool-plausible         | Creation of Db successful!
tool-plausible         | Loading plausible..
tool-plausible         | Starting dependencies..
tool-plausible         | Starting repos..
tool-plausible-db      | 2025-04-08 09:12:18.566 UTC [614075] ERROR:  syntax error at end of input at character 48
tool-plausible-db      | 2025-04-08 09:12:18.566 UTC [614075] STATEMENT:  UPDATE sites SET legacy_time_on_page_cutoff = ?
tool-plausible         | ** (Postgrex.Error) ERROR 42601 (syntax_error) syntax error at end of input
tool-plausible         | 
tool-plausible         |     query: UPDATE sites SET legacy_time_on_page_cutoff = ?
tool-plausible         |     (ecto_sql 3.12.1) lib/ecto/adapters/sql.ex:1096: Ecto.Adapters.SQL.raise_sql_call_error/1
tool-plausible         |     (ecto_sql 3.12.1) lib/ecto/migration/runner.ex:341: Ecto.Migration.Runner.log_and_execute_ddl/3
tool-plausible         |     (elixir 1.18.3) lib/enum.ex:1714: Enum."-map/2-lists^map/1-1-"/2
tool-plausible         |     (elixir 1.18.3) lib/enum.ex:1714: Enum."-map/2-lists^map/1-1-"/2
tool-plausible         |     (ecto_sql 3.12.1) lib/ecto/migration/runner.ex:311: Ecto.Migration.Runner.perform_operation/3
tool-plausible         |     (stdlib 6.2.2) timer.erl:595: :timer.tc/2
tool-plausible         |     (ecto_sql 3.12.1) lib/ecto/migration/runner.ex:25: Ecto.Migration.Runner.run/8
tool-plausible exited with code 1

[flayks]

One thing I just found weird is that when I add a team, it moves all the existing sites to it and there is no way to move them from one to another. For instance I have a lot of personal sites and they all moved to this new team.

[zoldar]

@flayks You should see "Change Team" under Site Settings > Danger Zone. From there, it should be possible to move the site between the teams.

[aerosol]

You'll need >1 teams for this to work. So go to My Personal sites, add a new site and the option should appear then.

[flayks]

@aerosol Oh ok, but wouldn't adding a new site lose all the data? I find it confusing of why it moved it all to the team, it should remain personal and then we say which ones need to be in the new team, IMO.

[zoldar]

@flayks Adding a new site under My Personal Sites is only meant to trigger creation of a personal team which then becomes available as a choice in "Change Team". Other than that, this site doesn't matter - it should not have the same name as any existing site, it can't anyway as domains are unique across the whole application. It can be even removed shortly afterwards. No data will be lost on site team change.

[aerosol]

#5318