SAP Customer Data Cloud Positions

SAP Commerce Cloud

Skip to end of metadata
Go to start of metadata

Commerce Cloud Overview

Create an immersive shopping experience with Gigya’s extension for SAP Commerce Cloud (previously Hybris). Gigya’s social technology combines the core elements that power e-commerce - product awareness and discovery coupled with customer acquisition and loyalty - into a comprehensive set of features and services that are designed to keep customers engaged as well as increase shopping cart conversions while on SAP Commerce Cloud websites.

The Gigya extension provides two main Customer Identity Management packages:

  • Registration-as-a-Service (RaaS): An end-to-end user management system package. This platform offers a comprehensive cloud-based user registration service that supports login by social networks while allowing sites to maintain a single user database that combines social and traditional site authentication. For additional information and advanced implementation options see Customer Identity.

  • Social Login: The Gigya extension can be used as an external authentication system, allowing users to sign up to your site using their social networks. Users can register and login to your site with their social network identities, which the site will manage as conventional Hybris user accounts.

The extension supports SAP Commerce Cloud multi-site configurations. In addition, the Gigya extension provides a generic Gigya plugin that can be used to embed any of Gigya's social plugins within your Commerce Cloud websites, and a purchase synchronization feature that enables you to track user purchase activity using Gigya's Customer Insights analytics tool.


Versions and Compatibility

Latest Versions

For support of Commerce Cloud versions 1811 and above, use the native connector that is built-in to Commerce Cloud, for additional information see:
For an instructional video about this integration, click here.


Legacy Versions

From version 6.2 through (and including) 1808 (6.8), this documentation will show you how to install and maintain the GConnector for Commerce Cloud.



 Everything in this document below this point only pertains to supported versions prior to 1811.

VersionConnector TypeComments
6.2 through 1811Legacy GConnectorUse the GConnector found here.
Version 1811 and aboveCommerce ConnectorUse the connector built-in to Commerce Cloud.

For migrating from the Legacy GConnector (< 1811)to the new Built-In connector, see Migrating from Legacy GConnector To Built In Connector.


Instructional Video

If you have an SAP logon, you can watch instructional videos about this integration here


Note that after installing the installation, your point of reference for users should be "Gigya User", and not the regular "User" available in SAP Commerce Cloud: 

All features and user interfaces are fully configurable, require little time to install and can be controlled from the Administration Panel.

Note that user data is updated periodically by a cron job. See below for more information. 

Please note that support for Gigya Social Login as a separate plugin will not be available in future versions of this extension, starting with SAP Commerce Cloud 6.0. Social login will still be available as a feature of RaaS - Registration-as-a-Service.

Installation and Implementation


Before installing the Gigya Extension for SAP Commerce Cloud, make sure that:

  • The SAP Commerce Cloud platform is installed. 

    Unable to render {include} The included page could not be found.
     How to install Hybris

    After unziping the archive go to


    and source the setantenv.(bat|sh), depending on the platform.

    You will now be able to execute ant tasks.

    You should start with

    ant clean

    This will ask for the purpose of the installation. Choose develop if not on a production server.
    For additional information on the availability of tasks you can execute:

    ant -p

    Ant should always be executed under the bin/platform directory.
    To provide some basic features to your Hybris, you can use the installer.
    It is located under:


    and is named (depending upon your platform) either:


    - installer.bat

    and can be run from the directory using:

    ./ -r b2c_acc

    This will install one storefront and several cockpits.
    Go to bin/platform again and execute:

    ant clean all initialize

    Afterwards, you can go back to {hybrisDir}/config and open the localextensions.xml file.
    You will see that there are now more extensions added. You can add the GConnector addons to the bottom in the same manner as the other extensions.
    Go ahead and create a custom folder in:


    and place the Gigya GConnector extensions there.

    From this point the GConnector installation guide, below, should help you to complete the installation.
    You need to execute the addoninstall command for yacceleratorstorefront as your storefront.
    This will add the extensions there.
    After that run

    ant clean all updatesystem

    Then, finally, to start the server, run:


    Unable to render {include} The included page could not be found.

  • The following custom SAP Commerce Cloud extensions are installed: commercefacades, yacceleratorstorefront.
  • You have your Gigya API key.
  • You have created a User Key and User Secret.

    The Extension will use these credentials to access your data in the Gigya database. Creating a user key and user secret specifically for this extension is more secure than using your Partner Secret.

1. Download and Install the Extension

To install the extension:

  1. Download the latest extension here: 
    Gigya Developer Downloads

  2. Copy the gigya-addon folder to ${HYBRIS_BIN_DIR}\custom folder.

    1. SAP Commerce Cloud 6.5 and above (not including 1811 or later).
      1. Add “gigyacommon”, “gigyalogin” and “gigyaconsent” to localextensions.xml
        Run the following commands, replacing  yourstorefront  with your storefront name:

        ant all
        ant addoninstall -Daddonnames="gigyacommon" -DaddonStorefront.yacceleratorstorefront="yourstorefront"
        ant addoninstall -Daddonnames="gigyalogin" -DaddonStorefront.yacceleratorstorefront="yourstorefront"
        ant addoninstall -Daddonnames="gigyaconsent" -DaddonStorefront.yacceleratorstorefront="yourstorefront"


    2. SAP Commerce Cloud 6.2 - 6.4

      1. Add "gigyacommon" and "gigyalogin" to localextensions.xml.
        Run the following commands, replacing  yourstorefront  with your storefront name:

        ant all
        ant addoninstall -Daddonnames="gigyalogin" -DaddonStorefront.yacceleratorstorefront="yourstorefront"
        ant addoninstall -Daddonnames="gigyacommon" -DaddonStorefront.yacceleratorstorefront="yourstorefront"

        Run the following commands, replacing  yourstorefront  with your storefront name:


2. Configure Basic Settings

Log into the SAP Commerce Cloud Back Office. In the left sidebar, under Administrator, you should now see a Gigya folder.

If you are setting up your Gigya extension for the first time, right-click gigyaConfig in the Gigya Configuration in the Back Office, and click Create. For subsequent edits to the configuration, in the Back Office, open Gigya Configuration and select the relevant configuration. 


In the Back Office, a configuration wizard opens. 


Fill in the following fields (some are optional):

gigyaApiKeyThe site's Gigya API key.

The Gigya data center used by your implementation.

Where <Data_Center> is:

  • for the US data center (default)
  • for the European data center
  • for the Australian data center
  • for the Russian data center
  • for the Chinese data center

gigyaLoginBehavior (Deprecated) In this drop-down, you may choose between "loginExistingUser" or "Always login". The default is "loginExistingUser". See Adding Connections When the User is Not Logged In for information about this option.
gigyaSiteSecret *The Partner Secret Key (not required if you have a User Key + User Secret).
gigyaUserKey *Your application key.
gigyaUserSecret *Your application secret.

* You must enter EITHER gigyaSiteSecret OR gigyaUserKey + gigyaUserSecret.

StorefrontClick to locate and select the SAP Commerce Cloud storefront connected to this Gigya congifuration.
modeIn this drop-down, choose "social" if you want to use Gigya for social login or "raas" if you have acquired and plan to use the full RaaS service.
providersThe social providers you wish to use. The default is "*" for all providers. To limit the service to specific providers, enter them in a comma-delimited list (e.g. "facebook,twitter").
siteIn this box, click the Search button to display a list of sites. Choose the site you want to connect to the extension.

Finally, click Create to save your settings.

User data between Gigya and Hybris is synced based on Gigya's UID. For more information, see UID-Based Sync.

3. Configure Your Own Encryption (OPTIONAL)

By default, the extension includes encryption for the application key and secret. No configuration is required to set up encryption. 

If you wish to configure your own encryption, you may do so by adding code to the file as follows.

  • Use custom key
  • Use custom key and signature
  • Use custom key, signature and encryption provider


 Customized encryption should only be performed by admins with a good knowledge of SAP Commerce Cloud customizations.

In the file, add lines according to the following example, with the encryption provider you are using. In this example, the provider is Bouncy Castle: 



When loading a SAP Commerce Cloud instance, the public key will be generated inside the symmetric.key file.

You can specify the key directly inside the file. For more information, see the documentation.

4. Set Up Social Login (OPTIONAL)

To use the extension in Social Login mode, you need to create a Social Login Component to use in your website.

The Gigya Social Login component can be inserted in any secure (HTTPS) page in your website, where it will display as social network buttons (see the setup section below for customization options):


To set up Social Login:

  1. Open the SAP Commerce Cloud Management Console.
  2. In the left sidebar, under Administrator, choose WCMS.
  3. Right-click Component and choose Create > GigyaSocialLoginComponent.

    Click to enlarge screenshot

  4. In the component, go to the Administration tab and fill out a Name and ID (e.g. "showLoginUI") and the Catalog Version.
  5. Scroll down to the Unbound section to configure Gigya parameters, such as buttonsStyle and containerID. You will find information about these parameters in the documentation for the Gigya JS API method socialize.showLoginUI.
  6. Optionally, you may use the advancedConfig setting to configure any other parameter that socialize.showLoginUI offers. Enter the parameters in JSON object format, for example:

    {"redirectURL": "", "showTooltips": "false"}
  7. Click Create.

Now you can use the SAP Commerce Cloud CMS Cockpit to insert the Gigya Social Login component into a web page.

5a. Set up the General Screen-Set Component (OPTIONAL)

By creating a Gigya General Screen-Set Component in your SAP Commerce Cloud single storefront website, you link it to one of the Gigya’s RaaS screen-sets, such as Login, Registration, Profile Update, etc.

If you are using SAP Commerce Cloud in an SSO scenario, skip this section and proceed with Step 5b. Set up the Register/Login Component (OPTIONAL), below.


  • Open the Backoffice.
  • In the left sidebar choose Gigya Node.
  • Left-click General Screen-Set Component and on the front page, under Search bar, left-click on the plus (+) button.


In the Step 1 (General) section:

  • Choose the ID (e.g., loginID) to be a unique value; this field is mandatory.
  • Choose the Name (e.g., LoginButton).
  • Choose the Link Text that the component will display to the user (e.g., Login). When the user clicks this link, the chosen screen-set will appear.

  • You can change the selections for Show anonymous and Show logged in if you would like to hide the component from anonymous or from already logged-in users. By default, the component is visible to everyone.
  • Click NEXT.

In Step 2 (Screens) section:

  • Choose the Screen-Set that will be invoked by this component (e.g., Default-RegistrationLogin). For additional information, see Screen-Sets.
  • Choose the Screen-Set that will used when the user is on a mobile device; this is usually the same name as above, unless you created a screen-set specifically for mobile devices.
  • Choose the Start screen - this is the name of the actual screen within the screen-set that will be displayed from within the aforementioned screen-set.
  • Choose whether the provided data through the screen set will be treated like profile update (user is already logged in and adding new, or updating existing, information). If the value is ‘False’ the data won’t be synchronized to the database.
  • Click NEXT/DONE.

In Step 3 (Advanced) section (optional):

  • Click DONE.


5b. Set up the Register/Login Screen-Set Component (OPTIONAL)

This component is intended specifically for login, registration, and logout process.

The purpose of this component is that when you are in SSO group, in order to guarantee the session synchronization between all sites, you must use the Register/Login Screen-Set Component instead of the General Screen-Set Component. The main difference between both components is that the Register/Login Component contains a link through which a logout process is triggered. You should always use the Register/Login Component for Login and Registration and the General Screen-set Component only for user update flows (i.e., Edit Profile or Lite Registration).

  • Open the Backoffice.
  • In the left sidebar choose Gigya Node.
  • Left-click Register/Login Screen-Set Component and on the front page, under Search bar, left-click on the plus (+) button.

In Step 1 (General) section:

  • Choose the ID (e.g., loginID) to be a unique value; this field is mandatory.
  • Choose the Name (e.g., LoginButton).
  • Choose the Login label that the component will display (e.g., Login) for anonymous users. When the user clicks this link, the Login/Registration screen-set will appear.
  • Choose the Logout label that the component will display (e.g., Logout) for logged-in users. When the user clicks this link, the Logout process will be triggered.

  • Click DONE.

RaaS Screen-Sets and Flows

Gigya's RaaS offers the following screen-sets.

Screen-Set ComponentScreen-SetDescriptionImplemented Flows (Click link for more details and a flow diagram)
Register/LoginDefault-RegistrationLoginAllows the user to log in or register. Also enables the user to initiate a password reset.Login, Registration, Forgot Password
GeneralDefault-ProfileUpdateAllows the user to edit their profile.Update Profile
Register/LoginDefault-ReAuthenticationEvoke this screen-set to require the user to re-authenticate anywhere added security is needed.Re-Authentication
Register/LoginDefault-LinkAccountsWhen a user is trying to register with a social account that shares an email address with an existing registered account, this screen-set can be evoked to merge the two accounts.Link Accounts
GeneralDefault-LiteRegistrationWhen a currently anonymous user would like to subscribe to a newsletter or register for an event with only their email address. Lite users can not login and do not have registered accounts.Newsletter Subscription or any other instance when you only require the user's email address and they do not need to have a full account.

New User Creation

RaaS includes social login in that it allows users to log in with a social network; otherwise they can register as a site user with a user ID and password. In any case, new users, whether they are social users (logged in with a social identity) or site users (registered in the site) are created both in the Gigya system and in your Hybris database.

6.  Integrating Customer Data Cloud Consent (OPTIONAL)

If you are using SAP Commerce Cloud < 6.5 you will map any Consent objects using the normal Field Mapping functionality as you would for any other Gigya field. This section is only relevant for SAP Commerce Cloud v6.5 or greater and only if you installed the gigyaconsent Addon in step 1.2 a during Installation of the GConnector.

Consent Template Creation

In order to synchronize gigya consent object to hybris, consent template should be created first. Without template the synchronization won’t be triggered. Based on the consent template a consent object is created/updated in hybris during login/registration/profile update flow and the value of ‘isConsentGranted’ field is synched. Bear in mind that the id of the template have to be exactly the same like id of the gigya consent in the gigya console. For instance if we have consent in gigya console with id = terms.test.consent, when we create a template in order to synch this object we have to put the same id.

  • Open the Backoffice.
  • In the left sidebar choose User Node.
  • Left-click Consent Template and on the front page, under Search bar, left-click on the plus (+) button.

In the Required (Required Fields) section:

  • Choose the ID (e.g., terms.testConsent) to be the same like consent id in Gigya console; this field is mandatory.
  • Choose the Site for which the consent should be applicable.
  • Choose the Version of the template.



The following video demonstrates the various customization options of the GConnector with SAP Commerce Cloud: 


Session Management

When using the GConnector with your site, you can manage your sessions in a number of different ways.

To configure sessions, navigate to the Session Management tab of the Gigya tab.


Press the PLUS button ( + ) to begin the wizard and use the guidelines below to configure your sessions.


First you may choose whether you want the GConnector to manage the sessions or use SAP Commerce Cloud. If you choose SAP Commerce Cloud (Hybris), then everything is handled by the Hybris CMS and the following configurations do not apply.



If you choose Gigya to lead the session, then the GConnector will control when the sessions end. The options available when selecting Gigya are as follows:

  • Session Type
    • n/a - Default; You can not create a new session manager with this option selected.
    • Sliding - You can configure how long you want your dynamic sessions to last, i.e., 30 minutes, and on every server interaction the user's session will be refreshed with the designated length.
      • Duration - When Sliding is selected, you will then have to enter the session duration, in minutes, that you want the session to be refreshed for. Recommended Best Practice is to never use sessions that are less than at least 5 minutes in duration. It is important to note that this setting should never be set to the minimum of 1 minute as this may cause intermittent and hard to diagnose login failures.
    • Fixed - You can set a finite period of time to allow a session to be valid, i.e., 30 minutes, and when the fixed session period expires, the user's session is terminated, whether they are still browsing the site or not.
    • Valid Forever - The session will be valid for 10~ years or until the session cookie is deleted.
    • Until Browser Closes - The session will end when the user's browser is closed (not the current tab). Note that due to the way some browsers (e.g., Chrome) manage their sessions, this may not always occur, as the session may be kept alive as long as the browser has processes running in the background (even if the UI was closed by the user), and will not actually terminate the session until the user restarts their computer.


After saving your first configuration, the Session Management page will look similar to the following.


At which point you can add additional configurations or edit existing ones, if needed, via the bottom pane of the page.


Session management configuration is complete. You can utilize a single session configuration between some or all of your storefronts, it is not necessary to create multiple configurations, unless you want the storefronts to have different session configurations.

If your storefront is part of an SSO group and you use Sliding (dynamic) Sessions on any of the sites of the group, all sites within the SSO group MUST use sliding sessions. Otherwise, SSO will not function properly. See Managing Session Expiration for additional information.


Field Mapping

By default, the following required Hybris fields are mapped from Gigya to Hybris on registration, login, and profile update:

  • UID
  • firstName

Map additional necessary fields following the instructions below:

  • In the Backoffice tree, open the Gigya Node and select Gigya Field Mapping.
  • On the front page, under Search Bar, left-click on the plus (+) button.
  • In the Step 1 (General) section of the Gigya Field Mapping Creation Wizard, due the following:
    • Select the configuration/storefront that you will be assigning the mapping.
    • Select the Synchronization direction; It is best practice to have identifiers synced in only a single direction, from Gigya to Hybris.
    • In the Attribute's name in Hybris field we will enter: uid
    • We will map the email field of the Profile object, so in the Attribute's name from Gigya field we will enter:
    • Select String as the Hybris Attribute Type.
    • Select False for the Custom option.
    • Click Create.

The license could not be verified: License Certificate has expired!

Select the Gigya configuration or site you would like to apply the mapping to. 

  1. Click Create or Save

Complex attributes are Hybris attributes (or Gigya JSON objects) that hold other fields within. To map such fields, you need to enhance the converter (hook). For more information, see below.

How to map an email to SAP Commerce Cloud ID

  1. Create a Field mapping
  2. Select synchronization direction (Generally it is good practice to have identifiers synced only in one direction Gigya to Hybris)
  3. We will be using the email from the profile object so on the Gigya’s attribute name we will enter:
  4. On Hybris attributes name we will enter: uid
  5. Select String as type
  6. Select the configuration/storefront to which you will assign the mapping
  7. Click Create

It is important to note that SAP Commerce Cloud uses 3 individual fields to keep track of the user. Even though we are mapping either the Gigya UID or Gigya to SAP Commerce Cloud UID, the specified field is also being mapped to Hybris fields named:

  • originalID
  • ID (Hybris uid)

The field named gigyaUID is always the Gigya UID regardless of whether you are setting the SAP Commerce Cloud UID as the Gigya UID or

Default mapping is only from Gigya to the CMS, syncing data the other way requires using custom hooks.

Mapping Complex Fields - Advanced

For example, a complex attributes could be a SAP Commerce Cloud product. They hold other models inside them: images, price groups, discounts etc.

  • Step 1: Prepare the server, command below stops SAP Commerce Cloud server.

    ./ stop
  • Step 2: Add java file inside the populators directory. 

    package com.gigya.login.service.converters.populators;
    import de.hybris.platform.converters.Populator;
    import de.hybris.platform.servicelayer.dto.converter.ConversionException;
    import org.apache.commons.lang3.Validate;
    import org.apache.log4j.Logger;
    import com.gigya.login.model.GigyaUserModel;
    import com.gigya.socialize.GSKeyNotFoundException;
    import com.gigya.socialize.GSObject;
    import com.gigya.socialize.GSResponse;
    public class GigyaUserNamePopulator implements Populator<GSResponse, GigyaUserModel> {
        private static final Logger LOGGER = Logger.getLogger(GigyaUserNamePopulator.class);
        public void populate(GSResponse gsResponse, GigyaUserModel gigyaUserModel)
            throws ConversionException {
            try {
                GSObject profile = gsResponse.getData().getObject("profile");
                String firstName = profile.getString("firstName");
                String lastName = profile.getString("lastName");
                gigyaUserModel.setName(firstName + " " + lastName);
            catch (GSKeyNotFoundException e) {
  • Step 3: Add bean below within root bean node inside the {extensionName}-spring.xml

  • Configure a custom hook

    <!--custom hook-->
    <bean id="gigyaUserNamePopulator" class="com.gigya.login.service.converters.populators.GigyaUserNamePopulator"/>
    <bean parent="modifyPopulatorList">
    	<property name="list" ref="gigyaCustomerAccountConverter"/>
    	<property name="add" ref="gigyaUserNamePopulator"/>
  • Step 4: Build and start a SAP Commerce Cloud server

    ant clean all && ./ start
  • Finally, create a field mapping that is marked as complex and set to Gigya to Hybris in the backoffice.


Sample Hybris Complex Attribute
	"USA": {
				"Population":"1.281 million",
				"Elevation": "131m",

If you want to map attribute from inner layers of the JSON to an attribute in the GigyaUserModel you can set the Gigya attribute’s name, for example This will map attribute that is in the following structure:


The Hybris attribute name is the name of the attribute inside the items.xml file and type system. For example if you have GigyaUserModel.getCountry(), you can write "country" in Hybris’ attribute name.

The SAP Commerce Cloud GConnector uses a custom converter whose bean ID is gigyaCustomerAccountConverter. To map complex fields, you need to extend this converter, by creating a populator which is added to the converter's list of populators. This is advanced configuration, and requires developer expertise in Hybris. 

To customize a converter: 

  1. Define a custom ID and class for your populator, for example:

    <bean id="gigyaCustomerKidsPopulator" class="com.gigya.login.service.converters.populators.GigyaCustomerKidsPopulator "/>
  2. Example structure for a populator: 

    public class GigyaCustomerKidsPopulator implements Populator<GSResponse, GigyaUserModel>
     private static final Logger LOG = Logger.getLogger(GigyaCustomerKidsPopulator.class);
     public void populate(GSResponse gsResponse, GigyaUserModel customerModel)
    //More implementation
  3. In the spring of the extension, assign modifyPopulatorList as a parent to your bean. For example, if the name of your bean is gigyaCustomerKidsPopulator, the code would look like this: 

    <bean parent="modifyPopulatorList">
       <property name="list" ref="gigyaCustomerAccountConverter"/>
       <property name="add" ref="gigyaCustomerKidsPopulator"/>

Available converters: 

Converter NameModel

In addition, the gigyaCustomDataReverseConverter is available for converting custom data from Hybris back into Gigya's data (custom) fields. 


Schedule Data Sync

The data in the mapped fields (above) is synced automatically every time a user logs in, or a user's profile is updated (regardless of whether it is being updated via the user or user or a Backoffice User). You can configure the way the synchronization will be handled in your Gigya Configuration. This synchronization happens via tasks or in the same thread as the update/login. By default, all synchronizations are asynchronous. 

You can also schedule a manual synchronization for a single user. Enable Data Sync by following the steps below:

  • In the Backoffice tree, open the Gigya -> Synchronization Task.
  • Left-click the plus icon.
  • Search for the customer you whose data you want to synchronize.
  • Select the configuration with which to make the call.
  • Choose the synchronization direction, where:
    • If you want to synchronize immediately leave the planned execution field empty.
    • If you want to schedule it for later click on the calendar on the right and select the date and hour.

Data Sync Technical Information

Synchronization Strategy

Synchronization strategy in the Gigya Configuration has direct impact on the performance. We recommend using the asynchronous strategy for all cases. When the synchronization is asynchronous a synchronization task will be scheduled for immediate execution.

Retry mechanism

The task has retry mechanism built in. The intervals between retries are growing with each fail with 15 minutes. Failures will not affect the login/update procedure or any other functionality. Each synchronized field is independent from the others, meaning that if one fails the other(s) will be synchronized.

Retry configuration

The retry mechanism is configurable via the properties files.

You can set the number of retries by giving the following property:

  • gigya.task.retry=10

By default this value is set to 5.


Importing existing users from a 3rd party system to Gigya via the SAP Commerce Cloud GConnector is not currently supported.



Generic Gigya Plugin

The Generic Gigya Plugin allows you to choose any social plugin offered by Gigya insert it into your Hybris website as a component. The functionality and design of each plugin can be customized extensively using Gigya API parameters.

Some of the Gigya plugins are:

  • Share Bar displays a bar of buttons for sharing to social destinations.
  • Comments allows users to add comments in your pages.
  • R&R give your customers an easy way to provide feedback on product and content across your site.
  • Reactions displays a one-click reaction buttons bar, allowing users to easily interact with posts or content on your site.
  • Loyalty plugins add a level of gamification to your website, including Achievements and Leaderboard.

For a full list of social plugins and usage guides, see the Gigya Plugins documentation.

To create the component:

  1. Open the Hybris Management Console.
  2. In the left sidebar, under Administrator, choose WCMS.
  3. Right-click Component and choose Create > GigyaGenericPluginComponent.
  4. In the component, go to the Administration tab and fill out a Name and ID and the Catalog Version.
  5. Scroll down to the Unbound section and enter the function name. This can be any function in the Gigya JS API. For example, to use Gigya's Share Bar plugin, enter "socialize.showShareBarUI". see the Gigya Plugins documentation for descriptions and technical details of the available plugins.
  6. Enter the parameters of the function according to the Gigya JS API documentation. Enter the parameters in JSON object format, i.e. {"key1": "stringvalue1", "key2": "stringvalue2"}.
    For example:

    Click to enlarge screenshot

  7. The Show Anonymous and Show Logged In radio buttons allow you to specify whether the plugin will be visible to anonymous users and to logged-in users. By default, it is shown to everyone.
  8. Click Create.


  • For sharing plugins, if a userAction object isn't passed in the function parameters, the plugin will look for an image with relevant Open Graph tags within the same page, and share that image. If no image has Open Graph tags, the plugin will share the largest image in the page.
  • Some Gigya plugins allow user registration. To enable users to register from within a Gigya plugin embedded as a component, make sure to set gigyaLoginBehavior to "Always login" in the General Setup.

Purchase Synchronization

Once you activate the Gigya extension, Gigya's Signals service (if it is available) begins to count user purchases and purchase amounts. Note that Signals is a premium feature and requires separate activation. Information from Signals is used in Customer Insights and the accumulated purchase values will show under Revenue Activity in Customer Insights.

Customer Insights allows you to analyze your website's performance by cross-referencing social network information, such as demographics and Facebook Likes, against the customers' activity on your site, including purchases.



  • The server clock must be set to GMT+0, otherwise errors and unexpected behaviors may occur. We recommend using NTP daemon to ensure that the server time is accurate.
  • Gigya screen-sets must entirely replace any login, registration, etc., screen provided by the CMS. The CMS registration, login and edit profile screens should not be rendered at all. Otherwise, the Gigya screen is placed inside the CMS screen and both will behave unexpectedly. 
  • After changing the value of the application key, you must re-enter the application secret.



SAP Commerce Cloud-Related Troubleshooting

  • You can review logs in the following way: 
    1. Open the SAP Commerce Cloud Administration Console  ( or
    2. Under the Platform tab, open Support
    3. Select the logs you wish to generate, and click Create
  • You can check if the Gigya module is installed correctly as follows: after logging in with Gigya, open the browser's developer tools. In the console, type window.gigyaHybris.authenticated. If the module is installed correctly, and you are logged in, it should return "true". 








  • No labels