Skip navigation

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


SnapApp Feeder


This article will describe how to set up and configure the SnapApp Feeder application.  This application will allow you to "feed" new contacts into Eloqua (or update those that already exist) based on their interaction with your SnapApp(s).


In order to use the app, you must be registered at


What is the difference between and


Installation and Pre-Configuration


The SnapApp Feeder does not require installation, as it is a standalone application that runs outside of Eloqua, and connects to your instance.


Things you'll need to do first:

    • Make sure that the Eloqua user account that is being used for the feeder has Eloqua API access.
    • Create a Contact Group in Eloqua (called a Shared List in E10), to store the Contacts created/updated by the feeder. For more information about creating a contact group, please search the knowledge base for an article named "Database Management".
    • Create a DataCardSet (Custom Data Object) in Eloqua, to store the information returned by the feeder.


Setup and Usage


To access the feeder, first visit and log in.


Once logged in, click on the Apps menu.



Next, click on Feeder, then SnapApp Feeder.  The following screen will appear:


Click New Step, and you will be presented with the following


Select your Eloqua Credentials and click GoThe Configuration page will then be displayed.


On the Configuration tab, enter the following information:

    • Description (optional):  Some text about describing this feeder instance
    • SnapApp Username:  Your SnapApp Username (email address)
    • SnapApp API Key:  Your SnapApp API Key
    • SnapApps to Display:  Controls which SnapApps are shown in the SnapApp drop-down list.  Options are:
      • All Apps: Will list all of the SnapApps in your account
      • Apps by Campaign: Will present you with another option to select a Campaign from your account, then will display the SnapApps associated to that campaign.
    • SnapApp:  This is the SnapApp that you want to feed data in from.
    • Contact Group for Results:  The Contact Group/Shared List that you'd like the contacts added to when the feeder runs.
    • Store Data In:  Where you would like the return data stored in Eloqua.  The only option for this feeder is Custom Data Object.
    • Custom Data Object:  The Custom Data Object to store the SnapApp data in.


Depending on the type of SnapApp you select, the following additional settings will be displayed:


    • Questions:  Up to 10 questions that you want to track the answers to (for Quiz type SnapApps) .


    • Additional Fields:  Up to 5 additional fields that you wish to track.


    • Click Save Settings.


Now, click on the Field Mappings tab to choose where you would like to put the data returned from SnapApp when the feeder runs.


On the Mappings tab, choose which Eloqua Contact and Custom Data Object fields to map to corresponding data from the SnapApp system.

    • For the Custom Data Object fields, the list selections will be populated based on the existing Custom Data Object chosen on the Configuration tab.
    • For Display Name Field, the field you choose MUST be set as Unique in Eloqua in order for the feeder to function properly.  (Note: this field cannot be set to email address - see Eloqua Cloud Apps: Custom Object Unique Codes for more info).


Depending on the type of SnapApp you select, the following additional mappings will be displayed:


    • Answers:  The answers to up to 10 questions that you chose on the Configuration tab (for Quiz type SnapApps).


    • Additional Fields:  Up to 5 additional fields that you wish to track.


    • Click Save Settings.


Now that the Configuration is complete, and the Mappings have been set, it's time to Test the feeder.  Click on the Test tab.


On the Test tab you can test run the feeder. You can choose between a “Dry Run” (no data will be written to Eloqua) and a “Full Run” (The data will write to Eloqua – this is effectively a manual run of the feeder).


The History tab shows a history of previous feeder runs.


Once all is configured, all that is left to do is switch back to the Credentials tab and Run the feeder.


Now that the feeder is configured and enabled, the leads from your SnapApp will begin to flow into Eloqua.  If the contact does not exist in Eloqua, a new one will be created, and a custom object attached to the record containing the returned data.  If the contact already exists, the record will be updated accordingly, and a new custom data object attached to it.

Now that we've looked at Event / Webinar Cloud Apps - Registering Dynamically, let's look at how to dynamically query for attendance.


There is a new capability within the Event/Webinar cloud apps (WebEx, Adobe, Citrix GTW) that allows you to dynamically source the ID from either a contact record, or a custom data object.


In the previous post, we registered the contact for an event, sourcing the ID from the contact record.  When we did that, the connector created a Custom Object/Data Card, mapped to each contact record, that contained the Event/Webinar ID.  We want to use the ID contained in that same Custom Object / Data Card to query for attendance.  When the attendee is found, we also want to write the attendance data back to the same Custom Object / Data Card.


Let's start by setting up a Query connector.  On the Configuration page, choose to source the ID from a Custom Data Object Field.



If you choose the source type of Dynamic (in a Custom Data Object Field), when the connector runs, it will look at the contact and find all of their mapped Custom Objects/Data Cards in the chosen Custom Data Object/Data Card Set.


Now let's set up a rule to handle the case where multiple custom objects are returned for a given contact.  In the Dynamic Event Source Configuration section, choose your Selection Rule.  Based on your choice, the section will be displayed as follows:

Eloqua Cloud Connectors - Step Details - Google Chrome_2013-02-15_15-45-30.png


Eloqua Cloud Connectors - Step Details - Google Chrome_2013-02-15_15-45-43.png

The Selection Rule will be evaluated against to field chosen for Field to Evaluate on the Mappings page.  The choices are as follows:

  • Latest of Date Values - Returns the object with the field containing the latest (most recent) of date values.
  • Earliest of Date Values - Returns the object with the field containing with the earliest (oldest) of date values.
  • Field Contains Value - Returns the object with the field containing the Comparison Value.
  • Field Equals Value - Returns the object with the field exactly matching the Comparison Value.


We now have our rule for matching, but we'll need to chose the Field to Evaluate, as well as the Custom Data Object field that contains the Event/Webinar ID to use for the query.



When the connector runs, if multiple records are found, it will apply the Selection Rule to the Field to Evaluate and return the matching record.  It will then and retrieve the Event/Webinar ID from the chosen field in the Custom Object, and use that to query for attendance.  The attendance data will be written back to the same object that acts as the source.


By using these new dynamic ID source capabilities, you can streamline your Event/Webinar management.

In addition to the recent release of Form Tools - Running a Cloud Connector via Form Processing Step, enhancements to the Eloqua Event/Webinar apps were also introduced.  Now you can Form Tools - Running a Cloud Connector via Form Processing Step, and also use a field on the contact record or a mapped Custom Data Object, as a dynamic source for the Event/Webinar ID.


This means that you can use the same custom object created when you registered the contact, to query for attendance and hold the returned data.


To see this in action, let's first configure a Form Tool to register a contact. (Note: this will also work when running the Register connector on the canvas or program builder)


Start by following the step from Form Tools - Running a Cloud Connector via Form Processing Step.


On the Configuration screen, let's choose to source the ID dynamically from a contact field.

Eloqua Cloud Connectors - Step Overview - Google Chrome_2013-02-19_16-07-51.png

If you choose the source type of Dynamic (in a Contact Field), when the connector runs, it will look for the ID in the contact field that you specify on the Mappings page.

Eloqua Cloud Connectors - Step Overview - Google Chrome_2013-02-20_11-26-39.png

By doing this, we can use the same connector to register contacts for different events/webinars.  So, we can put a form field containing the ID (hidden or shown) on your registration form and map it to the contact record.  When the contact submits the form, the ID will be written to their record.  Now, when the Form Tool executes for the contact, it will use the ID found in the field and register them for that Event/Webinar.


The other thing we'll do is save the Join URL, Event/Webinar ID (and any other returned data) to a Custom Data Object/Data Card Set.

Eloqua Cloud Connectors - Step Overview - Google Chrome_2013-02-20_10-12-16.png

When the connector executes, it will create and link a new Custom Object/Data Card to the contact, in the specified Custom Data Object/Data Card Set that contains the Event/Webinar ID.


Now for the really cool part...we can use this same Custom Data Object with the Query connector, and dynamically source the ID from the Custom Data Object itself.  So, we can use the same object to hold both the Register information (Join URL etc) and the Query results (minutes attended, polls answered etc.).


See Event / Webinar Cloud Apps - Querying Dynamically for details on how to do this.

With the most recent release of, you may have noticed a New Form Tool button on the connector overview pages.


You may be asking yourself "what is that" or "how does that work"??  Well, with this new feature, you now have the ability to set up a Cloud Connector to run "one-off" when a contact submits a form.


To illustrate how this works, let's walk through an example.  As a marketer, I want to be able to use the WebEx Register Attendee connector to register a contact for an event.  I have found that, when using the connector in a program, I am unable to process those "last minute" registrations due the run cycle of the steps on the canvas.  Since I am already using a form submit to add contacts to the program, which in turn kicks off the registration step, it would be really great if I could just execute the same connector functionality as soon as form is submitted.  Well, this is where Form Tools come in!!


Here's how to set things  up...


Start by logging into, the clicking on the App menu.



Next, select the WebEx: Register connector from the Communicate menu.  (NOTE: You can set up any program step-based Cloud Connector as a Form Tool)


The connector overview page will then be displayed.



Click on the New Form Tool button.  The Credentials page will be displayed.



Choose your Eloqua Credentials, and then click Go.



When the New Form Tool page shows up, you'll notice that the page looks exactly the same as it would if you were setting the connector up from a program step.  The difference here is that you do not need to Enable the step, as this will not run on a scheduled basis.  More on that later.


Continue to Configure the app as you normally would, and don't forget to set up any required Mappings.  When this is complete, Save your setup and then click on the Instructions link.


The Instructions will then appear, explaining how to use the new Form Tool.  Highlight and copy the URL shown next to the "Point the processing step to" will need it for the next step.


Go into Eloqua, and if you have not already, create the form that will be used for the event registration.  In the Form Editor, go into the Processing Step area and create a new Post Data to Server step.


Paste the URL that you copied from the Form Tool configuration screen into the box, as shown above.  Save the form.


Setup is now complete!  When this form is deployed, and a contact fills in the required info and submits, the WebEx Register Attendee connector will fire "one-off" and register the contact for the event.  The connector acts as it normally would, updating the contact or custom data object (depending on your setup choice) with the Join URL etc.


Some things to keep in mind...

  • As mentioned earlier, you do not need to Enable this connector.  It does not run on a scheduled basis, but rather is "triggered" by a form submit via the processing step.
  • You can set up any program step-based connector as a Form Tool.  So, in addition to event registration you can perform things like one-off String Manipulation or Concatenation, or Normalize contact data on the fly.
  • The connector is set up the same way as if it was being executed via a program step.  This means it can create custom objects, modify the contact record, or trigger an external event like sending  a Tweet when a form is submitted.r

Does any know how to set a dynamic content box within an email (not landing page) to collapse if the rule returns a null value, meaning there's no appropriate content to display in the box (no rule applies)?

Perhaps there is an app that can help with this.

Andrew Stanbridge

Posted by Andrew Stanbridge Feb 12, 2013

To date many of you are probably used to accessing Eloqua by going to While this login site still works, you might notice that after logging out, it takes you to I thought I would take a minute and explain what is all about. is the culmination of a lot of back end work being done to our authentication services. For example, In the Winter 13' release we introduced POD support. To date you might have had to switch to a different URL to access Eloqua depending on what POD you are on, POD2 customers use is POD agnostic so you never need to worry which POD or data center your production vs sandbox is on, you can always access Eloqua from


For the more technical people out there, can act as a central place to authenticate users via OAuth 2, SAML 2 SSO and a central place to query user identity information.


I hope you enjoyed this tidbit of info, update your Eloqua login bookmark!


I am loving Data Cards! Just finished creating a data card set that will store our various web activities which are happening on our website. Our website activity is synced with Salesforce in a custom object and now the data in that custom object is synced with data cards in Eloqua. This is going to allow our Marketing team to start building campaigns and automation around the activity on our website.


The down side right now is our Drupal to Salesforce sync is a manual process but we are partnering with a company which is going to help us turn this sync into an automated real time sync.


As we continue to grow and understand Eloqua (we are newbie’s just_ getting started) I am sure we will find better ways of doing these types of things, making better use of forms and landing pages but for now this Data Card sync is going to make a huge difference in how we do business and I think we will be taking more advantage of Data Cards moving forward.

It’s really tempting when creating your lead scoring model to include some super high buying indicator fields that automatically identify someone as a SIZZLING HOT lead.


An example:


“When are you looking to evaluate solutions for an XYZ initiative?”

  1. a) We are currently evaluating (Super sizzling, walking barefoot on coals hot)
  2. b) We plan to evaluate in 6-12 months (Arizona in July, put on sunscreen hot)
  3. c) 12-24 months (Keeping the bacon warm in the oven hot)
  4. d) More than 2 yrs (champagne chilling for midnight on New Years cold)
  5. e) We already have a solution (currently living in an igloo in Antarctica cold)
  6. f) We are never going to evaluate (our toes have fallen off due to frostbite cold)


Obviously at first glance, you’d want to weight this question really heavily and score really high on a) and b), right?

But what if only a small percentage of your prospects actually get a chance to answer that question? What about people who come into your database and enter lead scoring from a source that did not include the opportunity to provide an answer to it?


If you are weighting this question significantly higher than the other scoring criteria, there’s a large chance of most of your prospects aren’t getting a high enough score to become an MQL – because they won’t be getting a score on this question AT ALL.


Then you’re in a NOT SO HOT situation – with a sales team that’s wondering where all the leads are, and a marketing team frustrated that the lead scoring model they spent all that time on on isn’t working the way they had hoped.


So here is my advice – don’t use that field to score.


How can that work, you ask? How can we possibly IGNORE a question that is explicitly telling us who is and is not ready to talk to sales?


The answer is, you don’t IGNORE it. You just don’t include it in scoring model.


Here’s why.


The example question above looks a lot like a “Timeline” question that is usually part of BANT (Budget, Authority, Need, Timeline) qualification.


BANT questions are typically really intimate – getting straight at whether that person is ready to be talking actively with sales about solutions now, with no messing around. Often we see these questions being uncovered by the sales rep, in a one-to-one sales conversation after they receive and accept a lead from marketing.


But at the top of the funnel, where lead scoring usually occurs, most people aren’t ready to answer those questions yet. In fact, they may not even know the answers to those questions, because when people enter our scoring programs after downloading a piece of content, clicking on our emails, visiting our websites and landing pages, or dropping by our trade show booths, they are not even remotely qualified to be an MQL yet. We still have work to do to get them there, through our nurture programs and other marketing campaigns.


In short – your BANT criteria may not belong in your lead scoring.  That doesn’t mean these fields and questions cannot be used within automation to expedite qualification of some sort. In fact, they can be used to get the sizzling hot leads to sales FASTER if you don’t score on them, and if you configure your acceleration processes in the right way.


Making BANT Work for You Outside of Lead Scoring


Take someone who is not otherwise qualified from your lead scoring criteria. Maybe they have only dropped a business card in a trade show booth, but via your follow up emails they have filled out a form and answered this one BANT question with answer “a)” – so we know that they are currently evaluating and, hence, SUPER SIZZLING HOT.


By our lead scoring criteria, they aren’t quite close enough to be considered MQL – they haven’t interacted enough or maybe we don’t know enough about them to give them a high enough profile score yet. But because they’ve answered this question, we don’t want to wait for their lead score to catch up before we jump them in line and send them over to our sales team. Resting and waiting here is what makes lead scoring backfire!


Instead, you can put in place a separate process flow that bypasses the score-based lead routing and accelerates them DIRECT to MQL based on their response. (Technical Tip: you can do this using a Form Processing Step that sends that sends them to the CRM update program immediately and triggers lead assignment rules in CRM if they respond a certain way. You could also trigger a task to be assigned to the rep in CRM.)


So you would have two ways for someone to get to sales - 1) if they answer that BANT question right, regardless of what else they have done or who they are or what their lead score is; 2) They organically meet the criteria for the traditional scoring model.


At any point, a person can have the opportunity answer the BANT question during a campaign and jump the line to go straight to MQL – but you don’t have to goof around with your precious scoring model to make that happen.


Moral of the story? Seriously consider if putting BANT criteria in your top of funnel scoring model is going to deliver the results you are hoping for. If the answer is no, but you really want to incorporate BANT into your qualification process, find another way to automate it. Lead scoring and BANT – which are not necessarily the best of friends – can learn to cooperate in a way that maximizes opportunity for lead generation and maintains some sense of order in your scoring program.

A requirement we had from our business was to be able to create one global form that handles 80% to 90% of our form fills.  In our previous instance we utilize unique processing steps to route contacts into email groups/shared lists.  Now we pass the shared list ID from the landing page to our processing step. Here are quick instructions on how to find the ‘Shared List’ ID utilizing the Firebug tool with the Firefox browser.


1) Login to Eloqua -

2) Navigate to Contacts/Shared Library and left click on the 'Shared Library' icon.


3) Double left click on the 'Shared List' icon on the left hand navigation


4) Open up the Firebug application and make sure that your 'console' tab within Firebug is active.


5) Left click on the desired 'Shared List' within the available options.  You will see a string appear within the Firebug application 'GET https:///.....' (See below).


6) Mouse over the last entry within the Firebug tool and locate the word /list/...

7) The number after /list/ and before ? is the ID for the shared list.

8) Sample link:" style="font-size: 11pt; font-family: Calibri, sans-serif; line-height: 1.5em;" title="">


I hope this helps people finding shared list IDs within the E10 platform.  I saw another post on how to find this through the program builder but we do not allow our general users access to that tool.




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


Contact Data Normalizer Cloud App


This post will describe the Contact Data Normalizer Cloud App, and how to use it within your instance of Eloqua.


With the Contact Data Normalizer Cloud App, you can now normalize the data in a given field against a number of maintained master lookup tables.


In order to use the App, you must be registered at  When creating your account, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.


What is the difference between and


Contact Data Normalizer Cloud App Components


The Contact Data Normalizer Cloud App consists of the following Cloud Connector:


    • Contact Data Normalizer - allows you to  normalize the data in a given field against a number of maintained master lookup tables.


Components of the AppCloud


Installation and Configuration


To install the app in Eloqua, do the following. Log into and click on the Apps menu.



Click on Contact Data, then Data Normalizer, and the following screen will appear:



Click on Install Connector.  You'll then be shown the installation screen.


If you are an Eloqua administrator, you can click on Add Connector, and it will take you to the Cloud Connector Management area in your instance, with the install settings pre-populated.

You can also choose to do a Manual Install (note the settings above) and then go into the Cloud Connector Management are in your instance.  Enter the settings as shown below.





  Enter the following information:


To configure the App, do the following:

    • Add a step to your marketing automation program at any point you would like to run the contact data normalizer connector on a Contact record.
      • Note: The Cloud Connector will run on any Contact that flows into that step, and return the result(s) to another field within the Contact record.
      • Make sure that you have an account on
      • Drag a "Send to Cloud Connector" step onto the Canvas from the toolbar:


    • Double-click on the "Send to Cloud Connector" step, select Contact Data Normalizer from the list, and click on the configuration button.


    • When the Login screen appears, enter your credentials and click Log In.


    • Next the first setup screen for the App will appear.


    • The value for Step ID will automatically populate.  Select your Eloqua Credential, then click Go.


    • The Configuration page will then be displayed.



On the Configuration tab, enter the following information:

      • Description (optional):  Some text about this connector instance
      • First Normalization Set - Fifth Normalization Set: These are the maintained master lookup tables used to normalize your data.  You can select up to 5 sets, each to be used with the fields specified on the Mappings page.  Options are as follows:
        • Country to ISO 3 letter - Returns the 3 letter code for a given country
        • Country to ISO 2 letter - Returns the 2 letter code for a given country
        • Country to ISO Numeric - Returns the numeric code for a given country
        • Country to Internet domain - Finds the internet domain for a given country (for example, Canada would return .ca)
        • Title to Level - Returns a job Level for a given job Title.  See table below for some examples of normalized values:


        • Title to Role - Returns a job Role for a given job Title.  See table below for some examples of normalized values:


        • State (+ Country) to State - Returns the state for a given State and Country combination.
        • Country to World Region - Returns the World Region for a given country (NA, EMEA, APAC, LA)


    • Click Save Settings.


    • Next, click on the Mappings tab.


On the Mappings tab, choose the following:

      • Email Address:  The field on the Contact record containing the email address.
      • First Normalization Set - Fifth Normalization Set:  The contact data that you wish to normalize, based on the Normalization Sets chosen on the Configuration page.

        • Lookup Field: The contact field containing the data you wish to normalize.
        • Return Field: The contact field to write the normalized data back to.
      • Click Save Settings.


You are now ready to Test the connector to make sure all is set correctly.  Click on the Test tab.


Once your step is enabled and running, the Step Members testing tab will show you the counts of contacts in your step.


The Run Manually testing tab will allow you to perform a Dry Run or a Full Run of your step.


A Dry Run will simulate a run, but will not actually write the data back to Eloqua.  A Full Run will perform a run of your connector, actually updating Eloqua.


Use the Sample Data tab if you wish to test your setup on select contacts.


Enter their email addresses, one per line, and click Test Contacts. (these contacts must already exist in your instance).

       (Note: If you check the Full Run box, the data will be written to Eloqua, if left unchecked, it will simulate the connector and show you the results.)


To check the history of your step execution, click on the History tab.


Now that you have tested your step, it's time to enable it.  Click on the Credentials tab.



When you are ready to enable your step, click the Enable Step button. (Note: Remember to also enable your program in Eloqua)


As Contacts flow into the step, the app will evaluate the data in the chosen contact fields (Lookup Fields) against the chosen Normalization Sets, and write the normalized value back into the contact fields selected as Return Fields.

Have you ever wanted to enhance an email or campaign to see if you could increase performance but maybe didn't know where to get started? Or were worried that you didn't have the time or resources to take on a testing and tweaking endeavor? Lucky for you, Eloqua makes this easy with a few tools that are already available!


Email Deliverability Tests


View how your emails appear on multiple email clients all in one place or see how your email will be received by spam filters, with the click of a button! I feel these are one of the most overlooked and underused awesome tools available within Eloqua. You are limited to anywhere between 5-10 tests per month, but use them! They can be found within an individual email by going to the Gear Icon from the email > Test Content & Deliverability… > Deliverability Tab. Check the boxes of the desired tests (see below for options) and click Run Deliverability Test. I like to check the 'email me when the results are ready' checkbox so that I know when it’s ready, but you can access the results by returning back to this same screen, and clicking the Options drop down in the upper right hand corner. The test(s) take anywhere from 30 seconds to a few minutes to a few hours to complete (depending on how complex the email is, how many links, images are included, etc.).




Test Options

General Deliverability Test

  • This report shows you the deliverability performance of your email when sent to a wide variety of test email accounts that are hosted by different email service providers/domains (both business and consumer).
  • The regions covered in this test are: North America, Europe, APAC & Latin America.
Inbox Preview and Spam Content Check Test
  • This report shows you how your email will look in a number of different email clients and also lets you know how the content has performed when passed through several popular spam filters.
  • The report will be available for download, after a few hours of compilation, as two PDFs (one for the Inbox Previews and one for the Spam Check).


Once completed, you get to view this amazing PDF document that shows your email as it would appear on multiple mail servers! It even shows you where the typical fold is on the screen (the point at which a user must scroll down to see more). As you can see in the example below (which is one of the most common questions I hear – why doesn’t my email appear correctly in Outlook 2007/2010) I might want to make some changes, move around my call to action, and ensure that the text portion of my email is very user-friendly.




For more tips and tricks on Email Deliverability, view this Topliner’s post: The specified item was not found.


A/B Testing


This is, and always has been, one of my favorite practices, across whatever platform I’m working in. Whether you have a hunch that a different header will perform better, or you’re being told by your superiors to do something a certain way (but you have that gut feeling that that’s not right) A/B testing is almost always a sure fire way to find the correct route. You can do this easily within Eloqua as well. All new Eloqua installs come with a Best Practice program template built in: Setup > Program Builder > Program > BP - A/B Testing > BP – All Testing A/B Split. If you’re not quite ready to tackle Program Builder and are more comfortable in Campaign Canvas, here are two great articles on using Campaign Canvas for A/B testing: A/B Test Creation Using Segments and Campaigns (No Program Builder!)  and E10: How to Run A/B Email Testing on the Campaign Canvas.




Keep in mind that these programs (campaigns) are designed to test emails, but there’s no reason that you couldn’t also use this to test landing pages. Simply create copies of the email and set them up as you would using the instructions above, but switch out the landing pages that you’re linking to within the emails. Of course this would only work if you were sending the user to a landing page.


For a great list of items you should consider testing within emails or other marketing channels, check out this post on Topliners: A/B Testing Bible




Reporting is only useful if you're comparing your data to past data, goals, against budget, etc. Eloqua makes benchmarking and performance tracking easy within Eloqua Insight. A few key reports to keep your eye on regularly are:

  • Campaign Activity Performance Dashboard
  • Email Performance Dashboard
  • Email Analysis
  • Email Bounceback Overview


And of course reports related to separate assets you are using within the campaigns that you're sending (Forms, Landing Pages). For a complete list of reports available within E10 and their functionality, please view: The specified item was not found.


Best Practice Campaign Templates


We’ve taken away some of the work for you – take advantage of it! Within E10 are built-in best practice templates for a few different types of campaigns: Welcome, Simple Nurture, Re-Engagement, and Basic Event. These can be accessed by going to Campaigns > Create a Campaign > Eloqua Best Practices. You’ll even notice that when you click on each campaign template name, you’ll also see a link to a configuration guide.




And if that isn’t quite enough, check out this post for additional best practices around campaigns: The specified item was not found.


Right after publishing this post, I came across another great article on setting up your email and maximizing it's performance: How to: Improving Email Effectiveness with Simple HTML & Text Versions


One of the best things you can do as a marketer is improve your performance and success and these tools should give you the chance to do that!

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Progressive Profiling capabilities are now moved into the Oracle Eloqua Core Platform. Review this page for more info.

Please note: This article was edited by the talented Linda David.


This article will describe the individual pieces of the Progressive Profiling Cloud App, how to have it enabled for your Eloqua instance, and how to configure it. This document assumes that the reader is an E10 user, and is familiar with using landing pages.


It’s often very difficult to convince prospective buyers to spend any time filling out information in web forms, let alone lengthy complex web forms.  Add to that the resistance that can be seen when prospects are asked to fill out information they have already provided previously, and you have a recipe for poor conversion rates.  Luckily, there is a solution – progressive profiling.  The concept is simple, only ask for small amounts of information at a time, and never ask for the same information more than once.  Each time a buyer engages, you gain a little bit more insight into them, without ever putting a form in front of them that is more than a few fields in length. This builds the profile of your potential buyer which helps marketing for segmentation and scoring purposes and improves the quality of leads that sales receives.


As important as this approach is, it has historically been difficult to implement and requiring some complex javascript.  Now, with the Cloud Components in Eloqua 10’s HTML 5 interface, this technique can be done quickly, simply, and powerfully.  Let’s have a look at how it can be accomplished.


In order to use the Progressive Profiling App, you will need to be registered at


What is the difference between and


1. How to Install the Cloud App


The Progressive Profiling Cloud App is already available for use in E10, but may need to be enabled. See here for more information.


2. Let's Go! Add the Cloud Component on a Landing Page


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


First, start by dragging and dropping the progressive profiling component onto the design canvas for the landing page you’re creating.  You’ll see a sample image render, and you can double click it to begin editing the rules for your progressive profiling component.

step 2-1.jpg

With the editing interface popped open (you’ll need to have an account on to configure this, which are free to create), put in the credentials for your Eloqua instance, and click 'Go'.


A list of the forms in your instance is presented - select the form you want to build the progressive profiling rules for.  The component takes a master form with all the fields you would want on a contact (say 20 or 30 fields), and gradually presents just a few of those fields.  When you set up the master form in Eloqua, be sure of two things:


  • The fields are not required (or any progressive profiling forms that don’t have those fields will not work)
  • The form updates the contact record with the data submitted in the form, only if new value is not blank


With the form selected, click 'Save Settings' at the bottom of the screen.



3. What if We Have No Existing Profile? Handling the Unknowns


The Progressive Profiling Component automatically looks up a contact in Eloqua based on the cookie that is stored in their browser if that contact is known to Eloqua. However, there may be occasions where the visitor is not known to Eloqua - the "If contact is unknown" setting allows you to specify what action should be taken. There are two options available:

  • Show Lookup Button: This will show a single-field form that will ask the visitor to enter their email address so that the contact record can be located within Eloqua.
  • Show Form: This will show the set of fields defined in the first Progressive Profiling Rule (or up to the number of fields specified in 'Show a minimum number of fields').


If you select ‘Show Lookup Button’, there is additional configuration required:

  • Lookup Header Text: The text that’s visible above the email lookup field – this contains instructions for the visitor
  • Lookup Email Field Name: The label of the field to be used in the component (i.e. Please Enter Your Email Address)
  • Lookup Button Text: The text on the submit button.


When an unknown visitor visits the page, they will see the lookup form, can key in their email address, and click on “Find Me”.


This then (still entirely within the component) retrieves that Eloqua contact (if it exists) and displays the appropriate progressive / gated form.  This acts like the short form element in our original way of building a two-part progressive profile with “short form” and “long form”.

6-1-2012 5-22-24 PM.png

This, of course, can be fully configured with CSS to define the style.


4. Configure the Profiling Rules - What Visitors Will See


The next step is to configure the details of how you would like your progressive profiling to work and requires the configuration of the ‘Profiling Rules’. These are essentially building a series of “If the contact has a value in contact field A (or doesn't have a value), then present fields X, Y, Z” rules.  The rules are evaluated from top to bottom. When a rule criteria is met, only those fields in the rule are displayed on the form. If you choose to show a minimum number of fields, then more rules are evaluated (and more fields are shown) until the minimum number of fields is reached. You can reorder the rules, or add as many as you would like.


In order to do this, simply click on ‘Build Rules’ and another window pops up:

edit rules-top.jpg

Before walking through the rule configuration, there are a few things to highlight:

  • Show Minimum Fields: If, for example, you want at least 3 fields displayed, then check the box and enter '3'. If you have 5 rules with 1 field each, then the rules will be processed until three fields are shown. Otherwise, your visitor would be presented with one field per visit.
  • Identity field:  This ensures that a field used to identify the individual is submitted with the form data, if the visitor is known by your Eloqua database. This field is hidden and prepopulated on all rules if not otherwise present. Click 'Options' to select which field will serve as your identity field (Email Address is recommended).
  • 'CSS Styles' button: This allows you to set the style definitions for the Progressive Profiling form:

css fields.jpg

The first contact field that the component checks is set to ‘Email Address’, as this will identify if the contact exists in the Eloqua database. Click on "Add Rule" to add another contact field to evaluate. For each contact field selected, you can specify the criteria the contact field should meet - the most common rule is “data in this field Doesn't Exist”, in which case you will generally request that information.  However, you have a wide variety of other rules to look at including “Does Exist”, “Is In List (of values)”, and “Is Not In List”.

rule values.jpg

If you choose any of the List options (“in” or “not in”), you can then click the Edit List button to bring up an edit window for a list of values in the list to be considered.  You might use this, for example, to show certain fields if a person is known to be in certain industries, or from certain geographies.

edit list.jpg

When a rule is met, you can then specify what field(s) to display.  In the simplest case, this will be something like “if City does not exist, show City as a form field”, but can be whatever rules you need. When creating this set of fields to display, you can specify what type of field you'd like to show, how to show it, as well as whether it should be a mandatory field.

edit fields.jpg

The standard form field types are available, including Text, Select, Radio, Checkbox, and Hidden.

field types.jpg

The Edit button (pencil icon) opens a dialog box where you specify whether to pre-populate the field, and what contact field to pre-populate it from.

edit button.jpg

For the Field Types 'Select', 'Multi-Select', and 'Radio Buttons', you can choose from List Values you had previously created in the Cloud Component. When you create a new select list, you can input values OR import values from an existing select list in your Eloqua database. To create a new select list, click the 'New' button. A new browser window opens.

edit options-lists.jpg

First, enter a name for your new list, then click 'Save'. You can now click 'Show Eloqua Lists' to populate the drop-down with all select lists in your Eloqua database. Select the list, then click 'Import Values' to bring the values into the Cloud Component. Once the values are brought in, they can be modified, ie. you may want to remove some option values, then click 'Save' again.

create new list.jpg


5. What Happens if the Visitor Has All of the Data (the Field Display Rules are met)?


With all the rules set up, you then can specify what you want to have happen when a visitor to the page already has all the data that is being looked for.  If no rules are met, you can select from the following:

  • Show Content: Show a static piece of content - in which case you will be asked for the content (this can be HTML)
  • Redirect to URL: Redirect the visitor to a specific URL - in which case you will be asked for the URL
  • Submit Form Automatically: This will submit the form automatically and execute the form processing steps



6. Dynamic Form Data: Grabbing Data From Query Strings etc...


It is possible for the component to read values that are passed in via query string parameters from the  inbound link. To configure, click "Dynamic Fields".


This opens a screen where you can set a form field to a certain value based on the value in the query string parameter.  This allows you to alter values that are submitted into the Eloqua form based on the link that was clicked on, such as redirecting the visitor to a specific URL based on a doc value.


First, select the form field to be populated with the dynamic value, then indicate what the query string parameter will be.

new-edit dynamic fields.jpg

Using the page redirect example, you can use the same landing page (that contains the progressive profiling component) with an additional query string appended to the URL that will determine which page visitors are directed to after the form is submitted, ie. we have these three URLs:

You then simply configure the dynamic fields section to translate the values of 1, 2 or 3 to another URL so that this value is posted to a form field. All that you would need to now do is configure your Eloqua form processing step 'Redirect to Web Page' to use the form field ‘Redirect to URL’ to be able to send any submitters of the form through to these end locations as required.

new-edit value map.jpg

If you have a long list of values, you can prepare this in advance and upload to an Eloqua picklist, then use the picklist to populate the list of Input Values and Values (remember to click "Import Values" after you select the list). You can configure many dynamic fields, each with multiple values allowed to provide you with lots of flexibility on the outcomes available. Note that it is not necessary to have a form field in Eloqua for your query string parameter in order for this to work.


7. Finishing Things Off


There are a couple final pieces you are able to configure:

  • Set constant values for form fields using the ‘Static Form Data’ field, such as ‘Asset=123&Source=Progressive’. Ensure that your query string parameters match the html form field name on your form.
  • Set the submit button text.

step 7-1.jpg


8. Taking it For a Spin - Let's Test it


Following these same simple procedures, you can build as simple or as robust of a progressive profiling system you want.


With that set up, Save the component, return to the landing page Editor, and preview your page. You can see that the first time you visit, it does not know who you are, so it requests your email address.

6-1-2012 5-41-16 PM.png

If you type that in, and hit submit, it will send this to a form that updates your contact record and passes you back again to the same page (for example purposes).

6-1-2012 5-41-52 PM.png

Now, knowing your email address, it passes to the next rule in the chain and asks for your City (with a hidden, prepopulated field for email address).

6-1-2012 5-42-24 PM.png

Congrats - you're all done! Want to learn more? Take the Eloqua 10: Managing Social Media (Web-Based Training) and Best Practices: Managing Social Media Classes available in the Eloqua University (pass required).


Embedding the Progressive Profiling Component on non-Eloqua hosted pages


Your Progressive Profiling Component can now be embedded on an externally hosted page, ie. your corporate website, via an iframe. Click "Embed".


Set the dimensions for your Component, then copy the iframe code provided & paste onto the page you want it displayed on.



I came to realize recently that you cannot add 2 fields to a form that are using the same picklist. For example lead source most recent and lead source original (if using the same picklists).


Workaround: Use a custom picklist field and rename it for ease of use. You can then add the same picklist and save.

Otherwise you will receive an error.

Here are three key Eloqua Insight reports (Eloqua10) to help you answer questions such as:

  • Is my salesteam adopting Eloqua Engage? Who are they targeting?
  • Who on the team is sending the most emails? Templates versus their own? Who's getting the best engagement rates?
  • Which templates are the most used? Which get the best engagement rates?


In this article, you'll see screenshot examples of the information available in these reports. Click on the images below to see full-size versions.


NOTE: If your sales team is still using the Eloqua for Microsoft Outlook plug-in, these reports capture the same information for that tool. But you should definitely be considering an The specified item was not found. soon!


These sales email reports can be found in the folder "Sales Email Reports" under Email Metrics, which looks like the below:



Sales Email Opens and Website Visits

This report provides information about the recipients of your sales teams' emails: their contact information as well as if/when the email was opened and/or clicked and if the recipient unsubscribed or bounced. If an Engage template was sent, you'll see the name of that Email in the respective column.



Sales Email Template Usage

If your teams have built out a library of Engage templates, this report will show which are being used the most, and which are getting the best results -- this is great intel for managing your library.



Sales Email Overview

Who in your team is getting the most value from Engage? In this report, you'll see by Engage user who's sending the most emails and who's getting the best engagement. Highlight those users in your team meetings and gather their insight on what works best to share with other users.



These are the standard reports available to all Insight users. With the base Reporter license, you can remove columns or filter results; with the add-on Analyzer license, you can add further columns or even craft a custom report from the ground-up. We'd love to hear how you use the data from your Engage users to improve your marketing and sales efforts!

Salesforce seems to have removed Eloqua from its AppExchange after the Oracle purchase. I think I'm not the only one worried about the future of Eloqua and SFDC integration and in need of answers and re-assurance both from Eloqua and Salesforce.

Lead scoring strategies that succeed involve Marketing and Sales alignment.  The alignment doesn’t have to be perfect and it usually isn't.  But unilaterally developed lead scoring programs are doomed to fail without Sales adoption. 


When done poorly, lead scoring is just another data point in a field in Salesforce that doesn’t drive action.  Done well, lead scoring builds a bridge of collaboration between Sales and Marketing and leads to pipeline acceleration.   Marketing still needs to execute an effective campaign and nurture strategy to fill the funnel.  Lead scores are the exclamation point that leads to effective lead follow up action.


Lead scoring isn’t just about using a marketing automation platform to capture and calculate A1’s or C3’s or B2’s.  Lead scoring only succeeds with follow up action. These steps are the best ways to build a solid lead scoring program that Sales will support!

1. Agreed Upon Personas: Love them or loathe them, different personas usually require different scoring models are ranks.  Decision makers should be scored differently than an influencer or an end-user.  Some companies have multiple personas and scoring models uniquely suited for business units and product lines.  Understanding WHO leads to building a better scoring strategy and follow up action.


2. What the Heck is a Qualified Lead? Marketing and Sales need to agree on the stages of lead qualification.  What is a Marketing Qualified Lead? Define the lead score parameters and thresholds BEFORE pulling levers and pushing buttons in your marketing automation platform.


3. Profile Weighting:  Profile information is important building a lead score profile.  But it doesn’t tell the whole story. The traditional method of scoring on Budget, Authority, Need, and Timeframe (BANT) is difficult to capture in a reliable manner using marketing automation.  Not everyone openly and honestly provides budget information in an online form. Job titles can be inflated and difficult to score.  Need and Timeframe are easier to capture and score.  Work with Sales to identify the right profile information to capture and score.  Sales must validate and qualify the BANT criteria when initially working with a lead.  Marketing can only start building the profile.


4. Engagement Weighting – Identify the patterns of interest: How someone interacts with your company and content is powerful information which fills the score profile.  Where, how long and how often did they spend time with your content? What content did they consume? These scores are the secret sauce for a lead scoring program because they show levels of interest. 


5. Score What Matters. Ignore What Doesn't: Job seekers and competitors can spend a ton of time on sites and consuming content.  This behavior can lead to a high engagement scores and pull Sales away from leads they should focus on.  Use lead scoring programs to depreciate or suppress these scores altogether.  Sales will appreciate it!

6. Define Follow-Up Actions and a Service Level Agreement:  Follow up action is critical! Lead scoring will fail without Sales doing their part. Build follow up actions for each level of lead score. The follow up action can include the maximum time required for follow up and the recommended conversation. For example, a perfect lead with an A1 score may require follow up within 4 hours of reaching the CRM follow up queue.  The A1 conversation can steer toward activating a product demo.  On the other hand a C3 lead may require follow up within 48 hours and a personal email with links to an informational webinar. Sales must agree to the follow up action on each lead and enforce this with a service level agreement with Marketing. 

7. Review Lead Scoring with Sales: Success begins with reviewing the lead scoring model before it’s rolled out.  Sales managers can provide critical input to fine tuning a lead score model. This input leads to buy-in and enforcement on follow up actions.


8. Rollout, Test, Refine: When the lead scoring program is turned on, send leads to Sales with a bigger range of scores.  During the initial stage, some organizations may prefer a pilot rollout with a select Sales team to test scoring accuracy.  Sales should provide feedback and disposition tracking in the CRM system that shows lead scoring effectiveness. Fine tuning the filter can helps Marketing send better leads to Sales. The more consistent the follow up action, the better the lead scoring program!


Lead scoring takes work to build, refine and measure.  Marketing can drive the process but it only works with a strong partnership with Sales.

Filter Blog

By date: By tag: