What’s New — July 1–13, 2026

New

  • Your first week now starts with real history. Adding a competitor backfills its actual day-by-day install and download history from our directory archive, so charts and trends are populated on day one instead of building up over a week.

Improved

  • A quieter first week. New accounts no longer get a weekly summary before they have a full week of data, and the events already present when you add a competitor no longer arrive as a flood of “new activity” notifications.
  • Honest sync scope. The manual sync button now reads “Sync all competitors” and states that it refreshes every competitor in your account, not just the project you’re looking at.

Fixed

  • No more phantom download surges. Weekly summaries were headlining moves like “+999%” for plugins averaging one download a day. Download numbers are now read from settled days only, low-traffic plugins report an honest absolute move (“0 → 2/day”) instead of an invented percentage, and a single glitch day can no longer manufacture a spike.
  • Download charts no longer show false zeros. Days WordPress.org omits are recorded as “no data” rather than a real zero, so 60-day charts, week-over-week deltas, and playbook averages stop dragging plugins toward a fake decline.
  • “Downloads are down NaN%” is gone. Dormant plugins with no download baseline no longer produce broken percentages, phantom spike cards, or a summary whose subject line contradicts its body.
  • Competitors tracked by more than one person now sync correctly. When two accounts tracked the same plugin, syncs, project cards, insights, and lifecycle emails could read the wrong account’s data or stop silently. Every lookup is now scoped to your own competitor.
  • Reviews and releases no longer go missing. If two people tracked the same plugin, one account’s events could overwrite the other’s. Each competitor now keeps its own event history.
  • Playbooks no longer flag an old release as new. Adding a competitor whose last release was months ago stopped producing a “New release” playbook.
  • Rankings no longer report as stale when they are fresh. The freshness check on ranking data was failing on its own size and mislabelling healthy data.

Security

  • Outbound competitor-website crawls are hardened against internal network access, and personal data is kept out of internal logs.