IntegrationsTutorial

Privacy Analytics

Plausible or Umami collector and script readiness.

Integration

Privacy Analytics

Confirms Plausible or Umami script readiness.

Privacy-first analytics still fail at launch when the site ID is wrong, the collector script is unreachable, or the snippet never made it to the public landing page. PreFlight checks collector script reachability and landing-page install so you have traffic signal without shipping a heavy third-party tracker.

Requirements

What PreFlight checks

| Probe | What it proves | | --- | --- | | Collector reachability | The Plausible or Umami script endpoint responds. | | Landing page install | The configured site ID appears in the page source or init call. | | Domain alignment | The site ID matches the domain registered in your analytics dashboard. | | Script load path | The public URL serves HTML that references the collector. |

Failure guidance

| Symptom | Fix | | --- | --- | | Script not on page | Install the collector snippet on the public landing page with the exact site ID. | | Wrong site ID | Copy the site ID from Plausible or Umami settings and redeploy. | | Collector unreachable | Confirm the script URL and any self-hosted Umami instance are publicly accessible. | | Domain mismatch | Register the production domain in your analytics dashboard before launch. |

Dashboard setup

Navigate to Integrations → Privacy Analytics in your PreFlight project. Select Plausible or Umami and paste the site ID, script URL, and landing page URL. Deploy the collector snippet to the landing page if not already present. Run Pre-Flight Check and confirm collector and install probes pass.