Separate interest from a completed action
A visitor can click Start trial without creating an account. Another can submit a form that the backend rejects. Decide which observation you need before setting up a conversion goal. Plausible supports goals based on pageviews or custom events, giving you different ways to represent those actions.
For an illustrative demo-request site, record Demo CTA clicked as an expression of interest and Demo request saved only after the receiving system accepts a valid request. Keep the labels literal. Calling both events Lead would make the dashboard look simpler while making the outcome harder to interpret.
Choose a pageview goal or a custom event
A pageview goal can suit a meaningful confirmation page if that page is reached only through the intended workflow. A custom event is more suitable when the action happens without navigation or you need to emit a confirmed outcome. Check whether revisiting a confirmation URL would create a misleading result before choosing the easier setup.
Plausible documents CSS-class tracking for interactions and a JavaScript approach for more advanced conditions. A class on a submit button measures that interaction; it cannot establish that your backend saved the request. For a success event, connect the tracking decision to the application's actual success response.
| Question | Candidate signal | Interpretation limit |
|---|---|---|
| Did the offer attract interest? | Demo CTA clicked | A click is not a saved request |
| Did the website accept a request? | Demo request saved | Acceptance is not a qualified customer |
| Did the visitor reach a relevant page? | A pageview goal | Revisits may not represent a new outcome |
| Was a purchase confirmed? | A verified purchase event | Use the actual transaction outcome |
Give events names you can maintain
Keep the name used by the website and the dashboard goal aligned. Record the exact name, when it fires, and who owns the implementation. Use a stable event name for the action instead of putting a customer's name, email address, or request text into it.
If several pages offer the same demo, decide whether the action should remain one goal with a useful page context or several separately meaningful goals. Do not create a different label for every button color or minor wording change. The report should remain understandable after the page is redesigned.
Verify tracking through a real navigation sequence
Plausible's SPA documentation describes support for modern pushState-based routers and a separate setup consideration for hash-based routing. Inspect the implementation in your actual framework, including whether a script has been installed twice. Verify navigation and custom actions independently.
Open the site with a test visit, navigate to the offer, complete one valid request, and inspect the expected network activity and dashboard goal. Then submit an invalid request and revisit the confirmation state. The verification target is the event contract you wrote, not merely seeing some traffic appear.
Read conversions alongside the traffic that produced them
Use a configured goal to investigate relevant landing pages and referral sources. Compare visits and completed actions over a consistent period. In a fictional example, 12 accepted requests from 200 visits is a different observation from 40 CTA clicks from the same visits. Neither establishes how many paying customers followed.
If the final action happens in another application or on another domain, verify the full measurement path rather than assuming the website report follows the person everywhere. Keep acquisition reporting separate from detailed account activation and billing records. Each system should answer the question it can actually observe.
Budget for the events you add
Plausible's custom-event documentation notes that custom events count toward billable monthly pageviews. Estimate repeated interactions as well as visits when checking the current plan. A noisy event that fires on every input change can add volume without helping anybody make a decision.
Start with a few well-defined outcomes and review their usefulness before expanding. Plausible is a candidate when a focused website view of sources, pages, and conversions meets your decision needs. The useful result is a report you can explain and verify, with a clear distinction between interest, accepted requests, and downstream customer outcomes.
Sources and editorial method
Official sources linked in this guide were checked on October 27, 2026. Features, interfaces, and commercial limits can change. The examples are proposed workflows and illustrative calculations, not customer results or a hands-on product benchmark. Confirm the current documentation before implementing the workflow.