
How-to · Published October 20, 2026
How to set up events in Plausible and Fathom
How custom events / goals work in Plausible and Fathom — when they are enough, how to keep naming simple, and when to graduate to GA4 or PostHog.
Updated
Quick answer
Quick answer
Plausible and Fathom are pageview-first. Add a handful of custom events or goals for key CTAs (signup, contact, download). They will not replace product funnels — and that is intentional for privacy-first marketing sites.
Goals, not giant taxonomies
These tools shine when you track a few conversions on top of traffic reports. Aim for five or fewer named goals on a marketing site.
If you need nested funnels, account-level retention, or experiment assignment, look at PostHog or GA4 instead.
Plausible custom events
Plausible supports custom events via a small JS API or attribute-based triggers (depending on your setup). Name events clearly (Signup, Demo Request) and verify them in the realtime dashboard.
Billing is primarily pageviews, so events are about clarity — not a separate meter in the same way event-based products charge.
Fathom events / goals
Fathom’s model likewise centers on simple site analytics plus goals for conversions. Keep the same discipline: stable names, one purpose per goal, test after deploy.
Compare pricing and UX with Plausible vs Fathom.
When to graduate
Graduate when weekly questions outgrow "traffic + one CTA": multi-step onboarding, feature adoption, or ads-heavy attribution. Until then, a light script and a short goal list beat an unused event warehouse.
Script weight context: both sit in our light performance matrix.