tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of dowhy and Fathom Analytics — release velocity, themes, recent moves, and the top alternatives to consider.
DoWhy adds one estimation method a year and keeps its identification edge.
DoWhy is at v0.14, which added a doubly robust estimator and Python 3.13 support. The releases before it followed the same shape: v0.13 brought the Generalized Adjustment Criterion for identification, v0.12 added time-series effect estimation and a rank-based anomaly scorer. Between the feature releases sit patch versions handling pandas and CUDA breakage.
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.
DoWhy is at v0.14, which added a doubly robust estimator and Python 3.13 support. The releases before it followed the same shape: v0.13 brought the Generalized Adjustment Criterion for identification, v0.12 added time-series effect estimation and a rank-based anomaly scorer. Between the feature releases sit patch versions handling pandas and CUDA breakage.
Two threads run through the window. The identification side — DoWhy's differentiator against libraries that only estimate — keeps gaining criteria, from frontdoor with multiple variables through the Generalized Adjustment Criterion. The GCM side grows separately with missing-data handling, classifier selection logic and calibration work. The two halves are converging on a single API rather than staying separate entry points.
Given the pace of one estimator or criterion per release and the experimental flags still on missing-data support in GCM, the next release most likely promotes existing experimental features rather than opening a new estimation family.
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 dowhy or Fathom Analytics.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
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 dowhy 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 dowhy alternatives in Analytics are ranked by recent ship velocity. Browse the "dowhy alternatives" section above for the current picks, or visit /alternatives/dowhy 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.