TechXaro Abandoned Form Recovery

TechXaro Abandoned Form Recovery gives you a free, privacy-aware way to see where visitors start, stop, and abandon forms on your WordPress site. It helps you spot friction in the form experience and recover missed leads without sending form data to a remote AI service.

This plugin is designed for the free WordPress.org distribution and focuses on the core lead-recovery workflow:

• Track started, in-progress, abandoned, and completed form sessions
• Detect inactivity and abandonment automatically
• Capture generic HTML form activity and builder-specific completion signals
• Review entries in a clean admin dashboard
• Review privacy and consent settings from a dedicated screen
• Receive optional admin email alerts for abandonments and repeated abandonments
• Keep data retention and privacy controls configurable

Third-Party Libraries

• Chart.js 4.5.1 – MIT – https://www.chartjs.org –
  source: https://github.com/chartjs/Chart.js
• Tailwind CSS (used at build time; the compiled stylesheet assets/css/txfra-tailwind.css is included) – MIT – https://tailwindcss.com –
  source: https://github.com/tailwindlabs/tailwindcss

Full license texts and copyright notices for these libraries are included in third-party-licenses.txt. The plugin itself is licensed under GPLv2 or later; see LICENSE.

The compiled file assets/css/txfra-tailwind.css is built from src/admin-app/components/tailwind-input.css with the “npm run build” script in package.json.

Features

• Real-time autosave of in-progress form data with consent-aware defaults
• Automatic abandonment detection based on inactivity and browser end-of-session events
• Support for common WordPress form builders and generic standard HTML forms
• Dashboard stats for started, abandoned, and completed sessions
• Filterable entry list with searchable, sortable rows
• Privacy-safe exclusions for sensitive field categories
• Optional encryption of stored values
• Retention cleanup controls for historical data
• WordPress admin notices and settings screens for site owners

Supported integrations

Form integrations are detected automatically in the background. Supported builders include Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Elementor Pro Forms, Ninja Forms, Formidable Forms, and Bricks, as well as generic HTML forms.
All product names are trademarks of their respective owners. This plugin is not affiliated with or endorsed by them.

Privacy and consent

What the plugin stores in visitors’ browsers

When tracking is enabled, the plugin sets a first-party cookie named txfra_session_id to group one visit’s form activity. Session-scoped txfra_tracking_allowed and txfra_consent_given cookies distinguish permission to track from consent granted; per-form cycle and explicit-exemption cookies let server-side builder hooks distinguish a new attempt from a late request and apply the form’s consent rule. The plugin also uses sessionStorage to remember the visitor’s choice, the visit’s landing page and which forms were already submitted, and localStorage may hold a temporary copy of in-progress form values for crash recovery. That recovery copy is removed after completion. If IP storage is enabled, visitor IP addresses are saved with entries (IPs are not stored in Minimal tracking mode). No data is sent to external services.

Nothing is captured until an administrator enables tracking. Whenever consent is required by the active settings, nothing is sent to the server, no tracking cookie is set and nothing is cached in the browser until the visitor accepts. A decline stops tracking for the rest of that tab’s session, including on exempt forms; data already sent before the decline is not deleted. In Minimal tracking mode, field values are never sent or cached in the browser – only which fields were filled. Fields whose name matches the excluded patterns (passwords, card numbers, security codes and similar) are skipped in the browser before anything is sent.

Full capture mode and consent: Consent is required according to the enabled consent setting: globally, or by the selected page-specific rules. An explicit page or form exemption does not count as visitor consent. If both consent options are off in Standard privacy mode, Full mode captures permitted values without asking; site owners are responsible for using a lawful configuration. GDPR privacy mode always requires consent. The consent banner appears when a visitor focuses a control in a tracked form, before typing. Until consent is given or tracking is allowed by an exemption or disabled consent requirement, no data is sent, no tracking cookie is set, and no recovery data is cached. If the visitor accepts, the browser records consent as given. If the visitor declines, tracking is suppressed for the rest of that tab’s browser session, including on exempt forms; data already sent before the decline is not deleted.

Page-specific consent rules: When “Use page-specific rules” is selected, the “Always require” and “Never require” lists apply. A page matching “Always require” asks for consent. A page matching “Never require” is exempt. A page matching neither list asks for consent in Full capture mode, but not in Minimal capture mode. If neither consent option is enabled, consent is not requested and Full mode may capture permitted field values.