Skip to content

Plausible Analytics

Plausible shows which pages people visit, how they arrive, and whether they complete a goal you define.

Visit Plausible Analytics

Did the launch email lead to a booking?

Tag the link in your launch email so Plausible can group visits from it. Add a goal for the result you want to count. If customers can reach a confirmation page without a booking, ask your developer or coding assistant to send a named event after the booking saves successfully. A button click can count an attempt that fails.

Add the test or production site in Plausible and place its tracking snippet in your site’s HTML header. To tag the email link, add a campaign label such as utm_source=newsletter. Plausible can use the label to group that traffic.

How can you tell whether the goal fires at the right time?

Use a disposable copy with fake records and a separate Plausible test site. Confirm the copy cannot write to live records, send real email or submit analytics to your production site. Use a regular browser that can load the test script. If you cannot verify those connections, inspect the success handler and goal settings without submitting anything.

  1. Register the preview and set up the goal
    Add the actual disposable preview hostname to Plausible as its own site. The hostname is the address between https:// and the first slash. Install the snippet from that site and create a custom event goal named Booking Saved. Use that exact name in the code that runs after a successful save.
  2. Try a failed save and a successful one
    First reject an invalid time using the test copy. In the browser’s Network panel, confirm no Booking Saved request. Then save one valid booking and look for one request carrying that event name and no private fields.
  3. Check the test report
    A request in Network shows the browser sent the event. In its response headers, x-plausible-dropped: 1 means Plausible rejected it. Check the registered preview hostname and try a regular browser. Then check the goal in the test dashboard for the test date. If the event still does not appear, compare the request’s site and event name with the test site and goal.

Does Plausible remember who booked last week?

Plausible says it uses no analytics cookies or persistent visitor identifiers. Its daily identifier is scoped to a site and device, so a visitor count cannot follow the same customer across days or devices. Keep the booking history in your app. Keep names, private links and account identifiers out of page paths and any event data you add.

What counts toward the bill?

The hosted Starter plan lists US$9 per month at the tier covering up to 10,000 combined pageviews and custom events monthly, for one site. A pageview plus a separate custom event uses two units. A goal based on an already counted pageview adds no separate unit. Business includes funnels, custom properties and the Stats API.

A one-month traffic spike does not require an upgrade. After two consecutive months above the tier, Plausible asks you to upgrade and can temporarily lock the dashboard if you do not. Collection continues during that lock.

What can you take with you?

Download CSV summaries for a date range or goal. The site-settings export includes native statistics to date, while imported data can be included in the dashboard export. Keep your goal definitions separately. The Stats API returns aggregated figures on eligible plans. Scheduled exports of individual events and sessions are an Enterprise option.