Social Sign On
This guide will go over how to install and configure Social Sign On.
Social Sign On allows visitors to your Eloqua landing page to "Sign On" to view content using Facebook, Twitter or LinkedIn. Behind the scenes, an Eloqua form will be submitted, which will capture the fields passed back from the social network, as well as determine the next action (ie - what page to display, which campaign to add the record to, etc...).
In order to use Social Sign On, you must have an account at http://cloudconnectors.eloqua.com. It's free.
Social Sign on App Components:
The Social Sign On Apps are made up of the following Cloud Components:
- Twitter Signon
- LinkedIn Signon
- Facebook Register
As well, a form will need to be created in Eloqua to capture the correct information. For information regarding form creation, please see this video:
Social Sign On fields returned
Each social network provides a different set of fields. See this article for the standard fields that are returned. For each provider, it is possible to add additional, custom fields.
How to Install the Cloud App
Please see the following article on how to install Cloud Apps:
The specified item was not found.
Using Social Sign On
Creating the form:
The first thing that you should configure is the form. The form is used to map the fields from the App into an Eloqua contact, as well as determine where the contact will go after the submission.
Please see the following video on creating a form:
Once the form is created, please ensure that the HTML form name is defined. Please see this article on how to do so:
You will need to create all the fields that you are capturing via Social Sign On as "Form Fields" within the design component of the form. If the social provider returns a field that you aren't interested in, just do not create one here. Ensure that you have a contact (or data card) field to map to each field returned. IF one does not exist, you can create fields by following these instructions:
The specified item was not found.
It is recommend that you have, at a minimum the following processing steps defined:
Update Contact - with Form Data - Here you will map the Social Sign On fields to the Contact
Redirect To Web Page - Here you will define where the submitter will go AFTER they have signed on
Placing it on the landing page
Social Sign On elements can be dragged onto a landing page in E10. Please see this video to familiarize yourself with Eloqua Landing Pages:
Once the landing page has been configured, you can drag the App on, and place it wherever you would like. To find the App, click the "Cloud Components" button along the left hand side.
This will pop up a "Cloud Components" selector window, where you can search for the correct app:
Drag the app from the selector window, and drop it onto the landing page. The actual size of the button is determined by the configuration of the app, but you can resize the window as you see fit. When you preview the page, you will see that you might need to adjust the size.
Once the app is placed, it is recommended that you save the landing page.
Configuring the App
To configure the app, double click on the icon on the landing page. This will pop up a window, that looks like the following:
Type in your CloudConnector.eloqua.com username and password. IF you do not have one, click the "Create User" button, and follow the instructions.
Once you have logged in, you will see the following screen:
Login using your Eloqua credentials. You must have API access on your user. If you do not, please log a case with Eloqua support.
Once you are in, you will see a page similar to this:
- Eloqua DB: This is the Eloqua install that is being connected with. It is the same as submitted on the previous screen
- Eloqua Username: This is the Eloqua user name that is being used to connect with. It is the same as submitted on the previous screen
- Eloqua Password: This is the password for the Eloqua user. It is the same as submitted on the previous screen
- Component Owner: This is the cloudconnectors.eloqua.com user that created this app (ie - you!)
- Admin Email Address: This is the email address where any admin communications (ie - API errors etc...) will be sent
- App to Use: Twitter and Linkedin require an "app" be set up in order to access their API. This app controls the look and feel of the 3rd party login page. Eloqua has created an app for ease of use, but it is branded as an Eloqua. IF you would like to create a custom app for your company (With custmized name and logo) please select "Define a Custom App" and see this article : Social Sign On - Custom Apps (For Twitter, and LinkedIn)
- Icon (Twitter Only): Several different icons are available. See this article (Twitter Icons)
- Page Title/HTML Prior to the Form/HTML After the Form/Submit Button Name/CSS Content: These fields allow you to skin the secondary form page, which will only appear IF you are asking custom fields.
- Target Form: The data can be posted to either an Eloqua hosted form, or an external form. It is recommended that you select "Eloqua Form"
- Eloqua Form: Here you will select the form that was created earlier
- Form Field Mappings: This is where you map the fields from the third party (Twitter, LinkedIn or Facebook) and the custom fields you defined to the Eloqua form fields. More information below
- Form Submit Mode: It is recommended that you leave this as the default "Production (Automatically submit form)".
Form Field Mapping
The form field mapping screen is broken up into 2 sections, "Standard Fields" (fields returned by the third party) and "Custom extra fields" (additional fields that are being asked on the form:
To see a list of standard fields returned, please see this article (Social sign on fields returned)
To add a standard field, select the field from the drop down, and click "Add Standard Field". You will now be able to map it to any field you have defined on the form.
To add a custom field, click "Add Custom Field". Input a name and a type, and select the form field you would like to map it too.
Once you are done, click "Set Values".
You must map either an email field as a custom field OR an Eloqua Social ID as a Standard field.
IF you have additional questions, please visit the Social Sign On FAQ