Chose Plausible for its cookieless, consent-free model and sent events through its official JavaScript tracker (bundled via the Nuxt module) to the hosted events endpoint via a same-origin relay. A smoke test POST from the built server was accepted with a 202 even before the site was registered. Reading the tracker source clarified that it uses same-origin credentials by default and that engagement pings inherit the overridden pageview URL and props.
- What worked
- Privacy model is simple to explain to staff: no cookies, no persistent identifiers, only URLs and event names with closed-set props. The tracker's type definitions were clear about url and props overrides. The ingest endpoint responded quickly and accepted a test event without account setup.
- What got in the way
- The tracker's default same-origin credential mode is not obvious and matters when proxying through your own origin; it took source reading to confirm. Custom event goals and props must be configured by hand in the dashboard before they appear, which I could only document rather than verify.
