How It Works

How It Works

TechXaro Abandoned Form Recovery is a WordPress plugin that records eligible form sessions, saves permitted in-progress field activity, identifies abandoned attempts, and gives site administrators a place to review form activity. It is designed to reveal where visitors leave before completing a form so site owners can investigate friction and follow up through their own existing processes.

The plugin runs inside your WordPress site and stores its records in custom WordPress database tables. No form data is sent to TechXaro or to an AI service by default.

How It Works

How it works — step by step

01

Install and activate

Upload the plugin to WordPress, activate it, and open TechXaro Abandoned Form Recovery from the WordPress admin menu. Activation creates or upgrades the plugin’s database structures and schedules retention housekeeping.

02

Enable tracking

Open Settings and enable tracking. Tracking is disabled by default; no visitor form activity is captured until the administrator turns it on.

03

Choose a capture mode

Minimal mode records which eligible fields have been filled without sending or caching their typed values. Full mode can store permitted field values, subject to the configured consent rules and sensitive-field exclusions.

04

Visitor starts a form

The front-end tracker detects interaction with supported form elements. When tracking is permitted, it creates a first-party session identifier and begins recording the form attempt.

05

Autosave captures progress

The tracker periodically sends eligible field information to WordPress using the configured autosave interval. In Full mode this may include permitted values; in Minimal mode only field completion information is sent. A temporary browser recovery cache is used only where permitted and is cleared after completion.

06

Completion or abandonment is detected

A successful form submission is marked completed. If the visitor becomes inactive for the configured threshold or leaves without completing, the attempt can be marked abandoned. A scheduled server-side sweep also converts stale in-progress records to abandoned if a browser unload signal was missed. Validation errors and failed submissions are detected in the browser, so a form cancelled by validation is not wrongly marked completed. Very fast submissions are still recorded as completed.

07

Review and act

Administrators review totals, activity trends, and individual entries in the dashboard. They can inspect captured field information where allowed, filter/search entries, and delete individual or bulk abandoned records. They also get email alerts for an abandoned form, a new submission, or repeated abandonments.

08

Maintain privacy and retention

Administrators manage consent, excluded sensitive field categories, encryption, retention windows, and optional email alerts from Settings and the Privacy Policy screen.

Supported Integrations

Supported form integrations

The browser tracker uses generic HTML form detection and the plugin adds server-side completion hooks for:

Contact Form 7
WPForms
Gravity Forms
Fluent Forms
Elementor Pro Forms
Ninja Forms
Formidable Forms
Bricks Forms
Generic standard HTML forms

Works with 8 form builders and any HTML form. All product names are trademarks of their respective owners. This plugin is not affiliated with or endorsed by them.

The builder-specific hooks provide authoritative successful-submission signals, which helps avoid treating a browser submit event as a successful completion when validation or an AJAX workflow has actually failed. Availability and behaviour should still be tested on the specific site, theme, builder versions, and custom form configuration.

For Administrators

What administrators can see

  • •Dashboard: forms started, completed, and abandoned; daily activity chart; activity timeline.
  • •Dashboard filters: device type (desktop, mobile, tablet) and date range.
  • •Entries workspace: searchable, sortable, filterable records and an individual entry detail view.
  • •Entry details: status, number of fields filled, device, consent state, session details, and captured fields where permitted. Landing page and UTM source, medium and campaign details on each entry.
  • •Privacy Policy screen: current capture/privacy settings and suggested disclosure wording.
  • •Settings: tracking status, capture mode, autosave timing, inactivity threshold, consent rules, privacy mode, encryption, retention, excluded sensitive categories, notification recipient and notification types.

Notifications

Notifications

Optional WordPress email notifications can be configured for abandoned forms, new submissions, and repeated abandonments. Repeated-abandonment alerts use a configurable threshold (1–100). A test-email action is available to verify the site’s WordPress mail configuration. These are administrator alerts; the plugin does not provide automated visitor recovery email campaigns, SMS, or marketing sequences.

Privacy & Consent

Privacy, consent and data handling

  • •Tracking is disabled until an administrator enables it.
  • •When consent is required, the visitor is shown a consent prompt on first form focus. Until consent is granted, the tracker does not send data, create its tracking session cookie, or cache recovery values.
  • •Visitors can decline. A decline suppresses tracking for the rest of that browser tab’s session; previously transmitted data is not automatically deleted by declining.
  • •GDPR privacy mode always requires consent. Standard mode follows the selected global or page-specific consent configuration.
  • •Page-specific rules use separate Always Require and Never Require path lists. Pages matching neither list require consent in Full mode but not in Minimal mode.
  • •Minimal mode does not send or cache typed field values; it records only which fields were filled.
  • •Sensitive field types and name patterns (including password and payment-card-related fields) are excluded in the browser before transmission. File contents are not captured; only file metadata may be recorded.
  • •Optional encryption protects stored values. IP addresses are not stored in Minimal mode.
  • •Retention cleanup removes old records according to the configured retention period. Deactivation keeps plugin data; uninstall removes plugin tables, options, and scheduled tasks.

Important: the site owner is responsible for choosing a lawful consent configuration, publishing an appropriate privacy notice, and confirming local legal requirements. An exemption from a page-specific consent rule is not itself visitor consent.

Recommended Setup

Recommended setup

  1. Install and activate the plugin on a staging or test site first.
  2. Enable tracking and choose Minimal or Full mode based on the site’s privacy needs.
  3. Set an autosave interval appropriate to the form’s length and visitor experience.
  4. Set the inactivity threshold so ordinary pauses are not prematurely classified as abandonment.
  5. Configure global consent or page-specific rules; review the GDPR mode implications.
  6. Review excluded sensitive categories and ensure password, payment, authentication, and other sensitive fields are never captured.
  7. Set encryption and a retention period aligned with the site’s data policy.
  8. Enter the administrator notification email, select the alert types, and send a test email.
  9. Test each supported form builder with successful submissions, validation failures, abandoned sessions, mobile devices, and consent accept/decline paths.
  10. Review the dashboard and entry records after test sessions before enabling on the production site.

Dashboard

Dashboard walkthrough

The Dashboard is the operational overview. It summarizes form lifecycle activity and provides a daily chart comparing started, completed, and abandoned sessions. Device and date filters help narrow the activity view. The timeline presents recent events so administrators can quickly see whether form activity is increasing, completing, or being abandoned.

The View Form Entries screen is the investigation workspace. Administrators can search the entry list, use the available filters and sorting, open an individual record, inspect session and field details, and remove records when appropriate. Bulk deletion controls are available for abandoned entries and older records.

Limitations

What it does NOT do

  • •It records and displays form activity; it does not automatically contact abandoned visitors or send them a resume link.
  • •It does not provide a hosted SaaS analytics account, cross-site reporting, or external AI analysis.
  • •It does not claim to recover every visitor or every browser crash. Browser unload signals can be unavailable; the server-side stale-entry sweep is a fallback.
  • •Full-mode capture depends on consent configuration and field exclusions. Site owners must validate the configuration for their jurisdiction and forms.
  • •Integration support is implemented in code, but compatibility should be verified against the actual versions of each builder and any custom AJAX/validation behaviour.

FAQ

Frequently asked questions

Does the plugin work with my form builder?

It includes generic HTML form tracking and builder-specific completion hooks for Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Elementor Pro Forms, Ninja Forms, Formidable Forms, and Bricks. Test the exact form setup on your site.

Does it send my form data to an AI service?

No external AI service is part of the documented default workflow. The plugin uses local WordPress processing and database storage.

Where is the information stored?

In custom database tables on the WordPress site. Stored values can optionally be encrypted.

What is the difference between Minimal and Full mode?

Minimal mode records which fields were filled but never sends or caches typed values. Full mode can capture permitted values when the configured consent rules allow it.

Will visitors receive an abandoned-form email?

No. The available email notifications are administrator alerts for abandoned forms, new submissions, and repeated abandonments.

What happens when the plugin is deactivated or uninstalled?

Deactivation keeps data. Uninstall removes plugin database tables, options, and scheduled tasks.

Requirements

Requirements

Requires WordPress 5.8+ and PHP 7.4+. Tested up to WordPress 7.1. Free to download and use. No subscription or external account is required.

Free to download and use. No subscription or external account is required.

Download FreeBack to Home

Scroll to Top