tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of performance and Fathom Analytics — release velocity, themes, recent moves, and the top alternatives to consider.
performance keeps adding ways to check a model you have already fitted.
performance is at 0.17.1, which added check_priors() for prior predictive checks on Bayesian models and gave check_overdispersion(), check_model() and check_predictions() arguments to control residual type and plot range. The releases before it are a similar mix: a -2LL criterion column in test_likelihoodratio(), Bayesian predictive checks routed through modelbased, and in 0.16.0 a set of breaking renames including RMSA to the correct RMSR.
Fathom rebuilds its query engine and bolts on Search Console, reaching for GA4's lunch.
Fathom shipped a complete analytics-engine rebuild in March 2026, paired with secondary dimensions, faster queries, and more accurate time-on-page measurement. The product is closing the feature gap with mainstream analytics tools while keeping its cookie-free, privacy-first stance. Recent additions — Google Search Console integration, entry/exit pages, dashboard ZIP exports, and a fresh layer of bot detection — directly target reasons users still keep GA4 open in another tab.
performance is at 0.17.1, which added check_priors() for prior predictive checks on Bayesian models and gave check_overdispersion(), check_model() and check_predictions() arguments to control residual type and plot range. The releases before it are a similar mix: a -2LL criterion column in test_likelihoodratio(), Bayesian predictive checks routed through modelbased, and in 0.16.0 a set of breaking renames including RMSA to the correct RMSR.
Two consistent habits. Diagnostics keep gaining arguments to narrow what is examined — ppc_range, x_limits, maximum_dots, show_ci — which reads as a package being used on models large and awkward enough that the defaults stopped working. And simulated residuals via DHARMa keep displacing standard ones as the basis for the checks themselves.
With check_priors() newly added and Bayesian predictive checks now routed through modelbased, the next release most likely extends the Bayesian diagnostic set rather than reworking the frequentist checks.
Fathom shipped a complete analytics-engine rebuild in March 2026, paired with secondary dimensions, faster queries, and more accurate time-on-page measurement. The product is closing the feature gap with mainstream analytics tools while keeping its cookie-free, privacy-first stance. Recent additions — Google Search Console integration, entry/exit pages, dashboard ZIP exports, and a fresh layer of bot detection — directly target reasons users still keep GA4 open in another tab.
The roadmap is clearly aimed at making Fathom a viable single-pane replacement for Google Analytics rather than a privacy-first complement to it. Expect continued investment in detection accuracy, reporting depth (custom exports, secondary dimensions), and Google-side integrations. The new analytics engine is foundational — it is what makes the next layer of features possible.
Next likely moves are deeper UTM and campaign analytics, an experimentation or goals-funnel surface, and tighter agency tooling that builds on self-serve site transfer and shared-dashboard exports.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either performance or Fathom Analytics.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
See all performance alternatives → · See all Fathom Analytics alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fathom Analytics is currently shipping more aggressively (velocity 1.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fathom Analytics is currently shipping more aggressively (velocity 1.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top performance alternatives in Analytics are ranked by recent ship velocity. Browse the "performance alternatives" section above for the current picks, or visit /alternatives/easystats-performance for the full list with editorial commentary on each.
Top Fathom Analytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Fathom Analytics alternatives" section above for the current picks, or visit /alternatives/fathom-analytics for the full list with editorial commentary on each.