v3.1.0-rc.0

[apata]

This release

• Introduces the new dynamic and more configurable tracking snippet and script (legacy scripts and snippets will still continue to work). See this doc for more details
• Supports a new optional property on events: interactive. See this doc for more details.
• Revamps dark theme
• ...other fixes and improvements listed below

Upgrade

Update the image used for plausible

_compose.yml

plausible:
- image: ghcr.io/plausible/community-edition:v3.0.1
+ image: ghcr.io/plausible/community-edition:v3.1.0-rc.0

and restart the containers

_console

$ docker compose up -d

This will boot up the new version of the app.

Changelog

Added

• Custom events can now be marked as non-interactive in events API and tracker script: events marked as non-interactive are not counted towards bounce rate
• Ability to leave team via Team Settings > Leave Team
• Stats APIv2 now supports include.trim_relative_date_range - this option allows trimming empty values after current time for day, month and year date_range values
• Properties are now included in full site exports done via Site Settings > Imports & Exports
• Google Search Console integration settings: properties can be dynamically sought
• Weekly/monthly e-mail reports now contain top goal conversions
• Newly created sites are offered a new dynamic tracking script and snippet that's specific to the site
• Old sites that go to "Review installation" flow are offered the new script and snippet, along with a migration guide from legacy snippets, legacy snippets continue to function as before
• The new tracker script allows configuring transformRequest function to change event payloads before they're sent
• The new tracker script allows configuring customProperties function hook to derive custom props for events on the fly
• The new tracker script supports tracking form submissions if enabled
• The new tracker script automatically updates to respect site domain if it's changed in "Change domain" flow
• The new tracker script automatically updates to respect the following configuration options available in "New site" flows and "Review installation" flows: whether to track outbound links, file downloads, form submissions
• The new tracker script allows overriding almost all options by changing the snippet on the website, with the function plausible.init({ ...your overrides... }) - this can be unique page-by-page
• A new @plausible-analytics/tracker ESM module is available on NPM - it has near-identical configuration API and identical tracking logic as the script and it receives bugfixes and updates concurrently with the new tracker script

Removed

Changed

• A session is now marked as a bounce if it has less than 2 pageviews and no interactive custom events
• All dropmenus on dashboard are navigable with Tab (used to be a mix between tab and arrow keys), and no two dropmenus can be open at once on the dashboard
• Special path-based events like "404" don't need event.props.path to be explicitly defined when tracking: it is set to be the same as event.pathname in event ingestion; if it is explicitly defined, it is not overridden for backwards compatibility
• Main graph no longer shows empty values after current time for day, month and year periods
• Include bounce_rate metric in Entry Pages breakdown
• Dark mode theme has been refined with darker color scheme and better visual hierarchy

Fixed

• Make clicking Compare / Disable Comparison in period picker menu close the menu
• Do not log page views for hidden pages (prerendered pages and new tabs), until pages are viewed
• Password-authenticated shared links now carry over dashboard params properly
• Realtime and hourly graphs of visit duration, views per visit no longer overcount due to long-lasting sessions, instead showing each visit when they occurred
• Fixed realtime and hourly graphs of visits overcounting
• When reporting only visitors and visits per hour, count visits in each hour they were active in
• Fixed unhandled tracker-related exceptions on link clicks within svgs
• Remove Subscription and Invoices menu from CE
• Fix email sending error "Mua.SMTPError" 503 Bad sequence of commands

---

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

[timscha]

Upgrade from 3.0 is not working for me, I get an 502 error. Logs say this:

plausible-1            | Loading plausible..
plausible-1            | Starting dependencies..
plausible-1            | Starting repos..
plausible-1            | Plausible.Repo database already exists
plausible-1            | Plausible.IngestRepo database already exists
plausible-1            | Creation of Db successful!
plausible-1            | Loading plausible..
plausible-1            | Starting dependencies..
plausible-1            | Starting repos..
plausible-1            | ** (BadMapError) expected a map, got: nil
plausible-1            |     (elixir 1.18.3) lib/map.ex:535: Map.get(nil, "404", false)
plausible-1            |     (plausible 0.0.1) lib/plausible/data_migration/backfill_tracker_script_configuration.ex:90: Plausible.DataMigration.BackfillTrackerScriptConfiguration.tracker_script_configuration/2
plausible-1            |     (elixir 1.18.3) lib/enum.ex:1714: Enum."-map/2-lists^map/1-1-"/2
plausible-1            |     (plausible 0.0.1) lib/plausible/data_migration/backfill_tracker_script_configuration.ex:62: Plausible.DataMigration.BackfillTrackerScriptConfiguration.create_tracker_script_configurations/2
plausible-1            |     (plausible 0.0.1) lib/plausible/data_migration/backfill_tracker_script_configuration.ex:56: Plausible.DataMigration.BackfillTrackerScriptConfiguration.process_batch/2
plausible-1            |     (ecto_sql 3.13.2) lib/ecto/migration/runner.ex:341: Ecto.Migration.Runner.log_and_execute_ddl/3
plausible-1            |     (elixir 1.18.3) lib/enum.ex:1714: Enum."-map/2-lists^map/1-1-"/2
plausible-1 exited with code 1 (restarting)

[apata]

Thanks for giving it a go, @timscha, we will publish the next RC today!

[apata]

The next release candidate is now available, https://github.com/plausible/analytics/releases/tag/v3.1.0-rc.1, with its own discussion #5861.

[timscha]

Thanks for the quick fix @apata - Upgrade went well now. :)