Skip to main content
All CollectionsDivi 5Options Groups
Understanding the Spam Protection in Divi 5
Understanding the Spam Protection in Divi 5

Learn how to use the Spam Protection to reduce bot submissions, ensuring that your forms remain secure and reliable.

Updated today

Spam Protection Options in Divi 5 Contact Form Module

The Spam Protection options help prevent unwanted submissions by bots. For enhanced security and reliability, you can enable a basic math captcha or integrate third-party services like Google reCAPTCHA.

Divi 5 - Spam Protection Option Group

Where to Find the Spam Protection Options

  1. Open the Contact Form Module Settings: Click the gear icon or the module itself to access the settings.

  2. Navigate to the Content Tab: Locate and expand the Spam Protection option group.

Spam Protection Customization Settings

  1. Use A Spam Protection Service: Toggle this option to On to use a Google reCAPTCHA for bot prevention.

  2. Service Provider: Select a service provider from the dropdown menu. Currently, Google reCAPTCHA is supported.

  3. reCAPTCHA v3 Account: Add your Google reCAPTCHA account credentials:

  4. Minimum Score: Set a minimum score to determine interaction validity.

    • Scoring Range: Scores range from 0 to 1:

      • Higher scores (e.g., 1) are likely human interactions.

      • Lower scores (e.g., 0) indicate bots.

    • Default Value: 0.5.

  5. Use Basic Captcha: Toggle this option to On to enable a simple math-based captcha, such as "What is 2 + 3?" This adds a straightforward challenge for bots to fail.

Tips for Using Spam Protection

  • Choose the Right Protection: Use Google reCAPTCHA for advanced protection and Basic Captcha for simpler setups.

  • Set an Appropriate Minimum Score: Start with the default score of 0.5 and adjust based on your form's traffic patterns.

  • Test Before Launch: Verify that your captcha or reCAPTCHA integration works smoothly across devices and browsers.

  • Monitor Submissions: Regularly check submissions to ensure spam is effectively reduced without deterring legitimate users.

Did this answer your question?