Migrating from Fathom Analytics: What Changes and What Maps

Fathom and Clycyo agree on the fundamentals — cookieless, banner-free, lightweight — which makes this one of the lowest-risk migrations in analytics. The move makes sense when your questions outgrow traffic and events: you want to know which channel produces paying users, why a specific visitor abandoned, or whether the checkout got slower last deploy. Here is the path.

The mechanical part (under an hour)

1. Swap the snippet. Remove Fathom's script, add Clycyo's from the quickstart. Both are single tags; SPA navigation is handled automatically.
2. Port events. Fathom events map directly: fathom.trackEvent('signup') becomes window.webanalytics.track('signup'). Clycyo events also take a properties object, which you will start using immediately ({ plan: 'pro' } beats creating three separate event names).
3. Export history. Fathom's CSV exports cover visitors, sources, and pages per period. Keep a yearly snapshot; that satisfies every realistic future lookup.
4. Parallel-run a week. Optional but calming. Both tools count cookielessly, so the curves align closely.

UTM continuity

Your existing campaign links keep working untouched — UTMs are tool-agnostic. The upgrade is what happens to them: Clycyo persists the first-touch UTM set on the visitor record, so campaign credit survives the return visit that converts days later. If your UTM naming drifted over the years, the migration is a natural moment to adopt clean conventions.

What you unlock

• Identity: identify(email) at signup merges the anonymous research phase with the known user — the cornerstone of revenue attribution.
• Revenue events from webhooks: Stripe, Polar, or any billing system posts payments server-side; they arrive pre-attributed to first touch.
• Performance per visit: load time, Web Vitals, and JS errors on each pageview — the engineering half of the picture Fathom intentionally leaves out.
• Journey timelines: the per-visitor view that turns 'conversion dropped 8%' into 'visitors from the new campaign hit a broken form'. Browse real ones in the live demo.

What to double-check before committing

• If you relied on Fathom's uptime monitoring, plan a replacement — Clycyo is analytics, not synthetic monitoring.
• If you used email reports heavily, bookmark the dashboard instead (and the public share link covers stakeholders).
• Self-hosting is not an option here: Clycyo is managed cloud only.

Start on the free tier, run the week of parallel data, and keep whichever tool answers your Monday questions faster. We are confident enough in that bet to publish our own dashboard publicly.