poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of rfacebookstat and rgoogleads — release velocity, themes, recent moves, and the top alternatives to consider.
A Facebook Marketing API client for R whose release schedule belongs to Meta, not its author.
rfacebookstat wraps the Facebook Marketing API for R analysts, and nearly every release is a migration to a newer API version — v14, v15, v16, v19, v20 all appear in this window. Feature work rides along with those migrations: fbGetAdAccounts() gained a spend_cap field, and fbGetMarketingStat() gained use_unified_attribution_setting, which switches results to the ad-set-level attribution settings and overrides the older account-level argument.
A Google Ads API client for R that exists to stay one step ahead of deprecation.
rgoogleads gives R analysts access to the Google Ads API, and its release log is essentially a list of API versions cleared: v10, v11, v13, v14, v16. The last substantive code change was 0.9.2, which rebuilt gads_get_geo_targets() after Google started publishing its region reference as a zip archive instead of a plain CSV, forcing the function to download and unpack before reading.
rfacebookstat wraps the Facebook Marketing API for R analysts, and nearly every release is a migration to a newer API version — v14, v15, v16, v19, v20 all appear in this window. Feature work rides along with those migrations: fbGetAdAccounts() gained a spend_cap field, and fbGetMarketingStat() gained use_unified_attribution_setting, which switches results to the ad-set-level attribution settings and overrides the older account-level argument.
The package's direction is set almost entirely by Meta's deprecation cycle, and the release notes read as a log of keeping up. The attribution work is the one strand with its own logic: an argument added in 2.10.0, then fixed in 2.12.1 when it turned out not to apply unless fetch_by was also used. Three versions cut within four and a half hours on one day in April 2023 show migrations being cleared in batches rather than steadily.
The next release will almost certainly be a migration to a newer Marketing API version, since that has triggered every version in this history; whether anything else ships with it depends on what Meta changes.
rgoogleads gives R analysts access to the Google Ads API, and its release log is essentially a list of API versions cleared: v10, v11, v13, v14, v16. The last substantive code change was 0.9.2, which rebuilt gads_get_geo_targets() after Google started publishing its region reference as a zip archive instead of a plain CSV, forcing the function to download and unpack before reading.
Development is reactive by design — the package changes when Google changes, and the notes rarely describe anything else. The deeper rework happened earlier, in 0.7.0, when request generation was centralised into gads_make_request() and gads_customer() was rewritten onto SearchStream after the old get method was retired. Since then the structure has held and releases have thinned to version bumps, with the most recent gap running over a year.
The next release will be a migration to a newer Google Ads API version, and on this history it will arrive when the current one nears sunset rather than on any schedule of the maintainer's own.
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 rfacebookstat or rgoogleads.
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
An urban accessibility toolkit that grew into a distributional-equity toolkit.
The Carpentries' lesson skin, rebuilt on Bootstrap 5 with dark mode and a wider reach.
A project-bound modelling package that shipped its final scenario workflow and stopped.
A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.
The utility layer under KWB's R packages, growing by accretion one helper at a time.
See all rfacebookstat alternatives → · See all rgoogleads alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package, api-migration, marketing-analytics — within Analytics. rfacebookstat and rgoogleads are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. rfacebookstat and rgoogleads are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top rfacebookstat alternatives in Analytics are ranked by recent ship velocity. Browse the "rfacebookstat alternatives" section above for the current picks, or visit /alternatives/rfacebookstat for the full list with editorial commentary on each.
Top rgoogleads alternatives in Analytics are ranked by recent ship velocity. Browse the "rgoogleads alternatives" section above for the current picks, or visit /alternatives/rgoogleads for the full list with editorial commentary on each.