Admins: How to integrate Gigya SSO with Qualifio?

Tabata Vossen -

The Gigya and Qualifio integration combines the power of Gigya's seamless customer identity management experience with first-party data collection. Discover how to integrate Gigya SSO and Qualifio and identify participants more easily.


To configure Qualifio's integration with Gigya, you need the following:

  • A Gigya single sign-on enabled subscription
  • An Admin role in Qualifio

Adding Gigya to your integrations

To integrate your existing Gigya login system into Qualifio, you need to enable Gigya from Settings > Integrations & Partners > Gigya SSO and then click the ON/OFF button.


Configuring Gigya SSO

Click Configure and follow these steps:


  1. Type a name for your integration:
  2. Under Global, select a login screen type: Redirect (redirect campaign participants to your login/register website page) or Screen-Set (integrate your Gigya Screen-Set into your campaigns).
  3. Enter your Gigya user key, secret key and API key.
  4. Enter your Screen-Set name or your redirection URL (see below for details on both options).


Note: Values are to be copied from your Gigya Console. If you have trouble finding them, please contact Gigya Client support team to get these values.

Configuration for each site can be independent, or inherit global configurations. For instance, this is useful in case you want to show a different Gigya login screen to participants based on which site they are on.


 Click Save to save your settings.

Gigya Redirect

With the Redirect option, campaign participants are redirected to your Gigya login/register screen. After login/registration is completed, they are redirected back to your campaign.

If you choose to go for the Redirect option, you will be asked to enter your Gigya Redirection URL. The Redirection URL should be composed of your login/register website page URL (e.g.,, etc.), followed by a URL redirect parameter (e.g. ?redirect=, ?destination=, etc.). See example below:


This URL redirect parameter will be used to redirect your participants back to your campaign after they logged in or registered. The destination page (what comes after this URL parameter) is generated on Qualifio's side, you don't have to worry about it! However, you are responsible for making sure you set up the right parameter name (e.g. ?redirect=, ?destination=, or whatever your naming convention is) and ensure the redirection works properly. Any questions? Contact our Support Team!

Gigya Screen-Set

With the Screen-Set option, your Gigya login/register screen-set is integrated into your campaigns.

If you choose to go for the Screen-Set option, you will be asked to enter the name of your Screen-Set. See example below:

Screenshot_2019-10-24_at_17.11.32.png The Screen-Set is then initiated by calling:

screenSet:'Default-RegistrationLogin' //The default start screen is login.

This calls the login/register Screen-Set. The rest of the flow depends on user interaction.

If the participant chooses to log in, we retrieve and read their user account data with the gigya.accounts.getAccountInfo method.

# Define the API and Secret key (the keys can be obtained from your site setup page in the Gigya console).
# Enter the proper Data center (us1, eu1, au1) if not using us1.
# Requests include a secret and MUST be sent over SSL.

# You can copy and import the code below directly into Postman.

curl -X POST \ \
    -H 'content-type: application/x-www-form-urlencoded' \
    --data-urlencode "apiKey=[Enter-Your-API-Key-Here]" \
    --data-urlencode "secret=[Enter-Your-Secret-Key]" \
    --data-urlencode "userKey=[Enter-Your-Application/User-Key]"\
    --data-urlencode "UID=Enter-Valid-UID-Here" \
    --data-urlencode "include=identities-active,identities-all,identities-global, loginIDs, emails, profile, data, password, lastLoginLocation, regSource, irank, rba, subscriptions, userInfo" \
    --data-urlencode "extraProfileFields=languages,address,phones, education, honors, publications,  patents, certifications, professionalHeadline, bio, industry, specialties, work, skills, religion, politicalView, interestedIn, relationshipStatus, hometown, favorites, followersCount, followingCount, username, locale, verified, timezone, likes, samlData" \

Note: The Screen-Set will only be shown if the participant is not yet signed-in with Gigya.


The profile information is saved in the campaign statistics and pushed to Gigya.

To push the profile data back to Gigya, Qualifio uses the accounts.setAccountInfo method:

# Define the API and Secret key (the keys can be obtained from your site setup page in the Gigya console).
# Enter the proper Data center (us1, eu1, au1) if not using us1.
# Requests include a secret and MUST be sent over SSL.

# You can copy and import the code below directly into Postman.

curl -X POST \ \
    -H 'content-type: application/x-www-form-urlencoded' \
    --data-urlencode "apiKey=[Enter-Your-API-Key-Here]" \
    --data-urlencode "secret=[Enter-Your-Secret-Key]" \
    --data-urlencode "UID=Enter A Valid UID Here" \
    --data-urlencode "data={'testField001':'newData_001'}" \
    --data-urlencode "profile={'firstName':'Haley','email':''}" \
    --data-urlencode "rba={'riskPolicy':'failedLoginLockoutUser'}" \

Response example:

    "statusCode": 200,
    "errorCode": 0,
    "statusReason": "OK",
    "callId": "ddb3f8e144c84cb5b1bc5f010bddab2b",
    "time": "2015-03-22T11:42:25.943Z"

Sending the data back to Gigya is done in real time so you can start using it for segmentation and targeted real-time marketing right away.

If you do not want us to send the data back to Gigya, please contact your Qualifio Expert.

What data is pushed to Gigya?

Qualifio CRM Variable Gigya Parameter Example Value Management Rule
{username} profile.username  jdoe123 Sent back to Gigya to overwrite existing value
{firstname} profile.firstName John, Jane Sent back to Gigya to overwrite existing value
{lastname} profile.lastName Doe Sent back to Gigya to overwrite existing value
{email} Primary key which identifies the profile – field not shown to participants
{address} profile.address Rue de Birmingham 280 Sent back to Gigya to overwrite existing value
{zipcode} 3290 Sent back to Gigya to overwrite existing value
{locality} Diest Sent back to Gigya to overwrite existing value
{country} Belgium Sent back to Gigya to overwrite existing value
{phone} profile.phones.number 0487 66 49251 Sent back to Gigya to overwrite existing value
or be added to the existing one(s)*
{birthday} profile.birthDay
06/05/1959 Sent back to Gigya to overwrite existing value 
{gender} profile.gender f/m/u Sent back to Gigya to overwrite existing value
N/A profile.languages English, French, Dutch Background data sent back to Gigya to be added to the existing value(s), separated by a comma
N/A profile.UID String of 32 characters Background data saved in the campaign statistics but never edited

* This depends on a fairly technical setting and the format of your data in Gigya. You will either get a unique value (previous phone number is overwritten with new phone number) or a list of values (new phone number is added to existing phone numbers). For technical information about this, please contact your Qualifio Expert.


  • The domain of your Qualifio campaigns must not be if a "Custom API Domain Prefix" was enabled in your Gigya Console. Read more
  • When using Gigya SSO on mobile, we strongly recommend choosing the Gigya Redirect mode over the Gigya Screen-Set one. Because multiple iFrames are used, the latter has some differences between mobile and web screens and may not be responsive on mobile devices.
  • The only fields that are supported and can be sent back to Gigya are the ones in the table above. The Gigya SSO integration currently doesn't support fields linked to custom CRM variables.


Additional resources: