Skip navigation
1 2 Previous Next

Do It

20 Posts authored by: Joel Rothman-Oracle

On April 11th 2014, LinkedIn introduced changes to their API. Something that used to be optional will start being required.

To read more about it, see this post by LinkedIn.


Who this affects:
If you are actively using the LinkedIn Social Sign on app AND you have created your own "custom app" (instructions here), you might need to make a change to the configuration in order for the app to continue functioning.


Who is not affected:

This does not affect clients who are using other LinkedIn apps (such as sharing), clients who are using other social sign on apps (such as facebook and twitter) or clients who are using the LinkedIn social sign on with the standard, Eloqua app.


To validate IF you are affected, navigate to the LinkedIn social signon app via this link:

You will see a list of ALL instances of the app.

Click the "pencil" arrow beside the app to edit it

Under "LinkedIn App to Use", if you have selected "Define a Custom Linkedin App", this will potentially affect you:


Make a note of the value in the field "LinkedIn API key". You might need it later.


To Update LinkedIn:

To correct the issue, login to the LinkedIn developer portal:


If you see several apps, find the app that contains the same "LinkedIn API key" that you noted earlier. To find the key, click on the title of the app. Scroll halfway down to the section named "OAuth Keys" and look at the value int the field "API Key".


If there are no apps that have that API Key, most likely the Social Sign On app was created by someone else. In that case, please follow these instructions to create a new LinkedIn app. You will need to update each instance of the Eloqua Component with the new App Key and Secret.


Once you have found the correct app, copy the following value into your clipboard:

*NOTE* - This is case sensitive. Make sure you input it EXACTLY as it is above


Paste that value into the field "OAuth 2.0 Redirect URLs":


Click save.


It is recommended that you validate the Social Sign On app to ensure it's working correctly.

In the Spring '13 release, Eloqua upgraded its SQL Server Integration Services (SSIS) to the latest version, which gives clients greater speed and stability on uploads. This new version does not allow for source files that are formatted incorrectly , where syncs that were previously running correctly are no longer successful, causing issues for many clients.

If you receive an error similar to the following, you need to fix the source file:

The column delimiter for column "<column name>" was not found

This error generally means that there is an extraneous column present for example, there is no value in the header row, but there is a value within one of the subsequent rows.


Column A

Column B


Text A

Text B

Text C



If this is a one time upload, please open it in a spreadsheet program and validate that there is no data past  the last column that has a header. If there is, remove it and resave the file. If there is not, delete ALL the columns past the last one, and resave the file. Then, try the upload again.

As a temporary measure, clients with recurring uploads that are formatted in this way have had the functionality rolled back to the earlier version to allow for correction of the source file. Over the next several months, we will be communicating with clients a timeframe of when they have been will be moved to the new system, to allow for changes to be made at the source.

This post outlines the campaign that I went over during the "Driving Social Demand with Eloqua's Social Suite" session at Eloqua Experience 2012 in Orlando!



Description of Campaign:

The campaign encourages people to give you their twitter handle AND follow you on twitter. The specific example I gave was to offer a chance to win a $5 gift card to Starbucks everyday. The campaign uses Social Suite apps to capture the entry into the contest (via Twitter Social sign On), ensure that the record is following your Twitter account. It automates following them back. It gets the contacts social ranking (via Klout, but it could just as easily be Radian6). People with a high Klout score are direct messaged to ask if they enjoyed the content.


NOTE - Much of this campaign is applicable to ALL users of Eloqua, however the apps used on the landing page are only available in E10.


Purpose of this Article:

This article will describe how to set up this campaign, and where possible link to other existing articles on Topliners.



Here is a screen grab of the campaign:

EE2012 - Campaign Flow.png


Here is a screen grab of the landing page:

landing page sample.png


Apps used in this campaign:

Twitter Social Sign On Component - Social Sign On - Installation Guide

Slideshare Component - Installing and Using the SlideShare Cloud App

Twitter List Component - Installing and using Social Suite: Twitter


Twitter "Is Connected" Connector - Installing and using Social Suite: Twitter

Twitter "Follow" Connector - Installing and using Social Suite: Twitter

Klout Score Connector - Setting up the Klout Cloud Connector

Tweet Sender Connector - Tweet Sender - App Configuration Guide



Components of the AppCloud

For an explanation of the difference between a "Connector" and a "Component", please see this article:

Components of the AppCloud


How to enable Components

Components first need to be enabled in your install. You must be a customer administrator in order to enable a component.

For more information on how to do that, see this article:

The specified item was not found.



How to Install Connectors

Connectors can be used in either Canvas (in E10) or Program Builder (both E9 and E10). All the apps described in this article can be found on, and installation instructions are there. For more information about installing connectors, please see this article:

Cloud Connector Installation, Step by Step

This article reviews some of the testing tools that are available for end users of Apps. Not every App that is hosted on has every test option outlined below. They are typically found on connectors and feeders (the difference is explained here).



This document is not for testing the DEVELOPMENT of Apps. It is meant for end users


Accessing the Test Tools

When you are looking at the configurtion window for an app, you will see a series of buttons along hte left hand side. Click on the "Test" button:

test tools.png


You will see a potential mix of different tabs, depending on the app you are looking at. The options are as follows:


Step Members:

step members.png

This tab shows records that are in the step in Program Builder or Canvas, and what "state" they are in. IF a record appears in a step, but is not represented here, then the Program or Canvas has not executed yet. Clicking the "Refresh counts" button will refresh the number of records in each state.

Awaiting Action - These are records that are waiting for the App to process

In Progress - The app has started processing these records

Complete - The app has finished processing these records (but they are still in the step in PB or Canvas)


Under the "Action area, you can select the drop down and change the state of a record to either "Awaiting Action, "In Progress" or  "Complete". You select the option that you would like, and click "Go"


Run Manually

Run Manually.png

Run Manually allows you to manually execute the App. It is typically used in both Connectors and Components

You have 2 options:

Dry Run - A dry run executes the call, either on the contacts in a step OR for the relevant contacts in a feeder. There MUST be records in the step within Eloqua. IT DOES NOT modify the data within Eloqua. If there is a per transaction cost with the 3rd party, this will typically NOT use those calls

Full Run - A full run executes the call, either on the contacts in a step OR for the relevant contacts in a feeder. There MUST be records in the step within Eloqua IT DOES modify data within Eloqua. If there is a per transaction cost, it will be incurred.


Both run modes display the information back from the third party within the screen. Both only execute off 10 records



Sample Data

Sample Data.png

Sample Data is typically used with connectors. It allows you to define a contact (which does not need to be within the step in Program Builder or Canvas).

To use, place 1 email address per line. A contact MUST exist in Eloqua with the email address that is inputed.

By default, Sample Data runs as "Dry Run" mode above (where data is displayed, but not committed to Eloqua). If you want to have the data pushed to Eloqua, click on the "Full Run" button.

Click "Test Contacts" in order to execute.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

Tweet Sender

This guide will go over the installation and configuation of the "Tweet Sender" app.

The Tweet Sender app allows you to send a tweet to a contact in Eloqua. IF the twitter handle associated to a contact is follow the authorized Twitter account, a Direct Message (DM) can be sent to the Twitter handle. You can personalize the tweet with up to 2 fields from the contact.


It is assumed that users of this guide are comfortable with Program Builder OR Campaign Canvas. This app is supported on ALL versions of Eloqua.

As well, you will need an account on to use this connector. Sign up at



How to Install the App

As of the writing of this guide, this app is not available on, and must be installed from (please see this article to understand the difference).

Visit this URL and click on the "Install Connector" button, and follow the steps (NOTE, your Eloqua user will need to be an adminstrator user in order to install):


Using the Connector


The connector is triggered off a contact. It can be triggered from either Program Builder OR Campaign Canvas.


Campaign Canvas:


The tweet sender is used the same as a regular action in Canvas. Double click or drag "Send to Cloud Connector" from the left hand navigation (under the Actions header). The step will appear. Double click the step, and select "Tweet Sender" from the list:


canvas component.png

Click the icon to the right in order to start configuration.


Program Builder:


The tweet sender executes as a regular action step in program builder.

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:


Click the "Configure" button.


Configuring the Tweet Sender

If you are not already logged into, you will be to do so:

cloudconnectors login.png

On the next screen, you will be prompted to input the information for an Eloqua user. Please ensure the user has API access:

cloudconnector login 2.png


On the next screen, (configuration) you will need to do 2 things:

- Authorize a twitter account (this is the account that the Tweet will be sent from)

- Define the Twitter Message.

tweet sender config.png


Authorize Account:


Click on the "Authorize Account" button. This will bring you to a Twitter login screen. Please login with the correct account, and click the "Authorize App" button.


Twitter Message:

Here is where you input what the message looks like. URL's will automatically be shortned (using the T.CO shortner), and message longer then 140 characters will be truncated. You have the following configuration options available:

Direct Message - To make this a Direct Message (DM) place a lowercase d at the start of the tweet.

Twitter Handle - to include someone's Twitter handle, include the following ||TwitterID||. If you want to @message them, place it as such @||TwitterID||

Personalization from Contact fields - You can include personalization from up to 2 contact fields. The fields are defined in the "Mappings Area". To include the personalization, please insert: ||Pers1|| and ||Pers2||



Under the mappings area, you will map 3 fields from the contact:

Twitter ID - this is the field the Twitter handle

Twitter Personalization Field 1 - This is the field that stores the personalization message ||Pers1||

Twitter Personalization Field 2 - This is the field that stores the personalization message ||Pers2||


NOTE - Although you do not need to use both personalizations, you do need to map a field into them


Enabling the Step:

Remember, in order for this app to be live, you need to enable both the program/canvas AND the app. To enable the app, click on the "Credentials" tab, and then click the "Enable Step" button:


Because sits outside of the standard Eloqua code base, it has a separate release structure, with releases happening in a much more frequent manner.

This post will be updated with release notes for each release. Please check back often, or follow this post for the most up to date information.

IF you have questions, please make a comment and include the release date.


October 27, 2012:

  • Improvement - RSS Component added validation for URL structure of feed

October 25, 2012:

  • Overall Speed Enhancements
  • Bug Fix - Static value from query string in Progressive Profiling

October 12, 2012:

  • Form Prepop now supports checkbox fields
  • Bug Fix - email address in pre pop components


October 6, 2012:

  • UI Improvements to Box Content app
  • String Manupulator support for large text fields
  • Bug Fix - Form Submit accepting comma


September 30, 2012:

  • Fixes to Brainshark feeder
  • Fixes to Survey Gizmo feeder
  • Slideshare embed released


September 23 2012:

  • Radian6 "Buzz Widget" available
  • Polls supported in Survey Gizmo
  • Slideshare app available
  • Upgrades to UI framework

September 15 2012:

  • Improvements to Box app UI

September 11 2012:

  • Box embed - General updates
  • Bug Fix - Wrong screen displayed intermittently when editing field mappings
    Lithium - UI Bug fix

September 7th 2012:

  • Continued increase in throughput for connectors
  • Increase in speed-to-pick-up connectors the first time a contact goes into the step
  • Box component had preview added to show live doc
  • Box file explorer added
  • On24 register connector - BUG FIX - not sending blank values
  • On24 feeders now update-but-not-create contacts if setting is set as such
  • Lithium - BUG FIX - dates fixed


August 24th 2012:

  • Increase in throughput for connectors for faster execution of large data sets
  • Small UI tweaks
  • connector - display fields were added (revenue, employees)
  • Progressive Profiling - Ability to upload query strings.

The Eloqua AppCloud lets Eloqua clients integrate with webinar events providers quickly and easily.

Currently, Eloqua has prebuilt integrations with the following webiner providers:

  • Adobe Connect
  • Citrix GoToMeeting
  • On24
  • Readytalk
  • WebEx


Each provider is slightly different. So, this article will walk through the different connection points that are available, as well as the different fields returned per call.


First off, some definitions:

  • Register- This is the act of registering an Eloqua contact through Campaign Canvas to an event
  • Unregister - This is unregistering an Eloqua contact through Campaign Canvas to an event
  • Query - This is taking an Eloqua contact, who has hit a specific step in Campaign Canvas and seeing if they are registered for an event
  • All Viewers - This is a sych that runs on a regular interval (daily, weekly, monthly) OR just one time, and returns everybody who viewed an event. The data can be stored on a contact OR a custom object (data card)
  • All Registrants - This is a sych that runs on a regular interval (daily, weekly, monthly) OR just one time, and returns everybody who registered for an event. The data can be stored on a contact OR a custom object (data card)
  • Join Meeting URL - Some providers have a unique join meeting URL, which is returend when a contact is registered. This URL can be stored on a contact, and prepopulated in an email
  • Send Registration Confirmation - Some providers will trigger a confirmation email to a contact when that contact is registered. This is an email not sent by Eloqua
  • Multiple Events - This is the ability to store an "event ID" on a contact, which can be used by the step to determine which event to register a contact for. It allows for 1 step to be used for multiple events


Calls Offered:

RegisterUnregisterQueryAll Viewers (Feeder)All registrants (Feeder)Join Meeting (URL)Send Registration confirmationMultiple Events
Adobe ConnectYYYYY
Citrix GoToMeetingYYY



Fields Returned:


Adobe ConnectCitrix GoToWebinarOn24ReadytalkWebEx
CallRegisterQuery AttendanceAll Viewers QueryRegisterQuery AttendanceAll Viewers QueryRegisterQuery AttendanceAll Viewers QueryAll Registrants QueryRegisterQuery AttendanceAll Viewers QueryRegisterQuery AttendanceAll Viewers
EntityContactContact/Data CardContact/Data CardContactContact/Data CardContact/Data CardContactContact/Data CardContact/Data CardContact/Data CardContact/Data CardContact/Data CardContact/Data CardContact/Data CardContact/Data CardContact/Data Card
ICS File w/ Join LinkReceived
Meeting Details (Title, Audio info etc...)Received
First NameSentSentSentReceivedReceivedSentReceivedSent
Last NameSentSentSentReceivedReceivedSentReceivedSent
Email AddressSentSentSentReceivedReceivedSentSentReceivedSent


Job TitleSentReceivedReceivedSentReceivedSent
Address 1SentReceivedReceivedSentReceivedSent
Address 2SentReceivedReceivedSentReceivedSent
Home PhoneSentSentReceived
Work PhoneSentReceivedReceivedSentReceivedSent
Company IndustrySentReceivedReceivedSentReceived
Job FunctionSentReceivedReceivedSentReceived
Company SizeSentReceivedReceivedSentReceived
Custom Fields10 - Sent51033
Minutes AttendedReceivedReceivedReceivedReceivedReceivedReceivedReceivedReceived
Number of Questions AnsweredReceivedReceived
Live Attendance DurationReceivedReceived
Archived Attendance DurationReceivedReceived
Polls AnsweredReceivedReceived1010
Surveys AnsweredReceivedReceived
Questions AskedReceivedReceived
Start TimeReceivedReceivedReceivedReceivedReceived
First Entrance TimeReceived
Last Exit TimeReceived
Partner Ref fieldReceived
Late Registrant Handling for E9Available
Automatic Check for New ContactsAvailable
Meeting IDReceivedReceivedReceived



*NOTE - Sorry for the poor formatting of the table, I am limited in how I can format it. I will attach an XLS with the info as well

**EDIT - This article has been updated to reflect changes in the ReadyTalk app, which can be downloaded from here:ReadyTalk Connectors | Eloqua AppCloud | All the apps for Eloqua in the cloud!**

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


Static HTML App


This article describes the Static HTML ap, how to enable it in your Eloqua instance, and how to place and configure it on an E10 landing page. This document assumes that the reader is an E10 user, and is familiar with using landing pages.


In order to use the Static HTML app, you will need to be registered at


What is the difference between and


What is the Static HTML App?

Many web services allow you to embed their service onto your page, by allowing you to paste in a snippet of HTML code. This is often used for Youtube videos, embedded maps and other web services. The Static HTML app allows you to leverage all of the power of Eloqua's landing page editor, as well as allowing you to easily embed content from other sources.


Static HTML App Components

The Static HTML app consists of a single Cloud Component


How to Install the Cloud App


The Cloud App is already available for use in E10, but may need to be enabled.  See The specified item was not found.for more information.


Using the Components on a Landing Page


A Cloud Component is inserted into a landing page via drag and drop within the landing page editor.


From the editor toolbar, select the "Cloud Components" button.  A select box containing all of the available Cloud Components will then be displayed.




Drag and Drop the Static Content component onto the landing page:






Next, save the page, then double-click the component that you just dropped onto the page.  The following screen will appear:




Enter your credentials and click Log in.


The following screen will appear:



Place the HTML into the "Content" section, and click "Save Settings"


Close out the "Static Content Setup" window, and save the Eloqua Landing page.


View the landing page on the live URL to see the content. The content WILL NOT render within the editor, you must view the content on the live page.



What use cases have you used the Static HTML app for? Leave a note in the comments!

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

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 It's free.

What is the difference between and


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:

Eloqua 10 Form Editor Overview


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:

Eloqua 10 Form Editor Overview


Once the form is created, please ensure that the HTML form name is defined. Please see this article on how to do so:

Creating HTML Form name


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:

The specified item was not found.


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.

Cloud Components Button.png

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 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 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:

field mapping.png

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.


Additional Questions?

IF you have additional questions, please visit the Social Sign On FAQ

This article outlines the different icons available for the TwitterSocial Sign On App.

For a guide on how to use these apps, please see:

Social Sign On - Installation Guide



Dark Color, Large:


Dark Color, Small:


Light Color, Large:


Light Color, Small:

This post answers frequently asked questions regading Social Sign On (in no particular order):


What is Social Sign On?

Social Sign on allows Eloqua E10 clients an easy way to let visitors to their website "log in" via social networks, to access content or register for an event. Any time you use a form, you can use Social Sign on



Which 3rd parties is Social Sign On currently offered for?

Eloqua currently offers Social Sign On for the big 3, Facebook, Twitter and LinkedIn



What are the main differences between each provider?

Facebook embeds the form right on the page. For Twitter and LinkedIn, you will be sent to a page hosted by that service, to login. Each service returns different fields



What fields are returned?

To see a list of fields returned, please see the following article:
Social Sign On Fields Returned



The field I need is not in their, can I add custom fields?

Yes, custom fields can be added. For Facebook, it will be embedded right on the page. For Twitter and LinkedIn, a form will appear with the custom fields directly after the sign on



How do I tie this to a contact?

Facebook returns an email address, but LinkedIn and Twitter do not. You can add email as a custom field, and a contact will be created or updated with the mapped information. IF you do not ask for email, a contact will still be created with a place holder email, such as ""



How much does it cost?

It's free for any user of E10


Great, how do I get started?

See the installation guide that is available here: Social Sign On - Installation Guide








What about signing on via XYZ?

Well, that's a great idea! Our partners are constantly building out new integrations. If you want, you can log an "Idea'" through our support portal.



Please post other questions you might have in the comments. I will update the body of this post with questions as they are received.

Joel Rothman-Oracle


Posted by Joel Rothman-Oracle Jun 8, 2012

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions


The Eloqua Social Suite integrates with Radian6 via the Eloqua AppCloud.


For more information about Radian6, please visit their site:


To install the app, please visit:


The Radian6 App has 2 pieces in Eloqua. They are:


Radian6: Influencer Feeder - Allows you to use Radian 6 to feed in the top influencers on a particular topic:

This feeder will search Twitter for records that are Influencers on topics you define in Radian6 and feeds them into Eloqua on a nightly basis. The records can be stored as either Contacts or Data Cards in Eloqua. The following fields are returned:

Influencer Total Score

On Topic Post Count

Following Count

Followers Count

Updates Count


Radian6: Influence Query - Allows you to use Radian 6 to understand a person's engagement with a particular topic.

This connector will send Eloqua contacts to Radian6 (through either Campaign Canvas OR Program Builder). The results can be stored either as Contacts or Data cards in Eloqua. The following fields are returned:

Influencer Total Score

On Topic Post Count

Following Count

Followers Count

Updates Count

Eloqua offers Social Sign On with Twitter, Facebook and Linkedin.


The following fields are returned from those sites:


LinkedIn IDNameTwitter Handle
First NameEmailName
Last NameLocationScreen Name
Location NameBirthdayProfile Image URl
Number of RecommendersFollowers Count
Number of ConnectionsFollowing Counbt
Picture URLLanguage
IntestestsTime Zone
HonorsTweet Count
Date of Birth
Company Type
Company Industry
Current Position Title
Current Position Start Date
Current Position Summary


As well, each provider allows you to add custom fields.

A new feature has been added to, that allows you to easily tell if your app is enabled or not.


First, some quick background. When you are configuring any app that is hosted on, you must configure it, then enable it when you are done, so that it executes. This step was often missed. So, now there is a queue to remind you to enable the step.


See how the Credentials tab is red, and has a little red dot? That means it is not currently enabled:

not enabled.png

So, to enable the app, click the "Credentials tab". Under "Settings", click "Enable Step":

make enabled.png

Now, the "Credentials" tab should have changed to green:


This article is to outline the standard pieces of an app built on



The credentials area is where you connect the CloudConnector with the Eloqua application. It typically has the following fields:

Eloqua DB - This is the instance of Eloqua that the connector is being configured to access. It is typically a name, with no spaces. This instance must have the API enabled.

User Account - This is the username of the Eloqua user that is accessing the Eloqua DB. This is typically a name (first name and last name) separated by a dot, with  no spaces. It is not an email address. This user must be in the API access security group.

Program Builder Step ID - This is the ID of the step within the Eloqua program builder. It is normally populated when the Connector is first configured. IF not, you can find that information within the step in program builder.

Enable Step (Run Automatically) - If this is set to disabled, the connector will not run. In order to run automatically, this needs to be set to enabled.

The configuration area will have fields that are specific to the connector being set up. It will often require the username/password for a third party system. As well, IF data can be potentially stored in multiple places within Eloqua (ie - Data Card OR Contact), or a specific Eloqua Asset needs to be selected (Form, Contact Group), it is typically done here.

Field Mappings:
If fields need to be mapped, either from Eloqua to a third party service OR from the third party service to Eloqua, it is done here.

Run Step:

Run step has 3 separate sub tabs:


Step Members:

This tab shows the records within the step in Eloqua. IF the numbers are off, you can click "Refresh" to have the service update with the current information.

The step shows 3 "statuses". They are:

Awaiting Action - these are records who have hit the step in program builder, but not been picked up by the Cloud Connector

In Progress - these are records who have been picked up by the Cloud Connector, but who have not been returned back to Eloqua

Complete - These are records who have been processed by the Cloud Connector and returned to Eloqua

Under step members, it is possible to reset the status of a record (ie - if you wanted to retest a record, you could set a record from Complete to Awaiting Action)

Run Step:

If there are records in the step in program builder, WITH the status of "Awaiting Action" you can run the step from within Cloud Connectors. This pushes a maximum of 10 records through. There are 2 options:

Dry Run - This will reach into the step in Eloqua, and return the ACTUAL data that will be sent to the 3rd party. It sends the data to the third party, with a flag indicating it's test data. It displays the data that is recieved back from the third party, but does not write the data into Eloqua.

Full Run - This will reach into the step in Eloqua, and return the actual data, which will be sent to the third party. The data will be returned and written to the Eloqua database.  If there is a cost to use the third party system, this will be incurred.

Sample Data:

The Sample Data tab allows you to processes records that aren't currently in the step in Program Builder. However, the records DO need to exist within the Eloqua install that is using the connector. IT will populate with the email address of the person configuring the step. Input each email address on it's own line. IF you do not check the "full run" box, this will be run as a dry run. If you do check the box, it will be run as a full run. Click "Test Contacts" to run.


The history area shows the following information:

Total Queries - This shows how many times the step has processed

Valid Transactions - This shows how many times a record has been processed

Last Run time - This shows the last time the step executed

Error Count - IF there are errors this will show a count of them

Error Log - This will show the error message and the time

Filter Blog

By date: By tag: