Analytics

Osirion.Blazor.Analytics has one tracker component per analytics service. Each writes that service's tracking script into the page from configuration. They render on the server, so they work under Static SSR with no interactive render mode, and they live in the Osirion.Blazor.Analytics.Components namespace.

Plausible and Umami are available from 4.1.

Trackers inject third-party scripts, so these pages have no live demos: a demo would load the provider's script on the documentation page itself. Each page shows the markup its tracker renders instead.

What they share

@using Osirion.Blazor.Analytics.Components

<head>
    <meta charset="utf-8" />
    <base href="/" />
    <HeadOutlet />
    <GA4Tracker />
    <ClarityTracker />
</head>

• Base class. All six derive from AnalyticsTracker, which adds the SiteId and Enabled parameters. Enabled set to false turns a tracker off for one render; SiteId replaces the configured site ID for the trackers that use one (Clarity, Matomo and Umami). A parameter you leave unset keeps the configured value.
• Nothing renders by accident. A tracker whose service is not registered, whose Enabled is false, or whose required value is missing or invalid, renders nothing.
• Consent. The package has one consent gate, off by default. With it on, no tracker writes its script until the visitor accepted the analytics category in OsirionCookieConsent. Setup is on the package page.
• Content Security Policy. Clarity, GA4, Matomo, Plausible and Yandex Metrica write inline scripts and add no nonce; Umami writes only an external script tag. Each page lists the addresses its markup names.

Related

• Osirion.Blazor.Analytics: install, registration, configuration and the consent gate
• Cookie consent: the banner that records the visitor's choice