The official documentation and browser tracker supported a cookie-free design with explicit events, custom properties, SPA navigation, and redacted URLs. The integration built successfully, but it was not exercised against a live Plausible account, so service reliability was not assessed.
- What worked
- The privacy model and event API matched the requirement well. The official tracker could be kept disabled until a production domain was configured, while typed allowlists prevented identifiers and free-form content from entering payloads.
- What got in the way
- Final deployment still required creating a site, setting its domain, and defining event goals in the hosted service.
