SAP Customer Data Cloud Positions


Skip to end of metadata
Go to start of metadata


This section is a reference to Gigya's JavaScript Web SDK.

We highly recommend reading the  Using The Web SDK  guide. The guide includes a basic example and instructions for using Gigya's Web SDK methods.

Please see here for supported browsers.

When using Gigya's API's over HTTPS it is important that the script tag in the <head> of your pages reference the HTTPS version of the JS SDK, (note CDNS as opposed to CDN) e.g.,

<script type="text/javascript" src="https://cdns.<Data_Center>/js/gigya.js?apikey=YOUR-API-KEY-HERE"></script>

Finding your data center


onGigyaServiceReady is a variable that the Gigya WebSDK always checks for as soon as it completes loading. 

For Gigya methods to function properly, they can only be called after the Gigya WebSDK finishes loading completely. Attempting to call a method prior to this, will result in an error similar to the following:

Uncaught ReferenceError: gigya is not defined

To ensure that Gigya is always loaded prior to any method calls on your page, you can place all Gigya related functions inside a handler and then call that handler using the onGigyaServiceReady variable.

A code example follows:

function GigyaLoadFunctions() { 
        "callback":function(res) {
			if (res.errorCode === 0;) {
				window.userGigyaData = res;
var onGigyaServiceReady = function() {
<script type="text/javascript" src="" ></script>


Using the above example, after Gigya finishes loading, it will then call the onGigyaServiceReady function which will, in turn, call the GigyaLoadFunctions function.



If the Web SDK makes an API request that results in an UNVERIFIED_USER (403013) response, it will, internally, make another API request to accounts.verifyLogin (an internal method) and then repeat the original request.

This can happen, for instance, when a Site Admin publishes a new consent version and changes the minimum required version.


Gigya's Web SDK consists of the objects and methods listed below: