Flowcourier.Umbraco.Analytics.Core 17.5.0-alpha.2

Flowcourier.Umbraco.Analytics.Core

The shared base of Flowcourier's analytics packages for Umbraco. It adds an Analytics section to the backoffice, and fills the shared Analytics tab on every document (Foundation's — the SEO Agent's and AEO's per-page views appear there too, as further sub-tabs) with this package's panels. The same dashboards render whatever the traffic source:

• An Overview dashboard, the section's landing page: human traffic and AI-agent traffic side by side over the same range, with the agent half read from Flowcourier.Umbraco.AEO when it is installed. It renders whichever halves the site has and names the package that would supply the rest, so it is useful before anything is set up.
• Realtime, Visitors, Behaviour, Acquisition and Technology dashboards, plus a per-page traffic view — fed by a provider package. Install Flowcourier.Umbraco.Matomo for Matomo or Flowcourier.Umbraco.GoogleAnalytics for Google Analytics 4 — one of the two, never both.
• A "Google Search" sub-tab on documents, holding both of Google's views of the page because an editor reads them as one question — does Google have it, and is it fast when it gets there? It appears when either feature below is enabled and renders whichever half the install can serve.
• Optional Google Search Console: the index status from the URL Inspection API with what to do about it, and the page's clicks, impressions, CTR, position, queries, countries and devices — plus a site-wide "Search queries" dashboard.
• Optional Google PageSpeed Insights: the Lighthouse category scores and real-user (CrUX) data for mobile or desktop, in the same sub-tab. It shows the last analysis the server holds and waits for a click before running a new one — a run takes 20–60 s and spends PageSpeed quota. Lighthouse's own detail (lab metrics, opportunities, failing audits) is one link away in Google's tool.
• A live visitor badge on the Analytics section in the top bar; it pulses briefly when the number changes.
• Findings on the document tab (Foundation's strip): traffic down vs the previous 28 days with the channel that fell most, no visits on an old page, a landing page bouncing well above the site median, a mid-funnel page where visitors stop, no internal page leading here, site searches right after the page, server time far above the site's — and "not indexed" from the last Search Console inspection. Thresholds under Flowcourier:Analytics:Findings.
• Feeds Foundation's page detection: a node whose URL has pageviews is a page (so the document tab shows) and the tracked site URL is where the front end is probed for the rest.
• A Visits dashboard and a page flow, when the installed provider answers per visit — see below.

Configured entirely from appsettings. No database tables unless you turn Search Console index tracking on — that one feature stores the last known index status per page in FcAnalyticsIndexStatus, created on the next start after you enable it. You normally install a provider package, which brings this one in; install this package alone if you only want PageSpeed Insights and Search Console.

Visitor journeys

Two surfaces, both optional:

• A Visits dashboard: the visits of a date range, newest first, and the ordered path of whichever one you open — entry page, each pageview with the time spent on it, the last one marked as the exit, and any events, goals, site searches, downloads and outlinks shown on the step they happened on. Earlier visits by the same visitor open in the same panel. The Realtime dashboard's rows open it too, from data that report already carries.
• The page flow on a document's Analytics → Traffic tab: where visitors to this page came from and where they went next, as one picture — previous pages and external referrers on one side, next pages, outlinks, downloads, the visits that came back to the page and the ones that left the site on the other. Each side shows its top 8 plus one aggregated "other" row, and a toggle swaps the graph for the numbers.

It needs a provider that answers per visit. Matomo does; Google Analytics cannot (GA4's API has no per-visit data), so on a GA install these surfaces simply do not appear. Nothing here is stored in Umbraco — every request goes to the analytics host and the answer is rendered, never persisted.

Matomo prerequisites

Access and the kill switch

Journey endpoints are checked server-side for Analytics section access — every authenticated backoffice user can reach the API (editors need the document tab), so the client-side section gate is not the control. The same check now covers the realtime report, which also lists individual visits. A user without the section gets the error envelope with status 403, and the status endpoint reports the feature as not ready for them, so no surface is offered in the first place.

Set Flowcourier:Analytics:VisitorJourney:Enabled to false to switch the whole thing off: no dashboard is registered, the endpoints answer 409, and no request for individual-visitor data reaches the provider.

A note on privacy

Some sites run Matomo precisely to avoid individual-level tracking. This feature surfaces data Matomo is already collecting and that the Realtime dashboard already shows — it does not change what is tracked, and it stores nothing. If that is not wanted in the backoffice at all, the switch above is the answer; if it is not wanted anywhere, Matomo's own enable_visitor_log is.

Configure

{
  "Flowcourier": {
    "Analytics": {
      "SiteUrl": "https://www.example.com",
      "PageSpeed": { "Enabled": true, "ApiKey": "<google api key>" },
      "SearchConsole": { "Enabled": true, "Property": "sc-domain:example.com" },
      "Google": { "ServiceAccountJson": "<service-account key json>" }
    }
  }
}

Effective values (secrets masked) are shown under Settings → Flowcourier → Analytics.

Requirements

Umbraco 17.5 or later (net10.0). Google features need outbound HTTPS to googleapis.com / searchconsole.googleapis.com.

License

Free to use, including commercially — not open source. See the LICENSE.md packed with this package. Paid Pro features and consulting are available from Flowcourier ApS.

© 2026 Flowcourier ApS. All rights reserved.