Analytics

Web analytics for an Osy# app: Plausible or Google Analytics 4, page views on every route change, the e-commerce events both understand (view_item, add_to_cart, begin_checkout, purchase — GA4's names), and the consent GA4 needs in the EU before it may track.

// app.osy — grant the provider's hosts
use Osysharp.Analytics@0 { egress browser "plausible.io"; }

// config — which provider
app.Analytics = new AnalyticsSetup { Provider = AnalyticsProvider.Plausible, Domain = "shop.example.com" };

// the layout — once
Analytics(events: [], cart: [], currency: "SEK", onSent: Heard);

A shop built on Osysharp.Shop writes ShopAnalytics() in its layout instead, and gets every e-commerce event from its own rows.

• Plausible is spoken to through its Events API from the kit's own control — no third-party script on the page. It sets no cookie and needs no consent. A self-hosted instance: set Host and grant its host instead.
• GA4 loads Google's tag from the host the app granted (egress browser script "*.googletagmanager.com"; plus egress browser "*.google-analytics.com"; egress browser "*.analytics.google.com";), and only after the visitor accepts the consent bar. Before that nothing of Google's is fetched.
• A purchase is reported once per order in a browser, whatever reloads.

Its tests: tests/ (the kit in a real app) and npm test (the shim in a DOM, with the network stubbed — GA4 and the exact bodies Plausible receives).

Get it

Add the kit to your app’s manifest:

app MyApp {
  use Osysharp.Analytics@0;
}

Then run osy lock: it downloads the release, verifies it by its content address and pins that version in osyrin.lock. osy kits Osysharp.Analytics shows what the kit is for, from inside your app.

Reference: osy docs ui-analytics-kit.