The Gravity Forms Partial Entries Add-On is a powerful lead-recovery tool that acts like an “abandoned cart” system for WordPress forms. It captures data in real-time as users type, allowing you to collect information even if the “Submit” button is never clicked.
This is EXACTLY the same product as distributed by the developer. Sales Page
| Feature | Details |
| Developer | Rocketgenius (Official Gravity Forms Team) |
| License Requirement | Included with Elite and Nonprofit licenses |
| Current Version | 1.8.x (as of early 2026) |
| WordPress Compatibility | Requires WordPress 5.9 or higher |
| PHP Requirements | PHP 7.4 or higher (8.0+ recommended) |
| Database Impact | Uses standard gf_entry_meta table (increases MySQL resource usage) |
The add-on uses the WordPress Heartbeat API to save field data approximately every 30–60 seconds. It also triggers a save when:
A user navigates between pages on a multi-page form.
A validation error occurs during a submission attempt.
The “Save and Continue Later” link is clicked.
You can prevent your database from filling up with “junk” partial entries by setting specific rules:
Save on Progress: Only save once a user has completed a certain percentage (e.g., $20\%$) of the form.
Field-Based Logic: Only save if a critical field (like the Email Address) has been filled out.
Warning Message: You can display a custom message to users informing them that their progress is being saved automatically.
GDPR Compliance: Includes settings to manage personal data and ensure you aren’t capturing information against user consent.
Dashboard View: Partial entries appear in the standard Entries list but are marked with a “Progress” indicator (e.g., $45\%$).
Abandonment Analytics: Helps identify “friction points” by showing exactly where users stop filling out the form.
File Uploads: Files are not saved until the form is fully submitted.
Credit Card Data: For security and PCI compliance, credit card fields are never stored as part of a partial entry.
Save & Continue Sync: Partial entries and “Save and Continue” drafts are stored in different database tables and are not synchronized. Editing a partial entry in the backend will not update a user’s saved draft.
Hosting Constraints: Some managed hosts (like WP Engine) may disable the Heartbeat API by default, which can prevent the auto-save feature from working.
