Skip to main content
formsieve Docs Support
All docs pages

Feedback loop

Your corrections make Formsieve better on your site. There is nothing extra to click: use the host plugin's normal spam controls.

Where to correct

  • Gravity Forms: the Spam and Not Spam actions in the entry list (single or bulk) or on the entry screen, or the Mark as spam / Not spam buttons in the entry's Formsieve panel.
  • Contact Form 7 with Flamingo: move a message between Inbox and Spam in Flamingo → Inbound Messages (row action, bulk action or the status box). This works only for messages that still have a Formsieve log row: a message older than the log retention period, stored before Formsieve was set up, or from a form Formsieve does not check teaches Formsieve nothing and fires no feedback action.
  • Formsieve → Log: Mark spam and Mark not spam on any logged submission (the only way when Flamingo is not installed).

What a correction does

  1. Labels the decision. The log row gets your label ("spam" or "ham"), the time and your user ID. The dashboard counts corrections, which is the most honest measure of how Formsieve does on your forms. A correction always labels the row of the original submission, also after a Re-check of the entry, so each submission counts once.
  2. Learns the sender. Formsieve keeps two learned lists per site:
    • Not spam adds the sender's e-mail address to the trusted list. Later submissions from that address are allowed without a check (allowlist:learned), so they never reach the model.
    • Spam adds the address to the blocked list. Later submissions from it are blocked locally (blocklist:learned), with no API call, while the Blocklists pre-filter is on. The blocklists run before the replay cache, so a blocked sender stays blocked even when the same text was allowed earlier. Formsieve learns individual addresses, never whole domains, so marking one sender at a free e-mail provider as spam does not affect anyone else there. The trusted list matches the address typed into the form, so only mark real correspondents "not spam" (see Pre-filters).
  3. Leaves the notification decision to you. Restoring an entry does not re-send notifications: Gravity Forms has Resend Notifications on the entry screen. Restoring a message does not re-send mail: Flamingo lets you read the message and reply to it.

Privacy of the learned lists

The lists hold keyed hashes (HMAC-SHA256 with your site's secret salt) of e-mail addresses, never the addresses themselves, up to 5,000 per list. A personal-data erasure request for an address removes it from both lists (Privacy kit). If the salts in wp-config.php change, earlier entries stop matching (Troubleshooting).

For developers

Every correction fires fsv_gf_feedback with the entry ID, the label and the log row (or null when the entry has none), so you can forward corrections to your own analytics (Developer hooks and WP-CLI). A correction fires fsv_cf7_feedback with the Flamingo message ID (or 0 for a log row without a message), the label and the log row, so you can forward corrections to your own analytics (Developer hooks and WP-CLI).