Plugin profile · observed daily since 02 Aug 2026
Raptive Ads
Active installs6,000+ rounded
Current authorRaptive
Owner changesNone while we have been watching
Last release2 months ago 07 Jul 2026
Support0 / 1 resolved, last 2 months
Releases on record54
Rating5.0 /5 · 3
Added to directory21 Mar 2016
Requires WP4.6
Requires PHP5.6
Version lag0.1 behind
Tested up toWP 7.0.4 WordPress is now on 7.1
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by Raptive throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| adthrive | 44 | 10 Sep 2020 | 12 Apr 2025 |
| raptive | 10 | 12 May 2025 | 07 Jul 2026 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Moderately adopted: 6,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
43 downloads a day over the last 7 days, falling 14% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 146/day28 Aug 2026
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 15 Aug | 16 Aug | 17 Aug | 18 Aug | 19 Aug | 20 Aug | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 22 | 23 | 49 | 0 | 146 | 44 | 0 | 67 | 0 | 44 | 33 | 78 | 76 |
Unchanged throughout: ratings total (3) · active installs (6,000+) · version (3.13.0) · support threads (1) · threads resolved (0)
27 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory10 years ago 21 Mar 2016
Requires WP4.6
Requires PHP5.6
Version lag0.1 behind
Is anyone still maintaining this?
- Last released 07 Jul 2026, 53 days ago.
- Declares compatibility only up to WordPress 7.0.4, while 7.1 is current. The author has not confirmed it runs on the last 1 release.
- 0 of 1 support threads answered in the last two months.
- The same account maintains 1 other plugin; the most recent update to any of them was 10 Sep 2025.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 02 Aug 202627 days agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 07 Jul 20262 months agoVersion 3.13.0 released
- 15 Apr 20264 months agoVersion 3.12.2 releasedfrom the release logCommitted by raptive.
- 03 Mar 20266 months agoVersion 3.11.0 releasedfrom the release logCommitted by raptive.
- 27 Jan 20267 months agoVersion 3.10.0 releasedfrom the release logCommitted by raptive.
- 20 Aug 202512 months agoVersion 3.9.0 releasedfrom the release logCommitted by raptive.
- 16 Jul 202513 months agoVersion 3.8.0 releasedfrom the release logCommitted by raptive.
- 08 Jul 202514 months agoVersion 3.7.7 releasedfrom the release logCommitted by raptive.
- 08 Jul 202514 months agoVersion v3.7.7 releasedfrom the release logCommitted by raptive.
- 12 May 202516 months agoVersion 3.7.5 releasedfrom the release logCommitted by raptive.
- 12 May 202516 months agoVersion 3.7.6 releasedfrom the release logCommitted by raptive.
- 12 Apr 202517 months agoVersion 3.7.4 releasedfrom the release logCommitted by adthrive.
- 25 Mar 202517 months agoVersion 3.7.3 releasedfrom the release logCommitted by adthrive.
- 24 Mar 202517 months agoVersion 3.7.2 releasedfrom the release logCommitted by adthrive.
- 10 Sep 20205.5 years ago41 earlier releasesfrom the release logBetween 10 Sep 2020 and 20 Feb 2025. Listed individually in the public release log rather than here.
- 21 Mar 201610 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by Raptive for all 27 days we have observed it.
- It was last released 2 months ago (07 Jul 2026).
- Its author declares it tested up to WordPress 7.0.4; WordPress is now on 7.1.
- WordPress.org reports 6,000+ active installs.
- It carries 3 ratings, averaging 5.0 out of 5.
- 0 of 1 support threads in the last two months are marked resolved.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Reach out about this record
Corrections, missing context, or anything else about Raptive Ads: a person reads every submission, and corrections get a reply within 5 business days.