How to Set Up and Test Spam Protection in WPForms and Elementor Forms
Set up WPForms or Elementor form spam protection, compare unwanted entries, and test ordinary submissions without assuming the filter works perfectly.

To reduce spam in WPForms or Elementor Forms, start with the controls your form and plan support, then submit an ordinary test entry. A lower spam count is useful, but it does not tell you whether a real visitor’s entry was filtered too.
Start with the form plugin
WPForms includes an anti-spam token and an optional honeypot, managed in each form’s Settings → Spam Protection and Security section. WPForms can also use Akismet, while ActiveLayer documents support for both WPForms Lite and Pro. These are controls to configure and test, not a promise that every unwanted submission will disappear.
Elementor’s documented Akismet integration has a narrower plan boundary: it is available only on Elementor Pro plans that support form integrations. The documentation names “Elementor Advanced Pro Advanced plan and up.” Check your plan’s form-integration entitlement before planning around that control. You also need an Akismet account.
Configure protection in WPForms
Open the WPForms form you want to protect. Under Settings → Spam Protection and Security, enable its anti-spam token if it is off. If you want the optional honeypot, enable that there too. Do this for each relevant form rather than assuming a change to one form covers the others. These WPForms controls are managed in each form’s settings.
If you are using Akismet with WPForms, open that form and go to Settings → General, then turn on Enable Akismet anti-spam protection. The setting is in a different section from the token and honeypot controls, so check the form you intend to change.
If you choose ActiveLayer, go to ActiveLayer → Settings, paste your API key and click Verify key. ActiveLayer says WPForms protection is on by default once the key is connected. To leave a particular form out, use Configure next to WPForms, untick that form and save. After configuration, revisit that list: an excluded form should not be mistaken for a protected one.
Watch the service limit if you use ActiveLayer’s free plan. Its documentation says the plan includes 200 checks in total; after they run out, submissions go through unfiltered until you upgrade. A verified key and a previously successful test therefore do not establish that checks are still available later. Note which forms you excluded and account for remaining checks when you evaluate the results.
Configure Akismet for an eligible Elementor form
Before configuring the Elementor integration, make sure you have an Akismet account and an Elementor Pro plan that supports form integrations. Install the Akismet plugin, then enter your Akismet API key through Settings → Akismet Anti-spam in WordPress.
Elementor’s instructions require you to specify which form fields Akismet should scan: enter each intended field’s shortcode in the form’s Akismet Spam Protection section. A shortcode here identifies a field in that form; the documented example puts the email field’s shortcode in the Email field. Use the shortcodes from your own form rather than treating “email” as text you can paste unchanged.
Before testing, review those entries. If you intended Akismet to scan the email and message fields, confirm that you entered the corresponding shortcodes from that form. Having an Akismet account and key does not establish which fields the form will scan.
Test what visitors experience
First, record a baseline for each form you changed: over a defined period, count submissions you consider unwanted, using the same criteria when you check again. After enabling protection, compare a similar period for that same form. Keep excluded ActiveLayer forms separate from protected ones, and note if the free-plan checks run out during the comparison. Describe any difference as an observed change, not proof that protection caught everything or made no mistakes. Traffic and spam volume can change independently of your settings.
Next, send a clearly identifiable, ordinary test entry through each protected form as a visitor would. Confirm that the form accepts the entry and that it reaches the destination you normally use to review submissions. If you rely on an email notification, check that separately: submitting a form and receiving its email are different outcomes. Where your setup provides a way to inspect filtered entries, look for legitimate entries there too. One successful test is reassuring, but it cannot establish that every future legitimate entry will get through.
If a test fails, recheck the setting on that particular form before changing more controls. For Elementor Akismet, verify the intended field shortcodes. For ActiveLayer, confirm that the key verified, the form was not excluded and checks remain. Repeat the ordinary-entry test after making a change. The goal is fewer unwanted entries while real submissions still get through.
