Google reCAPTCHA is a program that judges whether a user is a human or a robot. You have probably seen some variation of reCAPTCHA.
CAPTCHAs are used by many websites to prevent abuse from 'bots', or automated programs usually written to generate spam. reCAPTCHA makes it hard for bots to submit your forms.
Formidable Forms offers one-click reCAPTCHA (v2), invisible reCAPTCHA, and score-based reCAPTCHA v3. When setting up reCAPTCHA for your site's forms, you will choose one of these types.
From Idea to Reality in Minutes. Build Powerful Forms, Dashboards, Apps and More.
Formidable Forms makes advanced site building simple. Launch forms, directories, dashboards, and custom WordPress apps faster than ever before.
The simplest way to create a reCAPTCHA key is through the reCAPTCHA admin console. If you prefer to use the Google Cloud Console, follow the instructions for the Google Cloud site. To set up reCAPTCHA on your website, follow these steps.
Register the site where you want to use reCAPTCHA. To identify your site, add a label, such as a nickname or the website's URL.
Set the reCAPTCHA type to either Score based (v3) or Challenge (v2). Only one type of reCAPTCHA is allowed per site. After you select Challenge (v2), Google shows its v2 options, such as 'I'm not a robot' Checkbox and Invisible reCAPTCHA badge.
Score based (v3): Uses reCAPTCHA v3 to verify requests with a score. Learn more about the reCAPTCHA threshold.
Challenge (v2) - 'I'm not a robot' Checkbox: Uses reCAPTCHA v2 to validate requests with the "I'm not a robot" checkbox.
Challenge (v2) - Invisible reCAPTCHA badge: Uses reCAPTCHA v2 to validate requests in the background with the Invisible reCAPTCHA badge.
Add the generated reCAPTCHA keys into your Formidable settings to proceed with the integration.
Go to Formidable → Global Settings and click the Captcha/Spam tab.
Under Select captcha type, click reCAPTCHA.
In the reCAPTCHA settings section, paste your reCAPTCHA site key into the Site key box and your secret key into the Secret key box. If the section is collapsed because keys are already saved, click reCAPTCHA settings to open it.
Select the reCAPTCHA type. It must match the type that you selected when you generated the keys.
Checkbox (V2): for Challenge (v2) - 'I'm not a robot' Checkbox keys.
Invisible: for Challenge (v2) - Invisible reCAPTCHA badge keys.
v3: for Score based (v3) keys.
Set the default language for your reCAPTCHA in the reCAPTCHA language dropdown. It's set to Browser Default by default, so the reCAPTCHA appears in each visitor's browser language.
If you use multiple reCAPTCHA fields on one page, keep the Allow multiple reCAPTCHAs to be used on a single page option checked. It's checked by default.
Click Update to save your changes.
Add the Captcha field to each form you want to protect. The field shows the reCAPTCHA you set up. Follow the guide on adding CAPTCHA to WordPress forms. If the form has multiple pages, place the reCAPTCHA on the last page.
The reCAPTCHA settings section stays open until both keys are saved. After that, it's collapsed when you open the page. Click reCAPTCHA settings to view or change your keys.
By default, a submission that fails the reCAPTCHA is rejected with an error message. To save these submissions as spam entries you can review instead, open Customize how spam submissions are handled on the same page. Then set CAPTCHA errors to Save as a spam entry. Learn more about how to add spam protection.
You can also protect your forms with Google reCAPTCHA v3. Instead of using the "I'm not a robot" checkbox or the invisible reCAPTCHA badge, reCAPTCHA v3 verifies requests with a score.
When you set the reCAPTCHA type to v3, a reCAPTCHA threshold field appears. Use it to set the lowest score a submission needs to pass.
Note: Google has implemented updates that significantly increase the difficulty of achieving a threshold score of 1 when submitting entries. This often results in the error message The CAPTCHA was not entered correctly. Adjusting the threshold to a lower score can help resolve this problem. Learn more about interpreting the score for reCAPTCHA v3.
A score of 0.5 is the current default value. A score of 0 is likely to be a bot, and a score of 1 is likely not a bot.
Setting a higher threshold will block more spam, but it may also block more real people. Setting a lower threshold will allow more bots and have fewer false positives. It will also stop fewer real users.
The score value for each entry will be displayed in the entry details.
If your form includes a reCAPTCHA and you want to turn it off, then delete the Captcha field from the form builder page. Delete the Captcha field on any form that includes a reCAPTCHA that you want to disable. You can also visit the Formidable → Global Settings → Captcha/Spam page and remove the reCAPTCHA keys.
If you are using Invisible reCAPTCHA and Google flags you as suspicious, it may display an image challenge after the submit button is clicked. This most likely happens when you submit your form multiple times from the same IP address. This is expected behavior for Invisible reCAPTCHA to ensure you are a human, and not a robot.
When the form is submitted, you may see the message "The CAPTCHA was not entered correctly".
Your site keys may not be correct. First, reenter the reCAPTCHA site keys and make sure there are no tabs or spaces in them.
If your site uses SSL on some pages but not others, you may be getting a cross-site scripting error blocking the script. Try forcing the form pages to use SSL.
If you have another plugin loading a reCAPTCHA on the same page, they are likely conflicting. Disable other reCAPTCHA plugins.
This message means Google reported a problem with your reCAPTCHA settings rather than with the visitor's answer, such as a missing or invalid secret key. Reenter the reCAPTCHA site key and secret key, and make sure both keys come from the same site in your reCAPTCHA admin console.
This error can appear when another WordPress plugin loads the reCAPTCHA in a different way and includes the script on every page. We've specifically seen this with the 'Pie Register' plugin. Learn how to find a conflict in WordPress to prevent the reCAPTCHA from failing.
If you're working on a local site at localhost, the reCAPTCHA may show the message "Localhost is not in the list of supported domains for this site key." Google doesn't support localhost domains by default. To use reCAPTCHA on your local site, add localhost to the domains for your site key in the reCAPTCHA admin console. Google recommends a separate site key for development.
When a page with a reCAPTCHA is loaded, you may see the error "Cannot contact reCAPTCHA. Check your connection and try again." One reason we have seen for this error is that the reCAPTCHA key is set to v2 but your forms are using invisible reCAPTCHA. Learn how to switch your keys to Invisible reCAPTCHA.
The reCAPTCHA relies on JavaScript to appear and validate. If nothing appears, this is a common sign of a JavaScript error on the page. You may also have another reCAPTCHA plugin installed that isn't playing nicely, like Google Captcha (reCAPTCHA) by BestWebSoft.
We have seen the reCAPTCHA fail in a certain browser. The cases we have seen ended up not being a browser issue, but related to page caching for logged out users. If the reCAPTCHA is working for you in one browser and not another, start by disabling any caching on your site.
If your reCAPTCHA shows the error ERROR for site owner: Invalid domain for site key, your site key is no longer valid.
Also, your website URL must match exactly what is included in the site key settings. Subdomains don't need to be added separately. Changes to the domains list may take up to 30 minutes to take effect.
If your reCAPTCHA shows the ERROR for site owner: Invalid key type message, you are using an incorrect reCAPTCHA key type. For example, v3 keys are not compatible with v2 reCAPTCHA, and v2 keys are not compatible with Invisible reCAPTCHA. Key types are not interchangeable.
Make sure that your generated key type matches the reCAPTCHA type you have selected in Formidable → Global Settings → Captcha/Spam. If you cannot resolve your issue, feel free to open a help desk ticket for further assistance.
To comply with the Google terms, include the reCAPTCHA badge on the page. To hide this, you can add the custom CSS below on your Formidable → Global Settings → Custom CSS page. Learn more about the Custom CSS settings.
When the login form is submitted, you may see this error message. If you have another reCAPTCHA plugin, such as Simple Google reCAPTCHA or reCAPTCHA Lite, they are likely conflicting.
This message appears when a form is submitted without a reCAPTCHA response. If the "I'm not a robot" checkbox is visible, check it and submit the form again. If no reCAPTCHA appears on the form, there is a JavaScript error on your page, or your theme is missing the wp_footer hook.
This article may contain affiliate links. Once in a while, we earn commissions from those links. But we only recommend products we like, with or without commissions.
In this article
Get More Done In Less Time With Better
WordPress Forms
Upgrade your
workflow with advanced WordPress forms and integrated Views.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
This website uses cookies
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
90 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
90 days
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Easy Digital Downloads is a complete eCommerce solution for WordPress.
Name
Description
Duration
edd_items_in_cart
Stores information about the cart.
Session
edd_session_
Stores information about the current user session.
Session
Formidable Forms is used to manage forms on this website.
Name
Description
Duration
frm_form_
Saves the ID of the form and the time the entry was submitted.
2 hours
These cookies are used for managing login functionality on this website.
Name
Description
Duration
wordpress_logged_in
Used to store logged-in users.
Persistent
wordpress_sec
Used to track the user across multiple sessions.
15 days
wordpress_test_cookie
Used to determine if cookies are enabled.
Session
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a web analytics service offered by Google that tracks and reports website traffic.
Used to determine if the user is in a new session/visit.
Session
__utmt
Used to throttle request rate.
10 minutes
__utmv
Used to store visitor-level custom variable data.
2 years
__utmz
Stores the traffic source or campaign that explains how the user reached your site.
6 months
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
fcookie
Used for bot detection.
7 days
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
ccookie
To remember if a user received a captcha challenge.
20 minutes
lissc
Pending
1 year
ABSELB
This is Load Balancer Cookie for affiliate marketing
2 years
spectroscopyId
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
session
brwsr
This cookie is used to Affiliate Marketing Cookie for LinkedIn
2 years
UserMatchHistory
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
session
lihc_auth_
Used by LinkedIn HelpCenter Live Chat to store language and chat start timestamp. Example names of this cookie include lihc_auth_en, lihc_auth_es, depending on language preference.
Session
lang
Used to remember a user's language setting
session
li_a
Used to authenticate enterprise users on Sales Navigator and Recruiter
30 days
li_gc
Used to store guest consent to the use of cookies for non-essential purposes
2 years
li_ep_auth_context
User to authenticate LinkedIn enterprise customers
30 days
li_rm
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device
1 year
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
lms_ads
This cookie is used to identify LinkedIn Members off LinkedIn for advertising
30 days
trkCode
This cookie is used by LinkedIn to support the functionality of adding a panel invite labeled 'Follow Us'
1 year
_guid
This cookie is used to identify a LinkedIn Member for advertising through Google Ads
90 days
trkInfo
This cookie is used by LinkedIn to support the functionality of adding a panel invite labeled 'Follow Us'
1 year
BizographicsOptOut
This cookie is used to determine opt-out status for non-members
10 years
li_oatml
Collects information about how visitors use our site.
30 days
IRLD
This cookie is used for Affiliate Marketing Cookie for LinkedIn
2 years
liap
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
90 days
l_page
This cookie is used for measuring conversion metrics on LinkedIn
6 months
pushPermInfo
Used across multiple LinkedIn services to determine cool off for push notification prompts
365 days
pushPermState
Used across multiple LinkedIn services to determine the user's push notification permission preference
30 days
ln_or
Used to determine if Oribi analytics can be carried out on a specific domain
1 day
chp_token
Used to denote whether the user has gone through two factor authentication or solved a Captcha.
Session
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
sdsc
This cookie is used for signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission
Session
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_mc
This cookie is used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side
6 months
PLAY_FLASH
Used by some LinkedIn services to facilitate the display of messages on page transitions . Users include notifying a user when a form is successfully submitted or fails , and to provide other similar notifications.
Session
li_referer
Used to detect bots. Cookie remembers the referring website before redirecting the user to captcha for authorization
15 minutes
f_token
Used to detect bots for anti-scraping
3 minutes
li_apfcdc
Used for triggering the abuse prevention features on member device.
10 hours
li_odapfcc
Used to control the number of abuse prevention features collected from member device.
2 Years
ac_L
Counts the number of times the account center banner, which is displayed to inform users with an incomplete profile how to complete their profile, was closed by a user to determine display logic
180 days
ac_LD
Contains the date when the account center was displayed to a user to determine display logic
180 days
recent_history_status
Used to determine whether a user enabled or disabled the Guest Recent History Setting
10 years
all_u_b
To know if a user has opted in to viewing LinkedIn on an unsupported browser
21 days
uh
Used to set the user preference for the mobile web platform via a user's settings
Session
abiRedirect
Enables import of address book during onboarding flow for users who choose to import their address book
Session
wwepo
Used to ensure that useres who choose to sign up using phone only have that setting and preference respected
90 days
li_cu
Used to map a user to a captcha challenge page
15 minutes
li_ec
Used to store unbound enterprise users' cookie consent
6 months
denial-client-ip
Stores user IP address for anti-scraping and DOS prevention
5 seconds
li_gpc
Used to remember a user's preferences on LinkedIn's Global Privacy Control
1 hour
denial-reason-code
Used for anti-scraping and DOS prevention
5 seconds
li_gp
Stores privacy preferences for guests to LinkedIn
1 year
rtc
Used as part of anti-abuse processes on LinkedIn
120 seconds
redirectFromM2MInviteSent
Used to notify and provide the appropriate profile display logic when the user sends an invitation to connect on LinkedIn from a LinkedIn member via email.
Session
queryString
This cookie is used to persist marketing tracking parameters
15 days
cookie.policy.banner.eu
Used to display cookie banner in LinkedIn Lite
365 days
cookie.policy.banner.nl
Used to display cookie banner in LinkedIn Lite on the Netherlands site.
365 days
appName
Used to identify the source as the LinkedIn Lite app to send the right service worker to the app
Session
appLang
Used to set the right language on the LinkedIn Lite app
Session
lls-integration
Validates whitelisted partners for content integrations
30 days
feed-sort
Used to remember a member's preference how the feed should be sorted
1 day
integration_type
Used to determine which integration traffic is coming from to render the profile namecard experience
30 days
li_theme_set
Remembers which users have updated their display / theme preferences
6 months
PLAY_LANG
Used by some LinkedIn services to remember a user's language preference
Session
lms_analytics
Used to identify LinkedIn Members off LinkedIn for analytics
30 days
PLAY_SESSION
Used by some LinkedIn services to store session information
Session
li_fat_id
Member indirect identifier for Members for conversion tracking, retargeting, analytics
30 days
redirectFromM2MInviteAccept
Determines the appropriate profile display logic when a user accepts an invitation to connect on LinkedIn from a LinkedIn member via email.
Session
li_giant
Indirect indentifier for groups of LinkedIn Members used for conversion tracking
7 days
sharebox-suggestion
Displays a banner that provides help text to first time users of the Elevate share box
Session
li_cc
Used to ensure a user's phone number is inputted in China
1 week
lss_bundle_viewer
Stores consent when a user agrees to view a Smartlinks link
1 month
interstitial_page_reg_oauth_url
Stores the referring page to ensure the Authentication screen displays correctly
1 day
df_ts
Device fingerprinting sampling for performance optimization
1 day
lil-lang
Stores user's selected language setting for LinkedIn Learning
Session
li_alerts
Used to track impressions of LinkedIn alerts, such as the Cookie Banner and to implement cool off periods for display of alerts
1 year
li_theme
Remembers a user's display preference/theme setting
6 months
li_feed_xray
Used to show new items in developer option 'Feed X-ray'
Session
VID
ID associated with a visitor to a LinkedIn microsite which is used to determine conversions for lead gen purposes
1 year
recent_history
Used to remember URLs visited by the guest to show the pages back where they left off
90 days
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Name
Description
Duration
affwp_campaign
Stores the affiliate campaign name for tracking purposes.
30 days
affwp_ref
Stores the referring affiliate ID for commission attribution.
30 days
affwp_ref_visit_id
Stores the visit ID linked to the referring affiliate.
30 days
LinkedIn Insight is a web analytics service that tracks and reports website traffic.