Verification to dashboard by RobertJoonas · Pull Request #6516 · plausible/analytics

RobertJoonas · 2026-07-20T09:03:09Z

Changes

Move verification (all flows: provisioning, review, and domain_change) to the dashboard (between the top bar and sources/pages reports). It will remain a LiveView, but will be teleported into the stats-react-container with the help of <.portal>. Various UI changes in this PR to make the UI feel more "banner-like".

For reviewers: For UI testing, I encourage playing around with it locally -- this PR builds a dev convenience for mocking different verification outcomes. The same code is also used for E2E testing.

In addition to verification, we'll also move the email reports CTA from stats.html.heex to React. The reason for that is positioning -- otherwise impossible to render it between top bar and stats reports.

New db field and onboarding logic

This PR also includes a migration, adding a new site.onboarding_status field which makes all of this possible. There are currently four different statuses possible:

:new_site
- The site was just created, didn't succeed verification, didn't receive any pageviews yet
- Means that a "Setup required" pill should be rendered on this site card on the /sites page
- Any links to this dashboard (such as the one in site-switcher.js) should append ?verify_installation=true&flow=provisioning to the URL to initiate a verification banner upon entering the dashboard.
:verification_completed
- Advances to this state once a verification success is encountered (no matter through what flow -- provisioning / review / domain_change)
- Means that "Setup required" won't ever render for this site again, and verification banner won't be triggered automatically for this site anymore. The only way to get verification again is Site Settings > Review Installation
:first_pageview
- The site has received at least one pageview
- Advances to this state when:
  - a full dashboard load happens and the site has pageviews (piggybacking on the same condition where site.stats_start_date is set for the very first time)
  - the site card on the /sites page is about to display "X visitors in the last 24h" (where X > 0) for the very first time
  - (note that either of the above can happen before verification success is encountered, in which case that step is simply skipped. This is also exactly what happens on CE)
- Similar to :verification_completed, we won't automatically trigger verification anymore
- In this state, the email reports CTA starts appearing to any site member with editor permissions (owner, admin, editor)
:completed
- Everything related to onboarding is done
- This is the database default for the onboarding_status field -- running the migration will set the new field value to :completed for every existing site.
- As for new sites (after this PR gets deployed), the only way to get to this state will be to dismiss or action (click the /:domain/settings/email-reports link) the email reports CTA banner.

Migration

Extract the migration and execute it

Tests

Automated tests have been added

Changelog

Need to update and review the flows on CE

Documentation

Docs have been updated

Dark mode

The UI has been tested both in dark and light mode

* Refine verification banner UI and copy - Simplify failure CTAs: keep "Check again" as primary, add ghost "Review installation" (or "Try another URL" when a custom URL retry is offered); remove installation-guide, change-method, and view-snippet expandable logic - Render inline "verify your installation manually" / "review your installation" links inside recommendation text (offer_custom_url_input scenarios) via safe HTML helpers, avoiding HEEx whitespace pitfalls - Tighten diagnostics title and body copy - Move the "Setup pending" pill in the sites list to replace the percentage indicator; use the generic pill component - Extend the notice component with title_class override and a spinner slot; swap success icon to solid check-circle * improve templating logic --------- Co-authored-by: Robert Joonas <robertjoonas16@gmail.com>

…icking retry

...and return the whole site struct. StatsController.stats action needs the whole site returned to known the "just updated" onboarding status when rendering the dashboard stats.html.

ukutaht

It was a lot to review so I don't feel like I could pay full attention to everything. Overall looks all good to me.

In general it doesn't feel great to me to have liveview running alongside React like this on the dashboard long-term but I also understand why it was done this way.

ukutaht · 2026-08-03T11:34:37Z

+      const { queryParams } = (event as CustomEvent<VerificationFinishedDetail>)
+        .detail
+
+      navigate({


Hmm I'm thinking using replace: true here would be more fitting so the path with URL params does not stay in the browser history.

Agreed. Did that in 90342eb.

There's still one quirk where if you navigate in React (e.g. change period/filters) then the verification params will stay in those history entries. So for example:

verification banner is visible (either loading or failed) and the params are in the URL

open the page filter modal, then close it

close the verification banner (params are stripped from the URL)

hit back in browser history (page filter modal appears)

Quirk: the verification params re-appear in the URL as well, refreshing the page now will bring verification back

In practice though, I think it's very unlikely to hurt the UX because:

although some clicking-around on the dashboard to discover what it can do is expected, going back in browser history when there's nothing meaningful happening on the dashboard yet is probably rare.

even though the query params might re-appear, the verification will only come back if 1) it didn't succeed before, and 2) the dashboard doesn't have any pageviews yet.

the worst case scenario is: user has to dismiss the banner for a second time.

Co-authored-by: Codesmith <codesmith-bot@users.noreply.github.com>

…t time) (#6571) * Revert "Use Blacksmith checkout with sticky-disk git mirror in Elixir CI (#6564)" This reverts commit fd528f2. * Fix inert service container health checks in Elixir CI The postgres and clickhouse health-check options were nested under env, so Docker never received a health check and jobs could start before ClickHouse was listening, failing ecto.create with Mint.TransportError{reason: :closed}. Move options to the service level and point the ClickHouse check at the real HTTP port (8123 /ping) instead of the unused 8124. Co-authored-by: Codesmith <codesmith-bot@users.noreply.github.com> * Give ClickHouse a 2m health-check start period ClickHouse on these runners can take over 50s to start listening during load spikes (the same slowness behind the Aug 3+ ecto.create failures). Without a start period the health check flips to unhealthy after ~50s and the runner kills the job before the server is ready; probe failures during the start period no longer count toward --health-retries. Co-authored-by: Codesmith <codesmith-bot@users.noreply.github.com> * Probe ClickHouse health check via 127.0.0.1, not localhost The server fails to bind [::] in these containers (IPv6 disabled) and falls back to 0.0.0.0 only, while busybox wget resolves localhost to ::1 and does not retry the next address, so the probe got connection refused forever and every service init failed. Reproduced against clickhouse/clickhouse-server:25.11.5.8-alpine: localhost fails, 127.0.0.1 succeeds and the container reports healthy within seconds. Co-authored-by: Codesmith <codesmith-bot@users.noreply.github.com> --------- Co-authored-by: Codesmith <codesmith-bot@users.noreply.github.com>

Adjust the global btn-base styling to make the button appear "disabled", when phx-click-loading is set on it.

RobertJoonas added the preview label Jul 21, 2026

apata reviewed Jul 22, 2026

View reviewed changes

Comment thread lib/plausible_web/live/sites.ex

RobertJoonas marked this pull request as draft July 23, 2026 11:32

RobertJoonas force-pushed the verification-to-dashboard branch from 01949f3 to 511af2c Compare July 27, 2026 06:52

RobertJoonas and others added 26 commits July 29, 2026 12:02

make verification work in a banner

e4143f1

move custom url input into the banner

6611ad4

improve notice styles

9f3c567

expandable instructions

894bcd5

stop polling pageviews

a5b23b3

rely on tracker_script_config object for installation_method

37f8951

proper dismiss logic

dc490f7

[revert me] debugging UI scenarios

b41381e

rename verification (component) to verification_banner

e170662

emails CTA banner

e6bd40c

revert changes committed for debugging

dde16fc

fix test after rebase

2494403

fix CE tests

c797cc0

improve stats_controller_test.exs

f03da3a

E2E: named verification results + add genserver for mock scenarios

f11d0c4

E2E: checks_mock module

d2d969c

E2E: plug in the ChecksMock module

6dc97b7

E2E: put_verification_scenario endpoint

f67e7df

e2e test for verification success

b52e667

get CI green

3836bd8

migration: add onboarding_status

eb517fd

update site schema with the new field

530ffd2

advance status to verification_succeeded

d1f6130

fix setup pending pill condition (/sites page)

222a85a

further guard verification banner rendering in provisioning flow

69f90e0

RobertJoonas added 6 commits July 29, 2026 12:02

move ChecksMock and MockScenarios into a single file, use :ets

f638a19

move checks_mock.ex to test/support

3126a39

different success message depending on the flow

0cb9ea2

fixup: make sure component goes into loading state instantly after cl…

25ece8a

…icking retry

stats_start_date -> ensure_stats_start_date

9fc6b5f

...and return the whole site struct. StatsController.stats action needs the whole site returned to known the "just updated" onboarding status when rendering the dashboard stats.html.

advance onboarding status from /sites page too

3fd5593

RobertJoonas force-pushed the verification-to-dashboard branch from 45547c4 to 3fd5593 Compare July 29, 2026 11:03

RobertJoonas marked this pull request as ready for review July 29, 2026 12:32

RobertJoonas added 4 commits July 29, 2026 19:04

push_navigate -> redirect

1131181

changelog + change dashboard link text for CE on installation screen

1e9e352

credo and remove redundant else clause

63331fa

fix installation_test (CE)

5a9d159

RobertJoonas mentioned this pull request Jul 30, 2026

Improve the first-dashboard launch banner #6535

Closed

2 tasks

fix E2E test

3e8c4b8

ukutaht approved these changes Aug 3, 2026

View reviewed changes

RobertJoonas added 2 commits August 4, 2026 09:21

remove runtime Mix.env call

3290d25

do not persist verification params in browser history

90342eb

RobertJoonas mentioned this pull request Aug 4, 2026

Migration: add site.onboarding_status #6572

Merged

1 task

apata and others added 3 commits August 4, 2026 10:44

Add workaround for CH query condition cache bug (#6562)

48dd58f

Use Blacksmith checkout with sticky-disk git mirror in Elixir CI (#6564)

5c512da

Co-authored-by: Codesmith <codesmith-bot@users.noreply.github.com>

RobertJoonas force-pushed the verification-to-dashboard branch from 350345a to acab7c3 Compare August 4, 2026 09:45

RobertJoonas and others added 4 commits August 4, 2026 12:35

fight with latency (Try another URL button)

2b94b44

fight latency (clicking Check again)

fb403fa

Adjust the global btn-base styling to make the button appear "disabled", when phx-click-loading is set on it.

nom format e2e

38a65a9

Merge branch 'master' into verification-to-dashboard

de47e98

RobertJoonas added this pull request to the merge queue Aug 4, 2026

Merged via the queue into master with commit b8484ea Aug 4, 2026
23 checks passed

RobertJoonas deleted the verification-to-dashboard branch August 4, 2026 15:26

Navigation Menu

Uh oh!

Uh oh!

Verification to dashboard - #6516

Verification to dashboard#6516
RobertJoonas merged 52 commits into
masterfrom
verification-to-dashboard

RobertJoonas commented Jul 20, 2026 •

edited

Loading

Uh oh!

Uh oh!

ukutaht left a comment •

edited

Loading

Uh oh!

Uh oh!

ukutaht Aug 3, 2026

Uh oh!

RobertJoonas Aug 4, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Uh oh!

Conversation

RobertJoonas commented Jul 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

New db field and onboarding logic

Migration

Tests

Changelog

Documentation

Dark mode

Uh oh!

Uh oh!

ukutaht left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

ukutaht Aug 3, 2026

Choose a reason for hiding this comment

Uh oh!

RobertJoonas Aug 4, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

RobertJoonas commented Jul 20, 2026 •

edited

Loading

ukutaht left a comment •

edited

Loading