Title: Formhawk Author: al5dy Published: August 31, 2026 Last modified: September 10, 2026 --- Search plugins ![](https://ps.w.org/formhawk/assets/banner-772x250.png?rev=3674948) ![](https://ps.w.org/formhawk/assets/icon-256x256.png?rev=3674948) # Formhawk By [al5dy](https://profiles.wordpress.org/al5dy/) [Download](https://downloads.wordpress.org/plugin/formhawk.0.6.0.zip) * [Details](https://vec.wordpress.org/plugins/formhawk/#description) * [Reviews](https://vec.wordpress.org/plugins/formhawk/#reviews) * [Installation](https://vec.wordpress.org/plugins/formhawk/#installation) * [Development](https://vec.wordpress.org/plugins/formhawk/#developers) [Support](https://wordpress.org/support/plugin/formhawk/) ## Description #### Stop guessing why your WordPress forms lose leads A form can look perfectly healthy while silently losing conversions, qualified leads and revenue. **Formhawk is a privacy-first form analytics and conversion optimization system built directly into WordPress.** It shows where visitors hesitate, where forms break, which fields create friction, which fields protect business value, and — when you explicitly enable optimization — which safe changes actually improve results. It is not just another submission counter. Formhawk combines **form analytics, field-level friction analysis, provider-confirmed conversion tracking, Field ROI, business outcome attribution, CRO experiments, automatic guardrails, rollback, and Minimum Viable Form optimization** in one local WordPress plugin. No external analytics account. No analytics cookies. No submitted field values sent to Formhawk. No need to replace your existing forms. #### Built for the forms you already use Formhawk automatically detects and analyzes: * **Contact Form 7** * **WPForms Lite and Pro** * **Elementor Pro Forms** * **Eligible standard HTML forms** For supported providers, Formhawk uses the provider’s server lifecycle to distinguish a real provider-confirmed success from a browser-side submit attempt. Generic HTML forms remain clearly labelled as browser-observed attempts when universal server confirmation is unavailable. That evidence distinction matters. A clicked submit button is not automatically a successful lead. #### See the complete conversion picture Formhawk turns every tracked form into an evidence-aware conversion dashboard with metrics such as: * Form views * Form starts and interaction rate * Browser submit attempts * Provider-confirmed successes where supported * Completion and conversion rate * Abandonment * Client-side validation friction * Provider validation failures * Provider and mail-operation failures * Average completion time and latency evidence * Last success and failure signals * Field reach and field-level friction * Last field interacted with before abandonment * Placement-level performance when the same form appears in different locations * Current versus comparable-period health signals Instead of asking **“Did anyone submit this form?”**, you can ask the questions that actually matter: **Where are people leaving? Which field is slowing them down? Is the form failing? Is a change improving real conversions or only producing more low-quality leads?** #### Field-level analytics: find the friction Formhawk analyzes the structure and interaction behavior of your forms without storing what visitors type into them. You can identify fields associated with: * High friction * Validation problems * Abandonment * Low reach * Conversion loss * Qualification value * Revenue or business-value impact This gives you a practical field-by-field view of where a form is helping the business— and where it may be costing conversions. #### Field ROI: make every field earn its place Most form analytics stop at conversion rate. Formhawk can go further. **Field ROI Business Value Intelligence** connects privacy-safe structural form evidence to downstream outcomes such as: * Qualified leads * Won leads * Lost leads * Spam * Revenue Formhawk can evaluate qualified or won leads per visitor, revenue per visitor, conversion impact, evidence quality and statistical confidence. This is important because the shortest form is not always the best form. A field may reduce raw submission volume but still be valuable if it improves lead quality or revenue. Another field may create friction without producing measurable business value. Formhawk’s Field Value Map and evidence-aware recommendations are designed to separate those cases instead of blindly telling you to remove every field that hurts conversion rate. #### From analytics to action with Autopilot CRO Finding a problem is useful. Testing whether the fix actually works is better. **Formhawk Autopilot CRO** can turn detected opportunities into controlled runtime experiments without permanently rewriting your Contact Form 7, WPForms or Elementor provider configuration. Depending on form structure and safety checks, the CRO engine can test presentation changes such as: * Safer field ordering * Progressive disclosure for eligible optional fields * Multi-step presentation for eligible forms * Submit button / CTA presentation * Label presentation * Placeholder presentation Autopilot operates in three real modes: * **Observe** — analyze and prepare a suggestion without sending experiment traffic. * **Approve** — prepare a safe experiment and wait for an administrator to start it. This is the default mode. * **Full Autopilot** — for eligible provider-confirmed forms, Formhawk can evaluate, promote, monitor and roll back changes inside its safety boundaries. The provider form remains the source of truth. Disable Formhawk and the original provider form remains intact. #### Decisions based on evidence, not guesswork Formhawk does not declare a winner because a graph moved up for a day. Its CRO decision layer uses controlled experiment evidence, minimum sample and runtime requirements, statistical decision rules, practical-effect thresholds and guardrails. Binary conversion experiments use a Beta-Binomial model; business-value decisions use outcome-aware evidence designed for real-world lead and revenue data. Automatic decisions are restricted to evidence that Formhawk considers trustworthy for the provider and experiment type. Browser-only signals remain advisory where server confirmation is unavailable. #### Automatic guardrails and rollback An optimization system should know how to stop itself. Formhawk monitors experiments and promoted baselines for signals including conversion degradation, provider failures, validation problems, JavaScript errors and business- value regression. If a promoted state later shows credible regression, Formhawk can restore the previous validated baseline. Invalid experiment data, schema drift or unsupported conditions fail safe rather than forcing an unproven mutation onto the form. That means optimization is not a one-way door. #### Minimum Viable Form: find the least friction your form actually needs **Minimum Viable Form** is Formhawk’s opt-in semantic optimization engine. Its goal is not to create the shortest possible form. Its goal is to find the ** minimum friction that preserves or improves measurable value per visitor**. The engine follows a controlled sequence: ``` analyze -> classify -> select -> experiment -> evaluate -> promote/reject -> monitor -> repeat ``` It uses Field ROI evidence, provider capability checks, field safety classification and dependency analysis to select one reversible semantic experiment at a time. For Contact Form 7 and WPForms, automatic removal experiments are limited to provider- verified **safe, optional and independent fields**. Unknown dependencies fail closed. Formhawk explicitly protects or forbids structural removal of fields associated with security, authentication, payment, CAPTCHA, files, signatures, legal/privacy consent and other high-risk semantics. Elementor Pro and generic HTML remain observe/ fail-closed for Minimum Form automation where the required dependency guarantees are not available. Winning states become immutable versioned baselines. Rejected changes stay rejected. A later regression can restore the previous validated state. #### Optimize for business value when the evidence exists Formhawk can choose the strongest available per-visitor objective from: * Revenue per visitor * Won leads per visitor * Qualified leads per visitor * Provider-confirmed conversion When mature business outcome data is not available, Formhawk explicitly switches to **Conversion Optimization Mode** instead of pretending it measured revenue or lead quality. No fake certainty. No made-up ROI. #### Business outcomes without storing the lead You can connect qualified, won, lost, spam and revenue outcomes to Formhawk using an opaque submission ID. Supported paths include: * The authenticated Formhawk Outcome REST API * WordPress Application Password authentication * The local `formhawk_record_outcome()` PHP API * Manual outcome recording in the WordPress admin The outcome layer is designed to connect business results back to structural form evidence without turning Formhawk into a CRM or storing the visitor’s submitted message, name, email address or phone number. #### Privacy-first by architecture Formhawk is designed to answer conversion questions without building a visitor surveillance profile. Formhawk does not intentionally store: * Submitted form values * Names * Email addresses * Phone numbers * Messages * IP addresses * Persistent visitor IDs * Persistent session IDs * User-agent history * Email recipients * Email subjects * Email bodies Formhawk creates **no analytics cookies** and does not use localStorage, sessionStorage or IndexedDB to create persistent visitor identifiers. Core analytics remain in your WordPress database. They are not silently sent to a Formhawk analytics cloud. Structural field names/labels and page paths may be stored so Formhawk can identify the form and its friction points; they describe the form structure, not the visitor’s response. #### Local WordPress intelligence, not another SaaS dashboard Formhawk runs inside WordPress and keeps its analytics data local to the site database. There is no external analytics account to create and no third-party tracking snippet required. Retention is configurable, cleanup is scheduled, and uninstall data removal remains under administrator control. The CRO runtime is designed to remain cache-compatible. Formhawk coordinates known runtime changes with WP Rocket and LiteSpeed and exposes an integration hook for other cache/CDN layers. #### Form health: know when something quietly stops working A form can still render while the business process behind it is unhealthy. Formhawk includes evidence-aware health and diagnostic signals for the frontend tracker, analytics storage, provider lifecycle, CRO storage/runtime, background evaluation jobs and the WordPress mail layer. Mail diagnostics are deliberately precise: a successful `wp_mail()` operation means WordPress/PHPMailer accepted the mail operation without reporting an immediate failure. It does **not** claim that the message reached the recipient’s inbox. #### Why Formhawk is different Formhawk is built around a simple idea: **Do not optimize a form for more clicks. Optimize it for better evidence and better business outcomes.** With one plugin you can move from: ``` Form Analytics -> Field Friction -> Field ROI -> Controlled CRO -> Minimum Viable Form -> Regression Monitoring ``` That is the difference between counting submissions and operating a conversion system. #### What Formhawk does not do Formhawk intentionally avoids claims the available evidence cannot support. * Generic HTML submit attempts are not relabelled as provider-confirmed conversions. * `wp_mail_succeeded` is not described as inbox delivery. * Field friction alone is not treated as proof that a field destroys business value. * Revenue optimization is not claimed when mature revenue evidence is unavailable. * Unsafe or ambiguous structural mutations fail closed. * The original provider form is not permanently rewritten by Autopilot or Minimum Form. This evidence discipline is part of the product, not a limitation hidden in fine print. ## Installation 1. Install **Formhawk** from Plugins > Add New, or upload the plugin directory. 2. Activate the plugin. 3. Open **Formhawk** in the WordPress admin menu. 4. Visit a frontend page containing Contact Form 7, WPForms, Elementor Pro Forms or an eligible standard HTML form. 5. Return to Formhawk. Detected forms begin appearing automatically as real traffic is collected. 6. Open a form to review conversion, abandonment, health, placement and field-friction analytics. 7. If you want business-value analysis, open **Formhawk > Field ROI** and connect qualified, won, lost, spam or revenue outcomes. 8. If you want automated optimization, explicitly enable **Autopilot CRO** or **Minimum Viable Form** for an eligible form and choose the operating mode you want. **No external analytics account, tracking snippet or analytics cookie is required.** ## FAQ ### What is Formhawk? Formhawk is a WordPress form analytics and conversion optimization plugin. It combines form funnels, abandonment and validation-friction analytics, provider-confirmed submission evidence, Field ROI, business outcome attribution, controlled CRO experiments, automatic guardrails/rollback and Minimum Viable Form optimization. ### Which form plugins are supported? Formhawk detects Contact Form 7, WPForms Lite and Pro, Elementor Pro Forms and eligible standard HTML forms. Contact Form 7, WPForms and Elementor Pro Forms can provide provider-confirmed success through supported server lifecycles. Generic HTML forms use browser-observed submit evidence where universal server confirmation is not available. ### Is Formhawk a form builder? No. Formhawk works with existing forms. Its job is to measure, diagnose and optimize them. Autopilot and Minimum Form apply reversible runtime changes inside verified safety boundaries instead of permanently rewriting the provider’s saved form definition. ### What can I measure with Formhawk? Depending on provider and available evidence, Formhawk can report views, starts, attempts, confirmed successes, completion/conversion, abandonment, validation friction, failures, timing, field reach, field friction, placement performance, form health and downstream qualified/won/revenue outcomes. ### What is the difference between a browser submit attempt and a confirmed conversion? A browser can attempt to submit a form even when provider validation or processing later fails. Formhawk keeps those concepts separate. Supported provider integrations can supply server-side lifecycle evidence for confirmed success; generic HTML attempts are not promoted to confirmed conversions without equivalent evidence. ### What is Field ROI? Field ROI connects privacy-safe field structure and experiment evidence to downstream business outcomes. It helps determine whether a field merely creates friction, improves qualification, protects revenue or needs more evidence before any conclusion is justified. ### Which business outcomes can Formhawk record? The canonical outcome model supports qualified, won, lost, spam and revenue/value evidence linked through an opaque Formhawk submission ID. ### How do I send qualified, won or revenue outcomes? Open **Formhawk > Field ROI > Outcome API** and create a dedicated key. Send the opaque submission ID, canonical status, integer value in minor currency units, ISO currency and an idempotency key to `/wp-json/formhawk/v1/outcomes`. WordPress Application Password authentication and the local `formhawk_record_outcome()` PHP API are also supported. ### What is Autopilot CRO? Autopilot CRO is Formhawk’s controlled optimization loop. It identifies an opportunity, creates a safe runtime variant, collects experiment evidence, evaluates guardrails and can promote or roll back a change according to the selected operating mode and evidence available for that provider. ### Does Autopilot permanently edit Contact Form 7, WPForms or Elementor forms? No. The provider definition remains the source of truth. Formhawk’s CRO changes are runtime layers. Disabling the optimization restores the original provider form behavior instead of leaving a permanently rewritten provider configuration behind. ### What can Autopilot test? Where Formhawk can prove the runtime structure is safe, experiments can include field ordering, progressive disclosure, multi-step presentation, submit button/CTA presentation, label presentation and placeholder presentation. Unsupported, ambiguous, conditional or protected structures fail closed rather than being guessed. ### What is Minimum Viable Form? Minimum Viable Form is an opt-in engine that tries to reduce unnecessary friction without sacrificing measurable conversion, lead quality or revenue. It selects one evidence-backed semantic candidate at a time, experiments, evaluates the result and builds immutable validated baselines from winners. ### Can Minimum Viable Form remove fields automatically? For Contact Form 7 and WPForms, removal experiments are limited to optional fields that provider/schema checks prove are safe and independent. Security, payment, authentication, CAPTCHA, upload, signature, legal/privacy consent and other forbidden or protected fields are not automatically removed. Elementor Pro and generic HTML do not receive autonomous field-removal behavior when the required dependency guarantees are unavailable. ### Can Formhawk optimize without revenue data? Yes. When mature business outcomes are unavailable, Formhawk can use provider-confirmed conversion as the objective and clearly labels the run **Conversion Optimization Mode**. It does not claim a revenue or business-value win it did not measure. ### What happens if an optimization makes results worse? Experiments have guardrails, and promoted baselines remain monitored. When Formhawk detects credible post-promotion regression within its decision policy, it can restore the previous validated baseline. Schema drift and invalid experiment integrity can also pause optimization and fail safe. ### Does Formhawk use AI to decide experiment winners? No. Experiment decisions are made by deterministic statistical and policy logic. Formhawk does not use an LLM to choose the winning variant. ### Does Formhawk store submitted values or visitor identities? No. The frontend tracker does not read or transmit visitor field values to Formhawk analytics. Formhawk does not intentionally store names, email addresses, phone numbers, messages, IP addresses, persistent visitor IDs, session IDs or user-agent history. ### Does Formhawk use cookies or browser storage? No. Formhawk creates no analytics cookies and does not use localStorage, sessionStorage or IndexedDB to create persistent visitor identifiers. Temporary attribution state is limited to the current page/form lifecycle and short-lived server-side replay- protection state uses hashed random assignment identifiers rather than a persistent visitor profile. ### Does Formhawk send analytics to an external Formhawk service? No. Core analytics remain in the site’s WordPress database and are not silently transmitted to a Formhawk analytics cloud. ### Does wp_mail_succeeded mean the email reached the inbox? No. It means WordPress accepted the mail operation without reporting an immediate failure. Formhawk deliberately does not describe that signal as proof of external inbox delivery. ### Can I exclude or rename a generic HTML form? Yes. Add `data-formhawk-ignore` to exclude a form. Use `data-formhawk-title` and optionally `data-formhawk-id` to give a generic form a stable, readable identity. ### How long is analytics retained? The administrator can choose 30, 90, 180 or 365 days. Cleanup is bounded and scheduled. Uninstall cleanup happens only when explicitly configured. ### Will Formhawk slow down every frontend page? The base tracker is designed for lightweight form analytics. CRO assets are conditionally used for placements with an active experiment or promoted runtime baseline rather than being imposed as a site-wide optimization layer on every page. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Formhawk” is open source software. The following people have contributed to this plugin. Contributors * [ al5dy ](https://profiles.wordpress.org/al5dy/) [Translate “Formhawk” into your language.](https://translate.wordpress.org/projects/wp-plugins/formhawk) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/formhawk/), check out the [SVN repository](https://plugins.svn.wordpress.org/formhawk/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/formhawk/) by [RSS](https://plugins.trac.wordpress.org/log/formhawk/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.6.0 * Added the opt-in Minimum Viable Form Engine with sequential, evidence-backed semantic field experiments. * Added reversible REMOVE_FIELD, MAKE_OPTIONAL and MAKE_REQUIRED mutation strategies with provider capability gates. * Added structural field safety classification and fail-closed provider dependency graphs. * Added immutable versioned form baselines, mutation genomes, schema-drift revalidation and original-form fallback. * Added business-objective selection for revenue, qualified leads, won leads and confirmed conversion. * Added robust revenue-per-visitor decisions with outcome maturity, coverage, expected- loss and practical-significance gates. * Added post-promotion business regression monitoring, automatic rollback and form- level optimization locks. * Added Minimum Form history, visual form map, before/after preview, safety diagnostics and accessible admin controls. * Hardened CRO integrity so one assignment records at most one binary conversion while independent provider submissions remain separately attributable. * Added schema v8 without changing existing analytics, outcomes, Field ROI results, Autopilot settings or provider form definitions. #### 0.5.2 * Replaced replayable CRO contexts with signed v2 contexts, random assignment IDs, issuance timestamps and short-lived hashed server lifecycle storage. * Atomically deduplicated browser events and separated server-issued assignments from browser views. * Restricted autonomous decisions to trusted provider evidence and added schema v7. #### 0.5.1 * Fixed repeated AJAX submissions being merged into one Field ROI submission. * Preserved retry idempotency while rotating submission markers after terminal provider responses. #### 0.5.0 * Added Field ROI Business Value Intelligence, privacy-safe outcome attribution and robust revenue inference. * Added qualified, won, lost, spam and revenue outcomes with immutable evidence history. * Added a strict authenticated Outcome REST API and schema v6. #### 0.4.0 * Added Formhawk Autopilot CRO, reversible presentation mutations and Bayesian binary decisions. * Added business-value objectives, guardrails, automatic promotion and rollback, and schema v5. #### 0.3.0 * Added hardened aggregate ingestion, provider registries, WPForms and Elementor Pro integrations. * Separated observed attempts from provider-confirmed submissions and added placement analytics. #### 0.1.1 * Initial public release of Formhawk. ## Meta * Version **0.6.0** * Last updated **1 day ago** * Active installations **Fewer than 10** * WordPress version ** 6.4 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/formhawk/) * Tags * [contact form 7](https://vec.wordpress.org/plugins/tags/contact-form-7/)[conversion optimization](https://vec.wordpress.org/plugins/tags/conversion-optimization/) [elementor](https://vec.wordpress.org/plugins/tags/elementor/)[form analytics](https://vec.wordpress.org/plugins/tags/form-analytics/) [WPForms](https://vec.wordpress.org/plugins/tags/wpforms/) * [Advanced View](https://vec.wordpress.org/plugins/formhawk/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/formhawk/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/formhawk/reviews/) ## Contributors * [ al5dy ](https://profiles.wordpress.org/al5dy/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/formhawk/)