Supported form sources and compatibility

See how Always Alert recognises common form plugins, page builders, custom mail, system messages, and unsupported paths.

Written By Kelsey

Last updated About 1 month ago

Always Alert works at the WordPress mail layer and can protect many form notifications without taking over the form plugin itself. Source attribution tells you where an observed message probably came from.

Recognised form sources

The current release can attribute common signals from:

  • Contact Form 7

  • Gravity Forms

  • Fluent Forms

  • WPForms

  • Ninja Forms

  • Formidable Forms

  • Bricks form submissions

  • Breakdance custom form submissions

It can also label detectable WooCommerce and WordPress System messages for exclusion and reporting.

Fluent Forms has a direct recipient/header integration. Other plugins and builders may be recognised through their headers, hooks, request context, or message patterns.

Form names in post-launch heartbeats

Where the source exposes a reliable name, Always Alert can include a form or page name in the metadata-only heartbeat.

The name may be unavailable for some plugins, custom code, or dynamic forms. Missing a human-readable form name does not necessarily mean the fallback copy failed.

Generic wp_mail

A message may appear as Generic wp_mail when:

  • it matched a notification-style subject but did not expose a known plugin signal;

  • custom code sent it through wp_mail;

  • a developer filter marked it as eligible;

  • its source could not be identified confidently.

Generic attribution describes source confidence. Review the status and reason before assuming the message was mishandled.

What Always Alert can see

Always Alert can inspect messages that pass through the WordPress wp_mail flow while the licensed plugin is active.

It cannot see a form notification that:

  • is sent directly by an external SaaS platform;

  • uses a custom transport that bypasses wp_mail;

  • is handled entirely in the browser or another server;

  • never reaches the mail stage because the form submission fails earlier.

Theme and mail-provider compatibility

Always Alert is transport-agnostic. It works before the existing mail transport, so it can operate alongside native WordPress mail, SMTP plugins, hosting mailers, and transactional providers that continue to use the WordPress mail pipeline.

Compatibility still needs site-level testing. Mail plugins, security plugins, custom hooks, and other code can change headers or message handling at different priorities.

Test a source

For each critical form:

  1. Use recognisable test data.

  2. Confirm the normal notification.

  3. Confirm the fallback copy.

  4. Check Always Alert → Logs for its source, status, and reason.

  5. If it is skipped in Form Notification Mode, review its subject and headers or temporarily compare Universal mode.

  6. Return to the least-broad coverage that reliably handles the required notifications.

Custom integrations

Developers can use WordPress filters to customise whether a message is eligible, excluded, attributed, or reported. Test custom rules against password resets, account messages, WooCommerce emails, and plugin-generated internal messages so broader coverage does not expose unrelated content.

Related articles