Skip navigation
1 2 Previous Next

Do It

20 Posts authored by: Joel Rothman-Oracle

*NOTE* - On April 11th, 2014, LinkedIn made a change to their API. Please read about it here. This post has been updated to reflect those changes.

 

Social Sign On is a really interesting tool. It allows people to sign in to view your content using systems that they are familiar with.

Eloqua currently offers Social Sign On to LinkedIn, Twitter and Facebook via our Cloud Components.

When you use a Single Sign On, you are pushing the web viewer to a login page hosted by the provider, where the web viewer is giving the provider (Twitter, Facebook, LInkedin) permission to share their information with a third party. In order to do this, the third party needs to have a connection with the provider. Eloqua has set up a connection with Twitter, Facebook and LinkedIn, but it is branded as an "Eloqua" page. Clients can set up their own custom applications, which are branded as the client.

For example, the twitter page looks like this:

twitter SSO.jpg

I have underlined in red the piece that can be branded as your company.

 

In order to set this up, please follow these steps:

1 - In the "Cloud Connector" set up page, under "App to Use" select "Define a Custom App"

2 - Click on the "Get App ID". This will send you to the correct page for each provider. You will need to login using your credentials for Twitter/LinkedIn/Facebook

twitter custom app.jpg

 

Each provider is different, and they have been broken up below:

 

Twitter:

The URL for Twitter is the following:
https://dev.twitter.com/apps/new

Login using your Twitter credentials, and click "Create a new application"

 

The following fields are required:

  • Name - This is the name that will appear on the login screen that visitors see. It is recommended to use the name of your organization here
  • Description - This is not displayed to visitors
  • WebSite - Place the URL of your company here. It is not displayed to visitors
  • Calback URL - Place the following URL:

               https://cloudconnectors.eloqua.com/SocialSignon/TwitterSocialSignon.aspx

Once you have clicked "Create your Twitter Application", it is recommended to click on the"Settings" tab, and select a new icon for the app, preferable your company logo.
Copy the "Consumer Key" and the"Consumer Secret". These will need to be placed in the configuration area for the app within cloudconnectors.eloqua.com

 

LinkedIn:

The URL for LinkedIn is the following:

https://www.linkedin.com/secure/developer

Log in using your LinkedIn credentials, and click "Add New Application"

 

The following fields are required:

  • Company Name - This name is not displayed to visitors
  • Application Name - This name is displayed to visitors
  • Description - This value is not displayed to visitors
  • Application Type - Set this to"Web Application"
  • Application Use - Set this to "Other"
  • Live Status - Set this to "Live"
  • Developer Contact Email - Place your email address
  • Phone - Place your phone number
  • Default Scope - Select "r_basicprofile"
  • OAuth 1.0 Redirect URL - Set to the following:
    https://cloudconnectors.eloqua.com/SocialSignon/LinkedinSocialSignon.aspx
  • OAuth 2.0 Redirect URL - Set to the following:

          https://cloudconnectors.eloqua.com/SocialSignOn/LinkedinSocialSignon.aspx

  • Agreement Language: Set this to the appropriate language

It is recommended that you place a URL to your company logo. The URL should be 80 x 80. You can upload the image into Eloqua.

Copy the "API Key" and "Secret Key". These will need to be placed in the configuration area for the app within cloudconnectors.eloqua.com

In E10, the HTML of a form name needs to be set before the form can be enabled. To do this, please follow these steps:

Click on the Gear Icon and Select "Settings":

settings.bmp

In the new window, under "HTML Name" you can either manually type a name, or you can click "Generate". NOTE - If you are going to manually type a name, the system will ensure that it is unique. You cannot have 2 forms with the same HTML name.

name.bmp

 

A new button will appear named "Use". Please click that button, and select "Done"

use.bmp

Then, click "Save"

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please install the replacement app.

Webex App

 

This article will describe the individual pieces of the WebEx App, how to install it and it will outline a sample program. This document assumes the reader knows how to use Eloqua Program Builder, Eloqua Emails and Eloqua forms.

In order to use the WebEx App, you will need to have a valid WebEx account with API access. You will also need to register at cloudconnectors.eloqua.com

What is the difference between cloundconnectors.eloqua.com and Appcloud.eloqua.com

 

 

WebEx App Components

The WebEx App is made up of the following Connectors:

  • WebEx Register - allows you to register a contact to attend a WebEx event.
  • WebEx Unregister - allows you to unregister a contact for a WebEx event.
  • WebEx Query - allows you to determine whether a contact actually attended a WebEx event.
  • WebEx All Viewers - allows you to pull into an Eloqua group all the people who attended a WebEx event.

The first 3 are Cloud Connectors, which are used in Program Builder. The last is a Cloud Feeder, which automatically pulls records into a group in Eloqua

ARTICLE – What is the difference between an App, a Connector, a Component and a Feeder

 

How to Install an App

 

To install the Webex App, visit this page:
http://appcloud.eloqua.com/apps/webex-connectors

Click on the green “Get App” button in the top right corner:

install app.png

 

Installing Connectors:
A new screen will open. Click on the “Add Connector”:

add connector.png

 

IF you are not logged into Eloqua, you will be prompted to login. It’s recommended that you click the “remember me” button. After logging in, you will see a screen similar to this:

cloud connector management.png

 

The bottom portion of the screen shows any connectors that are currently installed. The top portion is where the connector is actually installed. Click the “Add” button:

add.png

 

If you receive an error similar to this, it means the Connector had been installed previously:

all ready exists.png

 

If you receive a confirmation similar to this, the App connector has successfully been installed:

successfully installed.png

Repeat this for any other Connector you would like to install

 

Installing a Cloud Feeder

Cloud Feeders have a different installation then Cloud Connectors.

NOTE - Before the Cloud Feeder can be installed, the event needs to be configured within WebEx.  You will need to input the following information into the Cloud Feeder:

  • WebEx User Name
  • WebEx Password
  • WebEx Session Type
  • WebEx Session ID
  • WebEx Organization Name

 

Create a user in your Eloqua install. This user is the one used to push data in through the feeder. It doesn’t need to be dedicated to one feeder, but it should be a user dedicated to API access. For more information about setting up a user, please search the knowledge base of the article titled "Eloqua-Setup"

 

Ensure the user is added to the “API Users” security group to ensure it has API access. As well, remember the username and password for the user, because you will need it for the next step.

 

Create a contact group in Eloqua to store the Contacts. For more information about creating a contact group, please search the knowledge base for an article named "Database Management".

 

If you would like to store the Start Time and the Minutes Attended, create those fields in Eloqua now. For more information about creating a contact fields, please search the knowledge base for an article named "Database Management".

 

To install the WebEx feeder, go to the following URL: https://cloudconnectors.eloqua.com/StepTypeOverview.aspx?StepType=WebExAllViewersQuery

Click on the “New Step” button.  You will be brought to a screen like this:

cloud login.png

Fill it out with the user credentials you created in the previous step.

You will be brought to the following screen:

config.png

 

Input the information collected from WebEx earlier.

Select the contact group created earlier.

Once everything is configured, you will need to enable the feeder. In order to do that, click on the “Credentials” tab within and select “Enable Step”:

login.png

 

Using the Connectors in Program Builder

 

Each connector executes as an action in a step in Program Builder. Once a contact hits that step, the Connector grabs that contact, and processes it based on the logic defined in the Connector. When it’s done, the Connector changes the status of the contact in the program, and the contact continues on its way.

 

 

To use the Connector in Program Builder, do the following:

Create a step in the program where you want the step to execute

Set the action of the step to: “Cloud Connector”

You will be provided with a list of Cloud Connectors that have been created. Select the correct one from the list:

list.png

Click on the “Configure Button”. This will bring up a configuration window from Cloudconnectors.eloqua.com (you may need to login to Cloudconnectors.eloqua.com):

config.png

Once you are logged in, you will need to input the credentials of the user that was created earlier:

cloud login.png

On the configuration and field mapping screen, you will have slightly different options for each CloudConnector.

 

They are as follows:

Configuration

 

Register Attendee

Unregister Attendee

Query Attendee

Description

Description

Y

Y

Y

 

WebEx User Name

Y

Y

Y

From WebEx

WebEx Password

Y

Y

Y

From WebEx

WebEx Session Type

Y

Y

Y

From WebEx

WebEx Session ID

Y

Y

Y

From WebEx

WebEx Organization Name

Y

Y

Y

From WebEx

Source of WebEx ID

Y

Y

Y

Is it the same ID for each contact, or is it dynamic based on an ID in a contact field

Send Email invitations

Y

 

 

Do you want WebEx to send the invitation, or do you want it sent from Eloqua?

Store Join Meeting URL in

Y

 

 

If you are sending confirmation from Eloqua, you can store the URL for the webinar on a contact field

Store Event Attendance Data in

 

 

Y

Do you want to store data on the Contact or in a custom object? If you run many events, you want to store in a Custom Object

 

 

Fields:

 

Register Attendee

Unregister Attendee

Query Attendee

Email Address

Y

Y

Y

First Name

Y

 

 

Last Name

Y

 

 

Title

Y

 

 

Company

Y

 

 

Address 1

Y

 

 

Address 2

Y

 

 

City

Y

 

 

State

Y

 

 

Zip/Posta

Y

 

 

Country

Y

 

 

Phone

Y

 

 

Join Meeting URL

Y

 

 

Minutes Attended

 

 

Y

Start Time

 

 

Y

 

 

 

 

 

Once everything is configured, you will need to enable the connector. In order to do that, click on the “Credentials” tab within and select “Enable Step”:

 

The Program     

Defining every step of how to configure the program is outside the scope of this article. Here is a sample program that can be used as a guide to creating your program:

program.png

 

NOTES:

The webex "Query Attendance" step can only return data for events that have occurred in the last 90 days.

Apps – Apps are tightly integrated widgets that extend the functionality of Eloqua. They include things like being able to display 3rd party content, integrating with other system, manipulating data or whatever else our community decides. Many apps are developed by Eloqua partners, third parties or even our clients. Clients can install unlimited apps. The only restriction is the number of API calls per day that can be used, which varies by client, but should be stated in their contract.


AppCloud
– The AppCloud is a centralized market of Apps available to Eloqua clients. It houses apps that are developed by Eloqua Labs, as well as third parties and partners. It is available at Appcloud.eloqua.com


CloudConnector
– CloudConnectors extend the functionality of Eloqua program builder. When enabled, a CloudConnector is executed from a step within Program Builder. When a record hits that step, it is grabbed by the CloudConnector, where it either modifies the record in Eloqua (such as a data append) OR triggers an action in a separate system (such as registering for an event).


CloudFeeder
- A CloudFeeder pulls in data from an external source, and automatically feeds it into a group in Eloqua. This can be used to append data (such as getting a records Klout score) OR to group records (such as webinar attendees)

 

CloudComponent – A CloudComponent extends the functionality of Eloqua Landing Pages in E10. It pulls content or logic from 3rd parties, and displays it on a landing page, such as Twitter Feeds or Facebook Single Sign On


Cloudconnectors.eloqua.com
– Apps are designed to run outside of the Eloqua application. Some apps, such as the Name Analyzer or the Math Functions are designed by our Eloqua Labs. These apps are hosted at cloudconnectors.eloqua.com. It requires a separate login to Eloqua, but it is free to access.

Eloqua has many apps that can be installed to extend the functionality of the application. These apps can be developed by our internal Eloqua labs team, but they can also be created by any third party (including by Eloqua partners, and by our clients).  The Eloqua AppCloud, which can be found at Appcloud.eloqua.com is a marketplace of apps, covering a wide range of functionality, such as events, data augmentation or social.

 

Although Apps are deeply integrated within Eloqua, they are outside of the code of the Eloqua application. As such, they need to be hosted and managed somewhere. Apps that are created by Eloqua labs are housed and managed at cloudconnectors.eloqua.com. Currently, cloudconnectors.eloqua.com houses Cloud Connectors and Cloud Feeders. It is free, but does require a separate login.

Filter Blog

By date: By tag: