# reCAPTCHA Limitations - HubSpot Form Feedback

**URL:** <https://community.hubspot.com/t/recaptcha-limitations-hubspot-form-feedback/86129>\
**Category:** Lead Capture Tools\
**Tags:** forms\
**Created:** [July 25, 2023, 11:49pm UTC](https://community.hubspot.com/t/recaptcha-limitations-hubspot-form-feedback/86129 "2023-07-25T23:49:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![maxy345](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@maxy345](https://community.hubspot.com/u/maxy345)\
**Post date:** [July 25, 2023, 11:49pm UTC](https://community.hubspot.com/t/recaptcha-limitations-hubspot-form-feedback/86129/1 "2023-07-25T23:49:31Z")

</div>

**HubSpot Forms, Spam & Conversion Rates**  
We’ve been experiencing some issues with spam form submissions. Particularly from paid campaigns. We’ve enabled reCAPTCHA on our HubSpot forms to help prevent spam submissions on the website.  
There are a couple of things that could be worth updating in HubSpot so I thought I’d share some feedback here.

1. The reCAPTCHA puzzle is tedious and is definitely affecting form conversion rates. I also tested the form in incognito using a standard non-spammy Gmail account and the reCAPTCHA task appeared. It’s meant to only appear for suspicious submissions so I’m not 100% clear about when and why this fired.
2. Ideally, HubSpot needs to upgrade to reCAPTCHA v3. There are too many limitations with the puzzle form. Also, a simple ‘I’m not a robot’ checkbox would be much cleaner than the puzzle.
3. Honeypotting — would be cool to see a form settings option for this as well. I.e. Hidden option form fields with automation to flag as well
4. Finally, the CAPTCHA box is ugly. Not being able to hide this or edit the size/styling in CSS is frustrating… especially when you’ve built a form from scratch in Design Tools.

---

<div class="post-metadata">

**Author:** ![TomM2](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tomm2/32/70887_2.png) [@TomM2](https://community.hubspot.com/u/TomM2)\
**Post date:** [July 26, 2023, 9:45am UTC](https://community.hubspot.com/t/recaptcha-limitations-hubspot-form-feedback/86129/2 "2023-07-26T09:45:33Z")

</div>

Hey @maxy345 hope you’re keeping well!

It’s important to note reCAPTCHA is controlled entirely by google, and google being google they don’t share much, if anything about what triggers the reCAPTCHA puzzles or how they attempt detect bots. This is simply embedded by HubSpot into the form, they would have no control over how it actually works.

There are a few important things to note however.

1. The reCAPTCHA is a \*bot traffic detection\* tool, not a spam form submission tool. This means when it detects the web page traffic is coming from a bot, it will challenge it (via the puzzle). The form is designed to not allow a submission to go through without the reCAPTCHA resolving, but it’s not passing data to the reCAPTCHA to be verified. This means I could technically have the email “[Imastupidrobotlol@androids.com](mailto:Imastupidrobotlol@androids.com)” as my email and still pass reCAPTCHA and it has deemed me a human. HubSpot has some built in email verification tools but it’s not absolute, it’s very difficult to verify freemail provider email addresses as they all \*technically\* could be real emails.
2. Definitely agree, I know there was some conversation around the future of reCAPTCHA when the costs came in but I believe HubSpot went for the enterprise option since hCAPTCHA is a lot worse for puzzles. I’d definitely recomend giving [this feature request](https://community.hubspot.com/t5/HubSpot-Ideas/Upgrade-to-reCaptcha-v3/idi-p/389577) an upvote and posting your feedback there to the product team!
3. Not exactly a honeypot but there’s an interesting strategy that @danmoyle uses outlined in a great post from [him here](https://community.hubspot.com/t5/Lead-Capture-Tools/Protect-Against-Spam-Accounts/m-p/445578/highlight/true#M5969).
4. Again, this is really down to google. reCAPTCHA v2 and 3 don’t allow for customising the styling.

---

<div class="post-metadata">

**Author:** ![danmoyle](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/danmoyle/32/91166_2.png) [@danmoyle](https://community.hubspot.com/u/danmoyle)\
**Post date:** [July 26, 2023, 7:12pm UTC](https://community.hubspot.com/t/recaptcha-limitations-hubspot-form-feedback/86129/3 "2023-07-26T19:12:17Z")

</div>

Thanks for the mention @TomM2!

Great advice on the ideas upvote - adding mine to it. Thanks for bringing this up @maxy345.

---

<div class="post-metadata">

**Author:** ![RNpal](https://avatars.discourse-cdn.com/v4/letter/r/eada6e/32.png) [@RNpal](https://community.hubspot.com/u/RNpal)\
**Post date:** [September 25, 2023, 5:33pm UTC](https://community.hubspot.com/t/recaptcha-limitations-hubspot-form-feedback/86129/4 "2023-09-25T17:33:31Z")

</div>

@maxy345 I ran into the same issue and I came across this plugin [SilentShield – Captcha & Anti-Spam for WordPress (CF7, WPForms, Elementor, WooCommerce) – WordPress plugin | WordPress.org](https://wordpress.org/plugins/captcha-for-contact-form-7/) - this takes care of both recaptch v3 without impacting the flow of data to hubspot.
