You are not logged in.   Log in | Register

Site Setup

From $1

To get your Gigya Socialize implementation up and running, please make sure that you have properly configured your site details in our Site setup section.

 

 

Note - If you are not logged-in to Gigya:

  • Please go to http://www.gigya.com/ and log in.
  • Click on the "Get Gigya Socialize" tab and then hit the 'Edit' link on the right hand side of the page:

    generalsite.jpg


The following guide explores the available options and serves as a reference document for the configuration options:

 

Step 1

Please make sure that your site/widget domain is listed in the domains' table in the Site Setup page. To add a domain, please do the following:

Enter the domain name in the text box, and press the "Add site" button (see screen shot below).

 

addsite.jpg

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

 

After you have configured your domain you will be able to get your Gigya API Key. This key is used in every page in which Gigya Socialize Widgets or API calls are integrated.

Also, please note that the "Secret Key" is provided at the bottom of the page. This key may be used to generate and check Cryptographic Signatures to verify the authenticity of Socialize processes and prevent fraud.

 

Step 2

Press the "Edit" button that corresponds to the domain you wish to configure.

editlink.jpg

You will be redirected to the "Configure Site Settings" page, where you will find a form that you need to fill. The form consists of two parts:

The first part ("Configure Social Network Application Keys") is compulsory and the second part is optional.

 

Configure Social Network Application Keys

Gigya Socialize uses external applications to deliver its services in social networks. The external applications act as mediators, enabling Gigya Socialize to provide the various functions it offers – such as retrieving user info or sending notifications.

For Gigya Socialize 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 through the Request Application Key page on the Gigya website.

This is a screen shot of the form in Gigya website Site Setup for setting up social networks external applications:

configure.jpg

 

Configure Domain Alias (CNAME)

Some social network require a sub domain to make callbacks to. We highly recommend specifying a sub domain in your site and defining a CNAME entry in your DNS server that maps the sub domain to socialize.gigya.com. This provides the following benefits:

  • Simplifying the Facebook Connect flow, by removing the "Allow Offline Access Authorization" screen.
  • 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.gigya.com) to access the user’s OpenID data.


To apply this with Gigya Socialize please:

  1. Define a CNAME entry in your DNS server: specify a new sub domain in your site and point it to socialize.gigya.com. For example:
    socialize.yoursite.com   CNAME    socialize.gigya.com

     

  2. Enter your CNAME value in the corresponding text-field (see screen-shot below).
    Note: only sub-domain of the domain which you have configured in Step 1 will be accepted.

    SiteSetup_CNAME.gif

     
  3. When configuring the external applications for each social network make sure to follow the instructions for sites using Domain Alias. Mark below the social networks you have configured to use your Domain Alias.
    For example, in the screenshot we have marked the 'Facebook' and the 'Myspace' checkbox. This means that when opening an external application in Facebook and when opening an external application in MySpace , we should paste the CNAME sub domain instead socialize.gigya.com in the required places.

    Note: If you mark "Facebook", it is recommended to provide the 'Facebook "via" link redirect URL' (see screenshot above). The "via" link is shown in the Facebook newsfeed (see screenshot below). The URL you provide will be used to redirect users when clicking the link.
    SiteSetup-viaLink.gif

 

Optional Configuration

Configure your Site URL

The configuration form provides instructions for setting up site URLs. Please follow them to setup any URLs you wish include in this configuration.
If the Gigya Socialize configuration applies to all the different 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 sub domains only (i.e. "articles.gigya.com").
  • Apply the configuration to specific paths (i.e. *.gigya.com/articles/*)

 

congurl.jpg

 

Custom URL Shortening

Gigya includes a URL shortening service for URLs, which you publish to social networks using Gigay's API. If Gigya's URL shortening service is active, each of the distributed URL will be shortened to a URL with the soc.li domain. 

If you wish to setup a custom short URL that will be used when publishing content to Social Networks, please: 

 

  1. Define a CNAME entry in your DNS server: specify your short domain and point it to soc.li. For example:
    short.yoursite.com    CNAME    soc.li

     

  2. Enter your CNAME value in the corresponding text-field (see screen-shot below).

    SiteSetup_shortURL.gif

 

 

Facebook wall updates permission

This section is relevant to sites/applications which plan on:

  • Publishing posts into your users' Facebook profile and Newsfeed for the actions they take on your site.
  • Updating users' Facebook status.

Facebook requires the user to specifically opt in before your application or site can publish to the user's stream.

The user will be prompted by the following dialog, the first time your application attempts to publish to their stream:

SiteSetup_Facebook-AllowPublish.gif

Using this dialog the user will decide whether or not to grant your application permission to publish to their stream. If the user presses the "Allow Publishing" button, your application will receive indefinite privilege to publish, and the user will not be prompted by this dialog again.

 

This section of the Site Setup, gives you the option to change default behavior, and prompt the permission dialog while connecting to Facebook (as opposed to - while attempting to publish). To do that, check the "Request permission on login" check-box, as shown in the screen shot below:

SiteSetup_WallPerm.gif

 

 

Enable Offline access in Facebook

When this box is checked and the user connects to Facebook, he will go through an extra page that will ask for the permission to let your site perform actions on his behalf while the user is offline. Unless you intend to perform offline actions, such as automatically sending notifications to the user, we recommend keeping this option unchecked so the process of connecting to Facebook will be shorter.

SiteSetup_OfflineAccess.gif 

 

Enable retrieving email addresses from Facebook

The following check-box is unchecked by default. You may want to check it if you plan on sending emails to the users' mailbox using Facebook's contact email.

SiteSetup_EnableEmail.gif

 

If you check this checkbox, while connecting to Facebook, users will be presented with the following additional screen for allowing sending them emails:

SiteSetup_Facebook-AllowEmails.gif

 

If a user chooses to press the "Allow" button, you will be able, during the connection session, to receive his email address by calling the socialize.getUserInfo API method. The email address is provided as a field of the User object (named "email"), which you receive as part of the socialize.getUserInfo method response. 

 

The user may choose to change his contact email to his proxied email, as illustrated in teh following screen shot:

SiteSetup_Facebook-AllowEmails-Proxied.gif

In such case, when calling the socialize.getUserInfo API method you will receive the user's proxied email instead his regular email addresses. The proxied email is a field of the User object (named "proxiedEmail"), which you receive as part of the socialize.getUserInfo method response.

Facebook provides proxied emails as a channel through which your application can contact your users. The proxied email address can be used just like a regular email address.

 

Enable Facebook automatic session renewal

Determine weather Facebook sessions should be renewed automatically.

Note: If you plan on using Facebook Connect API directly, then this checkbox must be checked.

SiteSetup_AutoRenew.gif

Tags:
Files (0)