Spark GF Failed Submissions

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

Share of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

Refined from the date this plugin crossed into its current band.

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. A small install base leaves thin data to model from.

1. ★★★★★ UmbrellaWeb

   6.6y ago

   This is a great addition to gravity forms. Well done dev team. Knowing which forms have submission failures can help greatly to ensure your forms are working correctly. Love how it works. Would have give it 5* if not for some minor (essential) item missing. Multiple failure submissions are now logged and there is no way to remove them from the DB which can lead to a bloated DB. Yes you can change the threshold but when you find multiple bots or genuine failed submissions come through it quickly bloats the DB. Good thing its uses INNODB as its structure. Having a simple select and delete options is definitely essential in my opinion. Also combine with that filtering i.e. by IP address (same IPs) you can quickly see which IP addresses failed submissions come from, identify them and blacklist them. Currently very cumbersome to identify the same IP etc. Hope the developers can update this awesome plugin with those 2 features 🙂

   Read on wp.org ↗

1 disclosed vulnerability on record for this plugin, fixed in the current version. Sites on older versions stay exposed until they update.

1. Medium · 6.1 Spark GF Failed Submissions <= 1.3.5 - Reflected Cross-Site Scripting ↗
   2025-04-10 CVE-2025-32670 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') Affects <= 1.3.5 Patched in 1.3.6

Automated install-time checks, tested on PHP 8.1.12 · WP 6.8.2

Translated into 1 language, 0 at 90% or more

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

1. 2026-07-11 60+ → 70+ up after 85 days in tier
2. 2026-04-17 70+ → 60+ down after 51 days in tier
3. 2026-02-25 60+ → 70+ up after 80 days in tier
4. 2025-12-07 70+ → 60+ down after 44 days in tier
5. 2025-10-24 80+ → 70+ down after 6 days in tier
6. 2025-10-18 70+ → 80+ up after 1 days in tier
7. 2025-10-17 80+ → 70+ down after 1 days in tier
8. 2025-10-16 70+ → 80+ up after 1 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

• R Reject Urls And Emails In Textarea For (Gravity Forms) 700+ installs · 4.0★ · 2 shared tags D
• Real Time Validation For Gravity Forms 500+ installs · 4.1★ · 2 shared tags B
• Gravity Forms Zero Spam 100K+ installs · 4.2★ · 1 shared tag A
• Check & Log Email – Easy Email Testing & Mail logging 100K+ installs · 4.8★ · 1 shared tag A
• Advanced Custom Fields: Gravity Forms Add-on 30K+ installs · 4.1★ · 1 shared tag B
• Gravity PDF 20K+ installs · 4.9★ · 1 shared tag B

Embed this report card

Drop a live Pulse card for Spark GF Failed Submissions into a readme, a review or a deck. It updates itself.

Spark GF Failed Submissions: 70+ active installs, 4.0★ (1 reviews). Plugin Pulse (WP Mayor), as of 2026-08-31. https://plugins.wpmayor.com/plugin/spark-gf-failed-submissions