Skip to main content

Protect Public Forms with reCAPTCHA - Article

Configure the supported reCAPTCHA v3 connection for selected public forms and verify the intended registration, contact and Course On Demand experience.
Updated: 14 Nov 2026
4 min read

Summary

Public forms need to remain usable for legitimate visitors while reducing automated spam and abuse. The supported reCAPTCHA connection adds protection to selected form routes. Configure the correct site keys and domains, then verify the actual visitor journey rather than assuming that enabling one checkbox protects every form.

Use this article to:

  • Prepare the supported provider registration and platform keys
  • Choose which public form routes use protection
  • Verify legitimate submission and investigate configuration failures

Choose the forms that need protection

A public training offer can attract legitimate prospects and automated submissions at the same time. Select protection around the forms your organization actually exposes, such as account signup, anonymous contact or Course On Demand enquiries.

The integration supports reCAPTCHA v3. It is a provider-backed risk-control mechanism, not a training assessment or an eligibility decision about which Course a person may attend. Keep the normal form validation and business process intact.

Register the intended domains

Ask Eurekos to confirm configuration access. Open Settings → Third party integrations → reCAPTCHA and follow the provider registration link where needed.

In the provider setup, register the intended site with reCAPTCHA v3 and list the actual domains on which the forms will be used. The domain entry excludes the https:// or http:// prefix. Review custom domains and environment differences with the platform owner instead of assuming a test domain covers production.

Obtain the Site key and Site secret for that registration. They have different roles; keep the secret private and use the matching pair from the intended provider configuration.

Configure the platform forms

Enter Site key and Site secret in the Eurekos integration form. Select the intended form options, then Save.

OptionProtected routeWhat to verify
Enable on Sign up formAccount-registration formA legitimate new-user submission can follow the intended registration journey
Enable on Contact formAn anonymous visitor uses the Contact formAn anonymous visitor can submit a valid enquiry
Enable on Course On Demand formAn anonymous visitor uses the Course On Demand formA legitimate training enquiry reaches its normal follow-up process

These are separate choices. Enabling the Sign up form does not establish that Contact or Course On Demand is also protected. The anonymous-form behavior should not be generalized to every authenticated form or every page of the platform.

Test the visitor journey in context

Use the actual intended domain and an ordinary visitor session. Check that the provider protection is present and that a legitimate complete form can be submitted through the normal process. Confirm the resulting account or enquiry evidence separately from the visible provider indicator.

Coordinate the test with the owner of registration and notification settings. A successful form submission can still be followed by the platform’s normal approval, email or enrollment requirements. Protection does not replace those steps.

If a form stops working after configuration, identify whether the failure comes from a domain/key mismatch, provider loading or the form’s own validation. Avoid repeatedly changing unrelated registration rules to resolve a provider setup problem.

Verify the configuration

Scenario or checkExpected result or evidence
Provider registrationSupported v3 configuration and the correct intended domains
Matching keysSite key and private Site secret belong to that registration
Each enabled public formProtection is present and legitimate submission follows the normal workflow
An authenticated user contextProtection is tested on the specific enabled form and visitor state
A changed production/custom domainProvider registration and working submission are rechecked

Troubleshooting

ProblemWhat to check
A protected form fails after setupMatching v3 keys, registered domain and provider-loading evidence
One form is protected but another is notSeparate enable options for Sign up, Contact and Course On Demand
The test works only on the test domainRegister and verify the intended production/custom domain
A legitimate submission is not recordedSeparate provider validation from the form’s own required fields and downstream workflow
The secret appears in an instructional assetRemove the exposure and coordinate replacement through the credential owner

Third Party Integrations

FAQ