SAP Customer Data Cloud Positions


Skip to end of metadata
Go to start of metadata


CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart), is one of the most popular methods of distinguishing between a human user vs. an automated attacker. Gigya enables adding a CAPTCHA challenge to login and registration screen, to protect your site from automated hacking attempts. This guide walks you through the steps of setting up a CAPTCHA app. Gigya supports Google CAPTCHA solutions and FunCaptcha. 

Setting Up the App 

Google reCAPTCHA

When using the Google solution, we support Invisible reCAPTCHA for Registration and Checkbox reCAPTCHA for Login, which is displayed unobtrusively at the bottom of the browser page when a registration screen is loaded, and is triggered only if the profile of the registration attempt is deemed suspicious by Google's risk analysis algorithms.

reCAPTCHA is not currently available for use with mobile SDKs.


You need to configure separate credentials for each of the reCAPTCHA types, Checkboz or Invisible. Per Google, you should not use the same credentials for both configurations.

  1. Sign in to your Google account and go to
  2. Give your reCAPTCHA configuration a label and select the type of reCAPTCHA you need: For registration flows, select Invisible reCAPTCHA badge and for login flows, select "I'm not a robot" Checkbox. Selecting one of the options should open a "Domains" box.
  3. Enter your domains on which the relevant Screen-Sets are hosted. 
  4. In the list of domains, also enter a line with, so that when previewing your registration screen in the UI Builder, Invisible reCAPTCHA will function correctly. 
  5. Accept the terms of service and click Register
  6. Leave the browser tab open, or copy both the reCAPTCHA site key and the reCAPTCHA secret key to be used in the next step. 


Google does not support the use of reCAPTCHA inside an iFrame. reCAPTCHA must only be used in a parent window.



To activate FunCaptcha, you should first send an enquiry to FunCaptch at After completing an onboarding process, FunCaptcha will provide you with a public key and a private one.


Site Settings

  1. Open the Site Settings menu in Gigya's Console
  2. Select the provider: Google or FunCaptcha.
  3. Enter all the relevant CAPTCHA credentials. Note that Google reCAPTCHA includes two separate sets of credentials (invisible reCAPTCHA for registration, and v.2 for login)
  4. Save your settings on the bottom right-hand corner. 



Using CAPTCHA in the Registration Flow

  1. Open the Policies page in Gigya's Console
  2. Under Additional Security Measures, check the Require CAPTCHA during registration option.

    You now have to include a CAPTCHA widget in every registration screen of your site (see the UI Builder section, below, for additional information). A CAPTCHA will be triggered only if the registration attempt is deemed suspicious by the CAPTCHA provider's risk analysis algorithms. If this is the case, users will need to "prove they are human".

    If the registration seems legitimate, the CAPTCHA challenge will not be triggered. 

If you have not yet configured the CAPTCHA site key and secret, a warning will appear: "Warning: Missing CAPTCHA credentials". To fix this, enter your credentials as described in the Site Settings section of this page.

Using CAPTCHA in the Login Flow

Enabling CAPTCHA for a login flow is achieved via Gigya's RBA (Risk Based Authentication). 

To create a rule to trigger RBA during login flows:

  1. Navigate to the RBA tab of the Gigya Console.
  2. Under Global Rules, click Add Rule. This will open up the Add Global Rule dialog.

    You can use one of the available Default rules or create a custom rule.

  3. Select the rule you want to enforce.
  4. After selecting a rule, click Next
  5. In the configuration editor, choose whether to accept the default values, or customize the settings. For more information on customizing RBA rules, see Risk Based Authentication. It is recommended to edit the default name of the rule to make it easier to recognize if you have multiple different rules configured.
  6. Click Apply.
  7. Finally, ensure that you press Save Setting in the bottom right-hand corner of the Gigya Console to save your RBA configuration.

UI Builder

When using reCAPTCHA during the Registration flow, you need to add the reCAPTCHA widget to every registration screen of your site. Assuming you are using the UI Builder for customizing your screens, that can be accomplished with the following steps: 

  1. In Gigya's Console, open the Screen-Sets page
  2. Click the name of the relevant RegistrationLogin screen-set collection to open it in the UI Builder. 
  3. Under Screens, select the Registration screen. 
  4. Find the CAPTCHA widget in the Widgets menu on the left-hand side, and drag it into the canvas. 

  5. With the CAPTCHA widget still selected, on the right hand side of the UI Builder, you can configure the widget settings. For Google's reCAPTCHA, these are the available settings: 
    • Badge: Select the position of the reCAPTCHA badge in the screen.  
    • Type: The type of challenge that will be presented to the user, whether image or audio. In any case, the user can choose to switch to the other type.
  6. You can preview the result by clicking Preview in the top right corner, and simulate a login process (when configuring Google reCAPTCHA, make sure you add to the list of domains, as noted above) . When using Google, the reCAPTCHA badge should in the preview canvas in the selected position. The CAPTCHA challenge will be triggered in preview mode according to the usual risk analysis calculation. 

    ReCAPTCHA badge in the bottom right corner in the UI Builder's preview mode

    FunCaptcha challenge in the UI Builder's preview mode


    If you did not add to the list of sites in the reCAPTCHA Google settings, the badge will display the following error in preview mode:

CAPTCHA in Multi-Site Settings

In a multi-site setting, CAPTCHA credentials need to be configured individually per site. 

The CAPTCHA policy is inherited by default from the parent sites. However, child sites may override this policy configuration. 



  • No labels