Description
One plugin for everything your Contact Form 7 forms collect: the entries that were sent, the ones that were started but never sent, and optional support for AI assistants that fill in forms for visitors.
Saved entries
- Every submission is kept — each Contact Form 7 entry is saved in your own database, even when the notification email fails to send. Spam is kept separately for 30 days so you can rescue false positives.
- Encrypted at rest — field values, IP address and uploaded files are stored AES-256-GCM encrypted; only administrators can read them in the admin area.
- Uploaded files included — files sent through the form are saved with the entry (encrypted, up to 25 MB each) and can be downloaded from the entry screen.
- Entries screen — its own menu item with an unread counter, forms with unread entries first, unread/read/spam/trash, exact search by email or phone, entry details with page, IP and how many times the same contact abandoned the form before submitting, and bulk actions.
- Readable field names — columns, entry details and reports show the field labels from your form instead of tag names such as
text-925. You can correct a label in the form editor. - Import from other plugins — move your existing entries from Contact Form CFDB7 and Flamingo, including CFDB7 files. The other plugin’s data is not changed, and running the import again never creates duplicates. Once everything is copied and verified, the plugin offers to deactivate the old one.
- Export — a CSV file per form, or every form at once to an Excel workbook with one sheet per form. Check and adjust the column headings before downloading.
- Your rules — turn saving on or off per form, keep entries forever or for a set number of days. Contact Form 7’s
do_not_storesetting and theconsent_for:storageacceptance box are respected.
Abandoned forms
The plugin also shows you the abandoned forms — the ones that were never sent. It watches field activity on the forms you already have, and the moment a visitor who was genuinely typing leaves the page or goes idle without submitting, it records what they had entered so far.
- Catches real abandonment, not noise — a visitor has to actually type something recognizable as input before a leave or a long idle period counts as an abandoned attempt; accidental page loads and bot traffic don’t pollute the data.
- Only leads you can follow up on — optionally record an attempt only when the visitor left a complete email address or a phone number, so a visitor who typed just their name doesn’t clutter the list.
- Per-form breakdown — totals for the last 7 days, last 30 days and all time for every tracked form, drilling down into the field values captured for that form.
- Form conversion — see started, submitted and abandoned attempts and the abandonment rate for the last 30 UTC days.
- Privacy-aware — integrates with WordPress’s built-in Personal Data Export/Erase tools for both entries and abandoned-form data. A configurable retention period (default 60 days) deletes old abandoned events automatically every day.
- Your data stays on your site — the free version makes no outgoing requests of its own; everything is stored locally and shown only to users with the right capability.
WebMCP for AI assistants (experimental)
WebMCP is a proposed web standard that lets an AI assistant working in the visitor’s browser understand a form instead of guessing from the page layout. Other browsers simply see your normal form.
- Off by default — you enable it per form, after checking the purpose and field descriptions the assistant will read. If you later change the form, it pauses until you review it again.
- The visitor stays in control — an assistant can fill in the fields, but the visitor reviews them and presses send. Contact Form 7’s validation, spam protection and delivery work as usual. Consent checkboxes are always left for the visitor to tick.
- See what happens — anonymous counts of forms filled by an assistant, then submitted, abandoned or cancelled. No field values are collected for these counts.
- Light on your pages — the small script loads deferred, and only on pages that show an enabled form.
WebMCP is still an experiment in Chrome: visitors’ browsers show your forms to an assistant only if your site has a free origin trial token, or if the visitor has turned the feature on. The plugin’s AI agents screen explains how to get a token and tells you when it needs renewing. Complex conditional forms may need a separate check.
A note on scope
This plugin requires Contact Form 7 to be active — it has nothing to track without it.
Pro version
The Pro version is a separate, paid version. Everything described above works fully in this free plugin; Pro adds tools for actually following up on abandoned attempts:
- Trend chart — a 30-day line chart of abandoned events, for all forms combined or any one form, right on the same screen as the data.
- Field drop-off — see which fields were reached and the last field interacted with in abandoned attempts.
- Recovered leads — see saved abandoned contacts who later successfully submit the same form.
- Lead review — how complete each saved attempt is, whether it has a usable contact, and explained “worth checking” signs such as repeated text. These are hints only: nothing is deleted or blocked automatically.
- CSV export — download a form’s abandoned events, including every captured field, as a spreadsheet-ready CSV file.
- Webhook notifications — get notified the moment someone abandons a tracked form, via Mattermost/Slack, Telegram, Discord, or a generic JSON webhook of your own. Delivery is asynchronous, so a visitor’s browser never waits on it.
External services
This plugin connects to the following third-party service. Nothing else is sent anywhere by the free version.
Freemius (optional opt-in, licensing and updates of the Pro version)
The plugin includes the Freemius SDK, which handles the separate Pro version’s licensing and updates. In this free version, Freemius only shows an optional opt-in screen after activation.
- When: only if you choose to opt in (or activate a Pro license).
- What is sent: your site URL, WordPress and PHP versions, plugin version, site language, and the admin’s name and email address, plus plugin activation/deactivation/uninstall events. If you skip the opt-in, nothing is sent.
- Freemius Terms of Service, Privacy Policy and details on what is collected.
Support
Questions, bug reports or feature requests: the plugin’s support forum on WordPress.org, or https://rowan-web.ru/en/blog/rowanweb-abandoned-forms-for-contact-form-7/
Installation
- Make sure Contact Form 7 is installed and active.
- Upload the
rowanweb-abandoned-forms-for-contact-form-7folder to/wp-content/plugins/, or install the ZIP via Plugins → Add New → Upload. - Activate the plugin.
- In the Contact menu you will find three items: Saved entries lists entries and offers to import them from Contact Form CFDB7 or Flamingo if it finds any; Abandoned Forms shows abandoned attempts and holds the settings; AI agents turns on WebMCP for the forms you choose.
FAQ
Does this work without Contact Form 7?
No — the plugin hooks directly into Contact Form 7’s own forms and does nothing without it active (declared as a dependency, so WordPress will flag it if CF7 isn’t active).
Can it replace Contact Form CFDB7 or Flamingo?
Yes. It saves every new entry, and the Entries tab offers to import the entries those plugins already stored — CFDB7 entries with their uploaded files, Flamingo entries including spam. Import works even if the other plugin is already deactivated, never changes its data, and skips entries that were already imported. When every entry and file has been copied and verified, the plugin offers to deactivate the other plugin; its data is not deleted.
Are uploaded files saved?
Yes, encrypted, up to 25 MB per file (filter cf7at_submission_max_file_bytes). They live in wp-content/uploads/cf7at-files/ under random names without extensions, so even a direct link only returns encrypted bytes. Administrators download them from the entry screen.
What happens if the encryption key is lost?
Entries and abandoned-form data are encrypted with a key stored in your database (or in the CF7AT_ENCRYPTION_KEY constant, if you define one). When moving the site, move the whole database. If the key changes, old entries are shown as “encrypted with a different key” rather than as empty values. Export to CSV or Excel if you want an independent copy.
I updated from version 0.2 — why aren’t entries being saved?
On sites that used an earlier version, saving entries stays off until you decide. The Entries tab shows a notice with “Save entries of all forms”; you can also turn it on for a single form in the form editor (“Saved Entries” tab).
What counts as “abandoned”?
A visitor who has typed something recognizable as real input into a form’s fields, then either leaves the page, closes the tab, or goes idle for a while without submitting. Loading a form and leaving immediately, without typing anything, isn’t recorded.
What is WebMCP, and do I need it?
It is a proposed browser standard that lets an AI assistant in the visitor’s browser fill in a form reliably. You don’t need it for anything else in this plugin, and it stays off until you enable it for a form. Today it is experimental and mainly useful if you want to be ready early.
Can an AI assistant send a form on its own?
No. The plugin never enables automatic sending: the assistant fills in the fields and the visitor reviews them and presses send. Consent checkboxes are cleared for the visitor to tick personally.
Why do I need a token for WebMCP?
Chrome still treats WebMCP as an experiment and enables it for a site only when its pages carry a free origin trial token issued for that site, unless the visitor has turned the feature on. Register your site address with Chrome, paste the token on the AI agents screen, and the plugin adds it to your pages while at least one form is enabled. The plugin itself contacts no one. Without a token your forms keep working as usual.
My theme prints the same form twice (for example, in the footer and in a modal). What does the assistant see?
One tool per form on each page: only the first copy of the form is offered to the assistant, so it never has to choose between identical tools. The tool is named after the form ID, for example contact_form_123, and keeps that name on every page. The AI agents screen tells you when a form was seen more than once on a page.
To offer another copy instead, use the cf7at_webmcp_instance filter. It receives true for the first copy, the form, the copy’s number on the page (1, 2, …) and its CF7 unit tag:
add_filter( 'cf7at_webmcp_instance', function ( $use, $form, $ordinal ) { return 123 === $form->id() ? 2 === $ordinal : $use; }, 10, 3 );
The form is in a closed modal. Will the visitor see what the assistant filled in?
When an assistant starts filling a form, the plugin scrolls a visible form into view. It cannot open your theme’s modal, so for a hidden form it sends the cf7at:agentactivated event (it bubbles from the form; event.detail holds formId and toolName) and scrolls to the form once your theme shows it:
document.addEventListener( 'cf7at:agentactivated', function ( event ) { var modal = event.target.closest( '.my-modal' ); if ( modal ) { modal.classList.add( 'is-open' ); } } );
My theme fills hidden fields when a visitor clicks the button that opens the form. What about assistants?
An assistant calls the form directly and does not click that button, so anything your theme does on that click (remembering which file was requested, filling a hidden field, preparing a download after sending) does not happen. Do the same in a cf7at:agentactivated handler. The plugin never changes hidden fields or Contact Form 7 events: the visitor still sends the form with the usual button, and your after-sending actions run as they do for any visitor.
Why was WebMCP turned off for my form?
Support pauses when a form’s fields change (a field added, removed, renamed or made required, or its choices edited), because the reviewed descriptions may no longer match. Editing other text or the layout keeps it on. The Contact Form 7 editor of that form and the AI agents menu item show when a form needs a new review.
Does WebMCP slow down my site?
No noticeable effect. The script is small, deferred, loaded only on pages with an enabled form, and stops immediately in browsers without WebMCP.
Is the data safe?
Entries, uploaded files and captured field values are encrypted (AES-256-GCM), decrypted only when an authorized admin views them. A contact is pseudonymized internally through a hashed, site-specific identifier rather than stored as a plain lookup key.
Does this send any of my data anywhere?
No. The free version makes no outgoing connections of its own — everything is stored in your own database and shown only inside your own admin area. The only exception is listed under “External services” below, and it’s off until you opt in.
How long is the data kept?
Abandoned-form data: 60 days by default, deleted automatically every day; configurable from 1 day up to 10 years on the Settings tab. Saved entries: forever by default, or a number of days you choose; spam and trashed entries are deleted after 30 days. Lower it if you only need the data for a quick follow-up; raise it if you want a longer history.
Screenshots





Changelog
0.4.2
- Fixed: a valid WebMCP origin trial token was shown as “Wrong address” and not added to pages, because Chrome writes the site address with the default port (https://example.com:443). Tokens already saved start working after the update, with no need to paste them again.
0.4.1
- Fixed: WebMCP offered several identical tools when a page printed the same form more than once; now only the first copy is offered, and the
cf7at_webmcp_instancefilter can choose another. - Improved: WebMCP tool names are the same on every page (
contact_form_<ID>). - Improved: when an assistant starts filling a form, the form is scrolled into view; a hidden form sends the
cf7at:agentactivatedevent so the theme can open its modal. - Improved: editing a form’s text or layout no longer turns WebMCP off, only changing its fields does. Forms switched off are flagged in the form editor and on the AI agents menu item.
- Improved: the AI agents screen highlights fields whose description only repeats the field name, lists file uploads the visitor attaches personally, and notes forms printed more than once on a page.
- Fixed: vertically centered icons in CSV and Excel export buttons.
0.4.0
- New: the plugin now has a name that says what it does; the slug and your settings are unchanged.
- New: experimental WebMCP support, off by default and enabled per form, so AI assistants can fill in forms while visitors review and send them. Includes anonymous counts and an optional origin trial token.
- New: field labels instead of tag names in entries, reports and exports, with manual corrections in the form editor.
- New: one export dialog to check and adjust column headings before downloading CSV or Excel.
- New: a separate Saved entries menu item; forms with unread entries are highlighted and listed first.
- New: after a verified complete import, the plugin offers to deactivate CFDB7 or Flamingo. Their data is not deleted.
- Improved: admin screens redesigned, with one settings form and clearer notification channels.
- Pro: lead review with explained “worth checking” signs.
0.3.0
- New: saved entries. Every Contact Form 7 submission is stored in your database, encrypted — including entries whose notification email failed and spam (kept 30 days). Per-form switch in the form editor; sites updated from 0.2 decide on the plugin page.
- New: Entries screen — entries by form, unread/read/spam/trash, exact search by email or phone, entry details with page, IP and “abandoned before” count, bulk actions, CSV export, unread counter in the menu.
- New: uploaded files are saved with the entry, encrypted, and downloadable only by administrators.
- New: import from Contact Form CFDB7 and Flamingo, including CFDB7 files. The other plugin’s data is not changed; running the import again does not create duplicates.
- New: retention setting for entries (forever by default), privacy export/erase, full cleanup on uninstall.
0.2.1
- Fixed: the plugin menu item disappeared under Contact Form 7 6.2.4.1 and later, which moved its admin menu.
- Fixed: uninstall now also removes leftover rate-limit counters.
- Improved: nothing is written to the PHP error log unless WP_DEBUG is enabled.
0.2.0
- New: anonymous form conversion report (started, submitted, abandoned and abandonment rate) for the last 30 UTC days. Data collection starts with this update; saving filters do not affect anonymous counts.
- Pro: field drop-off report showing which fields visitors reached and where their last interaction occurred before abandonment.
- Pro: recovered leads, matched to a subsequent successful submission of the same form by email or phone; recovery dates in the event list.
- New: one-time optional review request on the plugin settings screen after 14 days and at least 5 saved abandoned forms.
- Improved: unique Composer autoloader, updated bundled dependencies, versioned ZIP builds and plugin homepage link.
0.1.1
- New per-form option: only record attempts where the visitor left an email address or phone number. Detected by value in any typed field, so phone numbers in plain text fields count too.
0.1.0
- Initial release: abandoned-submission tracking for Contact Form 7, encrypted storage, per-form admin screen with bulk delete, configurable retention, GDPR personal-data export/erase integration, and a Pro tier (trend chart, CSV export, Mattermost/Slack/Telegram/Discord/generic webhook notifications).
