Eatransform FormLeak shows you exactly where visitors hesitate and leave your contact or booking forms, so you know what to fix.<\/p>\n\n
navigator.sendBeacon<\/code> so abandonment data is captured reliably even when the visitor closes the tab.<\/li>\n- Automatically scans input fields inside
<form><\/code> elements, including Contact Form 7, MW WP Form, WooCommerce, and forms rendered dynamically via JavaScript (detected with MutationObserver).<\/li>\n- The dashboard shows a \"drop-off risk score\" for each field, so you can see at a glance which field is the biggest obstacle.<\/li>\n<\/ul>\n\n
Privacy<\/h4>\n\n
FormLeak never collects the content typed into form fields. It only stores behavioral statistics: time spent per field, backspace count, and error count.<\/p>\n\n
Data Collection Security<\/h4>\n\n
The data collection endpoint only accepts requests originating from the same site and applies a per-IP rate limit.<\/p>\n\n\n
\n- Upload the plugin to
wp-content\/plugins\/<\/code> and activate it.<\/li>\n- Visitor interactions on pages with forms are recorded automatically.<\/li>\n
- Check the drop-off risk score for each form under \"FormLeak > Dashboard\" in the admin menu.<\/li>\n
- (Optional) If you need to track a JavaScript form that doesn't use a
<form><\/code> tag, specify its CSS selector under \"Settings\".<\/li>\n<\/ol>\n\n\n\nDoes this collect any personal information?<\/h3><\/dt>\nNo. FormLeak only measures behavior (time on field, backspaces, errors). The text a visitor types is never sent to the server or stored.<\/p><\/dd>\n
Does it work with page builders or custom JavaScript forms?<\/h3><\/dt>\nYes. Standard <form><\/code> elements are detected automatically. For JavaScript-rendered forms without a <form><\/code> tag, you can specify a CSS selector in Settings.<\/p><\/dd>\n\n<\/dl>\n\n\n1.3.7<\/h4>\n\n\n- Applied a unique prefix (eatrfo_ \/ EATRFO_ \/ Eatrfo_) to all classes, constants, options, transients, cron hooks, REST namespace and script globals to prevent naming collisions, per WordPress.org review feedback.<\/li>\n<\/ul>\n\n
1.3.6<\/h4>\n\n\n- Fixed WordPress.org automated scan warning: unified Text Domain to match the plugin slug (eatransform-formleak).<\/li>\n<\/ul>\n\n
1.3.5<\/h4>\n\n\n- Fixed WordPress.org submission error: Plugin URI and Author URI were identical. Plugin URI now points to the announcement article.<\/li>\n<\/ul>\n\n
1.3.4<\/h4>\n\n\n- Renamed plugin to \"Eatransform FormLeak\" and updated slug to eatransform-formleak for the WordPress.org submission.<\/li>\n<\/ul>\n\n
1.3.3<\/h4>\n\n\n- Fixed a UI typo (\"\u4eba\u3076\u3093\" -> \"\u4eba\u5206\").<\/li>\n
- Fixed remaining misplaced phpcs:ignore comments for multi-line SQL strings; added missing NoCaching code to one ignore comment (Plugin Check: 0 errors, 0 warnings).<\/li>\n<\/ul>\n\n
1.3.2<\/h4>\n\n\n- Fixed misplaced phpcs:ignore comments so suppressions correctly target the flagged line (Plugin Check now reports 0 errors, 0 warnings).<\/li>\n<\/ul>\n\n
1.3.1<\/h4>\n\n\n- Renamed main file (formleak-ai.php \u2192 formleak.php) and unified text domain to 'formleak'.<\/li>\n
- Fixed unescaped output, missing input unslashing, and added justified phpcs:ignore comments for safe table-name SQL interpolation (WordPress.org Plugin Check clean-up).<\/li>\n
- Rewrote readme.txt in English; updated \"Tested up to\" to 7.0.<\/li>\n<\/ul>\n\n
1.3.0<\/h4>\n\n\n- Changed data retention period from 90 days to 30 days (auto-deleted after 30 days).<\/li>\n
- Added a \"last 30 days\" daily trend chart to the dashboard (submitted vs. abandoned, SVG line chart).<\/li>\n
- Added a per-session drop-off risk card with timestamp.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Removed the AI report and estimated-loss display; the plugin now focuses solely on behavior tracking and drop-off risk visualization.<\/li>\n
- Added same-origin validation and per-IP rate limiting to the data collection endpoint.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release.<\/li>\n<\/ul>","raw_excerpt":"Find out where visitors get stuck and abandon your contact or booking forms, without collecting any personal data.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/333579","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=333579"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/eatransform"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=333579"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=333579"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=333579"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=333579"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=333579"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=333579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}