GConnector is a tool that makes it easy to implement Gigya within a CMS or e-commerce platform, while leveraging the best of Gigya functionality without compromising the CMS capabilities. When using GConnectors, the user's session and user data are synced in real time between Gigya and the CMS, providing a smooth, cohesive user experience, and providing site admins with up-to-date, workable data. GConnectors share the same design principles. 


Core Features  

Extended Functionality

GConnector Identity Data 

The main RaaS actions (i.e. login, register and edit profile) are mirrored in the CMS user management system. This is achieved by registering to Gigya’s onLogin event, and creating or updating a user account in the CMS. In the case of mismatching data (for example, the user's country is registered as France in Gigya's database and Germany in the CMS database), the Gigya data overrides that of the CMS. 

The flow when a user logs in is as follows: 

<img src="https://docs.google.com/drawings/d/1wlrNOuFjKDGii1Fp_9Fln4-V2xlCwSayseadu_rQS-g/pub?w=720&amp;h=540">

UID-Based Sync

Data Store Sync

When implementing Gigya's Data Store (DS) to store user-related data, GConnectors may offer a DS Sync module that adds the ability to pull data from Gigya's Data Store and map it into the user account database in the CMS. This is provided through an optional, separate package that is installed separately.

This capability is currently available for the following connectors:

Back End Sync

In some cases, the GConnector includes a module for synchronizing Gigya data to the CMS back end or back office, where CMS admins manage user data.

This capability is currently available for the following connectors:

Field Mapping

Fields in one database are dynamically mapped to the corresponding field in the other database. For examples, see Gigya Connector for Drupal 8Gigya Extension for Magento 2.0, and Gigya Connector for Sitefinity 9

By default, the GConnector usually maps the following fields for every user in every CMS: first namelast name, and email


GConnectors usually offer the option of registering to specific events and adding custom code. Gconnectors offer hooks that are fired after the following events:


Gigya is committed to maintaining the highest level of security. Our platform is designed to protect customer data with a series of strict security and compliance standards which are applied to our GConnectors as well. These include the following principles: 

Configuration Options

Generally, the GConnector configuration options (sometimes available within the CMS Admin area) align with those of Gigya's Global Configuration. In addition, they include

Multi-Site and SSO Support

GConnectors support multi-site implementations. Configuration for each site is independent, and in some cases sites can inherit configurations from a master site. In addition, SSO is supported by Gigya. For more information, see Site Groups and Single Sign-On 

When configuring an SSO segment, the session management of all sites in the segment should share the same definition: 


For customers who implement Gigya's Consent Management, enables syncing the user's consent status to a consent object or custom field in the target platform. Connectors who have this feature can dynamically call any Gigya screen during the various customer interactions with their site. 

This is supported for the following GConnectors: 

Lite Screen-Set

Support showing the Lite Registration screen-set, for registering passwordless users via the connector integration. Lite registrations is used for newsletter subscriptions, lead generation and other customer communication use cases. The information is saved to Gigya's database. 

This is supported for the following GConnectors: 

GConnector Data Flow

The following diagram illustrates the typical data flow between Gigya (RaaS accounts namespace and Data Store) and the CMS (both client and server side), using the GConnector extension of the CMS. 

For a list of links to the APIs participating in this flow and other relevant documentation, see below. 

This flow is relevant both to implementations that use Gigya's Screen-Sets and custom screens with Gigya's Web SDK.

participant CMS Client Side
participant CMS Server Side
participant Gigya
participant DS
Note over CMS Client Side: User clicks "Login"
CMS Client Side->Gigya: accounts.login
Gigya-->CMS Client Side:onLogin event
CMS Client Side->CMS Server Side: AJAX request to handle CMS login \n with UID, signature and timestamp
CMS Server Side->Gigya: accounts.exchangeUIDSignature
Gigya-->CMS Server Side: User signature
CMS Server Side->CMS Server Side: Validate user
CMS Server Side->Gigya: accounts.getAccountInfo
Gigya-->CMS Server Side: User object 
Note over DS: Optional
CMS Server Side->DS: Get DS info \n (triggered by post getAccountInfo hook)
DS--> CMS Server Side: DS info \n Fires post ds.get hook
Note over CMS Server Side: Post merge hook
Note over CMS Server Side: Field mapping \n (Data transformation)
Note over CMS Server Side: Custom field mapping using hook
CMS Server Side->CMS Server Side: Create user/update existing user
CMS Server Side-->CMS Client Side: User is logged in to Gigya and CMS

APIs and Objects Used in GConnectors



Feature Overview

All GConnctors support the following features: 

In addition, the following matrix outlines supported features per connector:

CMSData Store SyncBack Office (Bi-Directional) SyncUID-Based SyncGigya-Led Session ManagementUser DeletionLite Screen SetUser Consent
Drupal 7   
Drupal 8 
SAP Commerce Cloud  
Magento 1   
Magento 2
Salesforce Commerce Cloud     


Product Updates

You can view the change log of the following GConnectors: 

 Internal - How to Open a CMS Ticket

  1. Open the Support tab of Gigya's Console.
  2. The subject of the ticket should follow this structure:

    PartnerID <CMS Name> Assign to R&D <case issue>

  3. Assign the ticket a "high" priority.

  4. Once the see "Assign to R&D" in the ticket title, they assign the ticket to the relevant R&D team.

  5. The should follow these guidelines when handling the case.

For websites which implement both a CMS and Gigya, a GConnector is a tool that makes it easy to implement Gigya within a CMS or e-commerce platform, while leveraging the best of Gigya functionality without compromising the CMS capabilities.