• SPAM PROTECTION • SETUP GUIDE

Understanding Honeypot Protection and Spam Handling

By Rivio Support Team
1 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Rivio registration forms include an always-on honeypot and separate controls for reCAPTCHA, duplicate submissions, and blocked domains.

Before you begin

Choose a test form and review the current protection settings before changing them. Use dummy submissions to check allowed and blocked cases. Google reCAPTCHA keys are configured separately from enabling reCAPTCHA on each form.

Use preventive controls and record handling together

Every form includes a honeypot to catch simple bot behavior. reCAPTCHA adds a challenge when enabled; the domain blocklist refuses selected email domains; duplicate protection limits repeat applications. These controls address different patterns.

Your team can still inspect suspicious records and mark them Spam. Spam is not sent to integrations. Do not use real applicant data to demonstrate bot behavior or assume one spam flag will prevent all future unwanted traffic.

Example

Submit normally through the storefront without manipulating hidden fields. Separately inspect a controlled record marked Spam in the app.

Expected result

Normal visitors do not fill the honeypot and spam records are excluded from integration processing.

Limits and important behavior

  • The hidden honeypot is always on and is intended to catch simple bots.
  • No single protection verifies that every applicant is a legitimate business.
  • Do not remove hidden anti-spam elements through Custom CSS or HTML changes.

Troubleshooting and verification

If a legitimate applicant is blocked, compare the email domain, duplicate-submission policy, and reCAPTCHA result. Identify the protection causing the rejection before changing a shop-wide setting or asking the buyer to submit again.

Screenshots to add

Screenshot placeholder: Capture the app screen or test result described in “Understanding Honeypot Protection and Spam Handling”. Include the relevant saved settings and the example outcome so readers can connect the explanation to the interface. Use dummy applicant details and mask any secrets.

Related guides