Was this article helpful?

Site Setup

Last modified 08:53, 12 Mar 2014

The following guide walks through Gigya's setup and serves as a reference document for the configuration options.

If you are not signed in to Gigya, please go to http://www.gigya.com/ and sign in or register, by clicking the Try Gigya button on the top right-hand corner of Gigya's site.

Use separate site definitions for every environment required by the development process.  For example, if you use three environments: Development, Staging and Production, you will need separate site definitions for each environment.  


Add Your Site

Once you sign in to Gigya, you will be able to view your Dashboard. The first thing you must do to get your Gigya implementation up and running, is add your site domain name to the sites table in the Dashboard page.

Press the "Add site" button:



Fill in the site domain, and optionally a description, and press "Add Site":


Note: A valid domain should be entered in the form of "mysite.com" (there is no need to include the "http://" prefix). If you are using Gigya in Flash applications, please enter the URL of the location from where your SWF files are stored and downloaded.

Clients with sites defined under Gigya's European data center should replace domain references to (http:// or https://) "socialize.gigya.com" (or "socialize.us1.gigya.com") with "socialize.eu1.gigya.com". To verify site location contact your implementation manager.
Domain references are defined in Gigya's dashboard, externally in social network app definition pages, and when using Gigya's SDKs to set the domain (in particular the APIDomain field in class GSRequest). 

Your domain name should now be listed in the Sites table:




The API key that is associated with your domain is next to the domain name in the table. This API key will be used in every page in which Gigya plugins or API calls are integrated.

Note: Production environment API keys should not be used for testing. Use separate site definitions and API keys for test and production sites.

Partner ID

The partner ID is displayed at the bottom of the table.

Secret Key

The "Secret Key" is provided at the bottom of the table. This key may be used to generate and check Cryptographic Signatures to verify the authenticity of Gigya processes and prevent fraud. Read more about the subject in the Security page of our Developer's Guide.

Site Settings

When you press the "Site settings" of your domain, you will be redirected to the Site Settings page, where you will configure social network application keys.


When you press the "Reports" link, you will be redirected to the site's reports page. Read more in our Reports guide.


When you press the "Plugins" link, you will be redirected to the site's plugins page. Read more in our Plugins guide.

Technically you are now ready to use Gigya in your application. 

Note: If you have not yet obtained Social Network keys for your application, and are still using temporary Gigya keys, continue to the next "Site Settings" step.


Approved URLs

The configuration form provides instructions for setting up site URLs. Please follow them to setup any URLs you wish to include in this configuration. If the Gigya service configuration applies to all parts of your site, you will not need to change the default configuration. However, if you wish to configure specific parts of your site to work under these settings, you can use the URL settings to:

  • Apply the configuration to specific subdomains only (i.e. "articles.yoursite.com").

  • Apply the configuration to specific paths (i.e. *.yoursite.com/articles/*)



Configure Domain Alias (CNAME)

For general information about configuring providers, see Setting Up External Applications.
Some social networks require a subdomain to which to make callbacks. We highly recommend specifying a subdomain in your site and defining a CNAME entry in your DNS server that maps the subdomain to client-proxy.us1.gigya.com. This provides the following benefits:
  • Redirecting users to your site from the Facebook "via" link in newsfeed items.

  • Featuring your site in the OpenID authentication flow. Users will be prompted to allow your site (instead of allowing socialize.us1.gigya.com) to access the user’s OpenID data.

  • A better user experience on platforms such as iPhone, Android, Windows Mobile.


Note: Customers on the European Data Storage Center need to point their CNAME to client-proxy.eu1.gigya.com not to client-proxy.us1.gigya.com. If you are based in Europe consult your Implementation Manager to find out whether you are on the EU DC.

To apply this with Gigya:

  1. There are two methods you can use to define a CNAME entry in your DNS server:

    1. Contact your provider and request a CNAME entry. Specify a new subdomain in your site and point it to client-proxy.us1.gigya.com or client-proxy.eu1.gigya.com.

    2. Define a CNAME entry in your DNS server. Specify a new subdomain in your site and point it to client-proxy.us1.gigya.com or client-proxy.eu1.gigya.com

For example:

login.yoursite.com   CNAME    client-proxy.us1.gigya.com 

Note: the CNAME must be a subdomain of your site. In other words the CNAME must end with your site name.

  1. Return to Gigya settings and enter your CNAME value in the corresponding text-field (see screenshot below).
    Note: only a subdomain of the domain which you have configured in Step 1 will be accepted.

  2. You can choose to enable CNAME for all OpenID providers - this will enable sites that use Social Login via OpenID to display their own domain name in the Social Login dialogs instead of "Gigya socialize":


Custom URL Shortening

Gigya includes a URL shortening service for URLs that you publish to social networks using Gigya's API. If Gigya's URL shortening service is active, each of the distributed URLs will be shortened to a URL with the fw.to domain for customers using the US data center or the shr.gs domain for customers using the European data center.

If you wish to set up a custom short URL that will be used when publishing content to social networks: 

  1. Define a CNAME entry in your DNS server. There are two methods you can use to define a CNAME entry in your DNS server: either contact your provider and request a CNAME entry, or define a CNAME entry in your DNS server.  Specify your short domain and point it to fw.to (US data center) or shr.gs (European data center). For example:

    short.yoursite.com    CNAME    fw.to    


  2. Return to Gigya settings and enter your CNAME value in the corresponding text field (see screenshot below).



Redirect Method

You can select your short URL redirect method out of the following options:

  • Javascript redirect Use Javascript to do a client-side redirect, not adding anything to fragment or query string
  • Server redirect, replacing existing URL fragment Use HTTP 302 redirect and append a new URL fragment or replace the existing fragment
  • Server redirect, append to existing URL fragment - Use HTTP 302 redirect and append a new URL fragment or concatenate to an existing fragment like a query string (with & separator)
  • Server redirect, append query string if URL fragment exists - Use HTTP 302 redirect and append a new URL fragment if one doesn't already exist and a query string if a URL fragment does exist on the target URL

The default redirect method is JavaScript.



Gigya encrypts usernames, emails, friends' names and friends' emails. Encrypted fields are stored and transmitted encrypted. Gigya manages decryption.
Personal identity information (
PII) is also encrypted but can be switched off if the Enable PII encryption checkbox is de-selected in the Site Settings:


When Enable PII encryption is checked, the following fields are encrypted:

  • In the Profile object "firstName", "lastName", "address",  "name", "phones".
  • In the Identity object "firstName", "lastName", "address", "phones". 

To set encryption for specific fields, including fields which are not covered by PII encryption, use accounts.setSchema or IDS.setSchema

Note that SQL-like queries such as accounts.search, IDS.search and the Identity Query Tool cannot use comparison operators (>, >=, <, <=), the contains keyword or regex expressions on encrypted fields.

For more information see Security & Privacy.

Configure Social Network Application Keys

Press the "Providers Configurations" tab under the "Site Settings".



You will be directed to the Providers Configurations page, where you must configure social network application keys.

The Gigya service uses external applications to deliver its services in social networks. The external applications act as mediators, enabling the Gigya service to provide the various functions it offers – such as retrieving user info or sending notifications.
For the Gigya service to work in your site, a dedicated external application is required for each social network you wish to use.
The following tutorials will guide you through the process of opening and setting up external applications:


We will be glad to assist if you need help with this process. You can contact us by filling in a support form on our site.
This is a screenshot of the form in Gigya website Providers Configurations for setting up social networks external applications:



Considerations for SN Apps when SSO is Enabled

When SSO is enabled, sites have the option of only configuring apps at the parent level, which will then apply to all child sites. However, if the site defines an application that is not the default (group) application (at the parent level), then the child site's application will be used, overriding the group application. The implications are:

  • A user may not connect to different accounts of the same SN in different sites. So if the user connected to FB account #1 in site A he must connect to the same FB account in site B or he will get an error.
  • When a user is logged out and then logs in for the first time to a site that belongs to the group using a social identity that was already used in a different site in the group he should be connected to the same group account as he was before.
  • When disconnecting from a provider on one site, all the connections for that provider (on all other sites) should be removed.


Facebook Configuration

When you click on the Facebook icon, the following dialog opens:



Enable Automatic Session Renewal

Determines whether Facebook sessions are renewed automatically.

Note: you may choose this option only after you have configured a Domain Alias (CNAME) for your site.

You need to enable automatic session renewal in order to log the user out of Facebook when calling socialize.logout.

Facebook External Application Canvas Page

This section gives you the option to provide a page URL that we will shown as an IFrame on the external application canvas page.

Note: a prerequisite for this feature is to open an external application in Facebook and to define the extra settings in the Optional - for advanced users only section.


Gigya Support

We will be glad to assist you with implementation, configuration, or any other issues. You can contact us by filling in a support form on our site. You can also access the support page by clicking "Support" on the upper menu of Gigya's site:


Fill in the form and you will receive the support you need.



If you have "Admin" status on your site, you can access the "Admin" link placed on the upper menu:


As administrator, you can:

  • Manage Users - you can add, edit, and delete users, and change their account permissions.
  • Export Chat Logs - you can download a CSV file of your chats for backup purposes.


This page has no custom tags set.


You must to post a comment.