Skip navigation
1 2 3 Previous Next

Do It

36 Posts authored by: chorenf

This was a tip from Tiziana Barrow:


USE CASE: A client wants to score on 140 countries. 



There is no current technical limit on the number of criteria within a model, rules within a criteria, or values within a rule. However you don't want the model to become too large to manage or takes too long to execute, but it would depend on the number, type, and complexity of the rules involved. 

It's more efficient to define 4 rules that cover 35 countries each than to define 140 rules that cover 1 country each, but both should technically be possible.  It's also more efficient to use "in set" or "equal to" operators instead of "match" or "contains", i.e. match on the exact country name or country code. 


Happy scoring!



This post by Marilyn Cox Spotlight on Success: 5 Reasons I Love the Analyzer License inspired me to write this quick post which may be a common scenario for you. You may have a sales team that is clamoring for leads from a tradeshow or an ongoing campaign. How do you send these on via a daily scheduled report if these contacts are in a Shared List? This solution is thanks to Owen Manning:


You'll need to customize a report to do this. I started by creating a prompt for "Contact List" (aka Shared List in Insight-speak). I then customized the Contact List report and added this prompt as a filter. As long as the fields you want to report out are part of the OOTB (out of the box) fields on the report, the result should do the trick.


Of course to create a customized report, you will need the Eloqua Analyzer license for Insight. The other thing to keep in mind is that newly added contacts to the Shared Lists take about 20 or so minutes to be added to Insight reporting. Happy report creating!



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.



This document provides some context for the Lead Process Flow template (login required and access to Eloqua Insiders). The typical funnel stages include: Suspect, Prospect, Marketing Qualified Lead (MQL), Sales Accepted Lead (SAL), Sales Qualified Opportunity (SQO) and Customer. As a lead moves through these stages of the buying process there are some recommendations on how to configure your CRM for the best results. This document outlines these best practices. Feel free to add your comments.




Suspect to Prospect

The conversion of a Suspect to Prospect (sometimes called Inquiry) occurs when a suspect raises their hand  and responds to a campaign. You can setup a rule in Eloqua to adjust the funnel stage based on certain types of activity. As a best practice, not all Prospects should be passed to the CRM unless they have reached the MQL status. That said, many organizations will send over these leads to their CRM and use Lead Scoring as a way of prioritizing which leads should be worked on first. It's important to differentiate a lead in the CRM either by using a funnel stage field or by stamping a lead as an MQL.


Prospect to Marketing Qualified Lead (MQL)

A Prospect becomes an MQL typically after it matches a certain lead scoring criteria that has been agreed upon by marketing and sales. At times, leads at this stage may be passed to a tele-qualification team for further qualification before being passed on to sales. Once leads reach this threshold within Eloqua they should be passed to the CRM and have their funnel stage field changed to MQL. This is an automatic rule that can be setup in Eloqua or your CRM. Some organizations also date stamp fields in the CRM to date stamp a lead when it reaches MQL status. This helps track how long a lead has been in this status.

11-19-2012 5-39-06 PM.png


MQL to Sales Accepted Lead (SAL)

Converting an MQL to an SAL occurs as sales "work" the leads that are passed on to them. Again, at this stage, it may be a telequalification team that is doing this follow up. Sales verbally (through a phone conversation) determines the validity of the lead and their desire to move forward in the buying cycle. Sales will make a a decision - either convert to an SAL or reject the lead.  This is NOT an automatic action. A simple change by the rep in the lead status field from "new" to "working" can indicate that a lead now has an SAL status. Many organizations will convert a lead to a contact and have an opportunity created with a stage of "Lead Accepted (SAL)" with a pipeline / forecast of 0%. A contact should also be added to the opportunity as well. A lead that has been given a status of "rejected" (or something similar) should be assigned a reason code (such as remarket, no budget, not ready, not qualified, etc.) and should be passed back to marketing for additional nurturing based on the reason code. In the example below, the "Lead Disposition" field contains the rejected reason code. This may mean Eloqua looks for a certain lead status and reason code and automatically pulls the contact into a lead nurturing campaign.


11-19-2012 5-49-33 PM.png


SAL to Sales Qualified Opportunity (SQO)

When sales makes a decision to move the lead forward, it typically involves changing the opportunity stage and/or assigning a pipeline / forecast to this individual. This is NOT an automatic action and something that must be done by a sales person. Sales should define the different opportunity stages that compose the sales qualified opportunity stage (for example: Discovery/Needs Analysis, Qualification/Capability Discussion). Leads that stall at this stage may be assigned a "lost" opportunity status with a specific reason code.

11-19-2012 5-41-03 PM.png

Please note: Leads will fall out of the funnel at any stage (not move forward). Marketing must create multiple re-engagement campaigns depending on the reason a lead fell out of a stage. The concept "no lead left behind" must be kept in mind or you have left yourself open to a competitor winning this business.


SQO to Closed Won

This occurs when a lead becomes a customer and/or a customer purchases another product/service. This will be reflected on the opportunity.


Additional resources:

This post will hopefully help you as you try and put the pieces of Eloqua together to create a simple campaign that will send an email and direct them to an Eloqua hosted landing page and form. It also assumes that you would want the form submission to be passed on to your CRM.



  • You've taken E10 fundamentals and the Landing pages course. This is not a training post.
  • You have your CRM integration all setup
  • You already created your Campaign Assets and tested them: Segment, Email, Landing Page, Form


Steps to Configure Your Campaign


  1. Create the Campaign in the Canvas. Drop the basic pieces on to the Campaign. It might look something like this (you can make it more complex based on your needs):
    10-17-2012 6-38-24 PM.png
    We added the Form and Landing Page on the Canvas to ensure that we are able to see the number of forms submitted (leads) and conversion rate as well as the email response metrics on the Campaign Analysis report.

  2. Configure the Campaign Steps. Add in the Segment, Email (ensure that there is a link to the landing page that you dropped on the Canvas), the form and the landing page (it's assumed you dropped the form on the Canvas onto the landing page). It will look something like this:
    10-17-2012 6-46-42 PM.png
  3. Configure the Form to Pass Data to the CRM. Before you activate the Campaign in Eloqua, you're going to want to ensure that your having the form submits pass to the CRM as well as appending the record to a Campaign in your CRM.
    a. Add a hidden field that you can add the CRM Campaign ID to. You can either enter it as a static field per below (copy the ID from and paste it as an example) or you can capture the data from a query string as outlined here: How to Capture Referring Sources to Landing Pages and in Forms using Query Strings10-19-2012 5-58-42 PM.png
    b. Make sure that Campaign ID form field is being saved to the Contact record:
    10-19-2012 6-03-07 PM.png
    c. Add in a form processing step to push the form data to the Eloqua/CRM integration program. It should look like something like below
    10-19-2012 6-05-44 PM.png

  4. Check your reports. I recommend the Campaign Analysis Report as it's a rolled up report of the emails and form conversions.
    10-19-2012 6-11-43 PM.png


That's it. If you're using Eloqua's Closed Loop Reporting Module, step 4 would change as Campaigns in the CRM would be completed automatically. Another reason to get that setup!


Any other tips you recommend?

I was asked if you could report on the different lead stages that a contact resides in within Eloqua as well as Segment off of this data. You can definitely do this and the recommended path is using Eloqua's Revenue Suite module. You may also be able to do some more simple funnel tracking using Contact fields and Segments within Eloqua. This is something I've come up with fairly quickly and should only be used as a guide and not a comprehensive solution. There are drawbacks to this approach. As you're using Contact fields, you don't have a historical analysis on the number of qualified leads vs sales accepted leads as an example. The data you're reporting on would be at that exact time unless you are exporting out the data from Eloqua to another system. Eloqua's Revenue Suite keeps all of the historical data for more accurate funnel progression reporting. All that said, here is a possible approach.


1. Define your sales/marketing funnel. This post uses the following funnel stage definitions: Integrated Sales and Marketing Funnel Stage Definition. It's assumed that you have also rolled out lead scoring to determine what is and isn't a qualified lead.

2. Create fields in Eloqua. Create a contact field called "Lead Stage", and a date field for Qualified Lead. It's up to you if you want to create date fields for the other stages. This will allow you to date stamp contacts when they have hit a certain stage in your funnel.

3. CRM integration on Opportunity information. It's recommended that you mirror the Opportunity stages within your CRM to contact records associated with Accounts on your CRM and pass that stage data back to Eloqua. Alternatively, you can pass CRM Opportunity information back to Eloqua assuming that you have associated a Contact Role to the Opportunity. The end goal is to be able to check if a contact is associated to an Opportunity in the CRM.

4. Create Segments/Filters in Eloqua for each stage (explained below)

5. Build the program


This assumes that you have Program Builder and Eloqua Data Tools experience. It's also recommended to take an Eloqua Admin course from Eloqua University.


This is an overview of a completed program:

9-24-2012 6-23-02 PM.png


Program Breakdown:

  • 00 Start - create a program feeder that feeds all contacts into the program on a daily basis
  • Has Opportunity Stage - Create a Shared Filter to check if the contact is associated to an Opportunity. For this to work you are either passing Opportunity data into Eloqua or someone is manually updating Eloqua contact records. I explained above the different options here. You can also add onto this path if you want to split out the specific Opportunity stage.
  • Is a Qualified Lead - Typically, this is dependent on the lead score of the contact in Eloqua. In this example, Create a Shared Filter to check the lead score of the contact.
    • If the lead score is between A1 and C2 (as an example), send the contact to the Update Rule and update the Lead Stage field you created as "Qualified Lead" or however you want to call leads at this stage. You may also want to date stamp the qualified lead record so you can keep track as to when it became a qualified lead.
    • The next step may be to send a quick notification to sales so that they contact the qualified lead. See the following post on a few approaches: Sending Notifications to Sales From Program Builder
  • Is a Prospect - Check to see if the contact has any activity. Create a Shared Filter to check if the contact has submitted any forms, visited the website and/or responded to any emails. Some organizations use tighter criteria (filled out specific forms).
    • If the criteria are met, update the lead stage field with "Prospect" lead stage.
    • If the criteria aren't met, update the lead stage to "Suspect"


That's really it. You can use Segments to report on this data and in the near future, you can use Insight to create some highly customized dashboards. As an added step, you would probably want to feed all "Qualified Leads" to the CRM integration program so this data gets updated in your CRM. funn

I went back to my archives and found that I created a very quick video on how to send notifications to sales reps via program builder. See:

This isn’t a training video (sorry that I'm almost whispering) and if you need help, let Support know.


Here is a sample program using this:

9-24-2012 3-58-00 PM.png

  1. You first need to create all sales reps as users in Eloqua (if they’re not already).
  2. Create the Ownership rules in Program Builder.
  3. Create the Program – See the video
  4. Test it out by having a notification sent to yourself


The main drawback with these notifications in comparison to the form notifications is that you can’t really customize the email very much. To get over this hurdle, many clients are now using the form submission cloud connector which can take advantage of using the "send notification" form processing step. Another approach for SFDC users is to create a SFDC Task in Eloqua that will be sent to the sales rep. This is useful when you have a "create unique leads only" process.

Eloqua has recently released some powerful new tools that will allow you to personalize your emails using data from Custom Data Objects. For example, if you want to send an email that includes their subscription date or the name of the product that was purchased, you can now create email merge fields of these Data Card fields for your emails. For more information check out the following:


Personalize Content Using Custom Data Objects - Video

Personalize Content Using Custom Data Objects - FAQ


This is a major enhancement but because a Custom Data Object can have multiple datacards for the same contact, only values from the last modified Data Card that is linked to the contact will be used for the field merge. Here is an example where this could be a challenge. If you capture a product such as training courses in one Datacard Set, a contact can have purchased multiple training courses. If you want to send an email that indicate that a contact had purchased a certain training course that has a certain subscription ID (say it's the ID needed to register online), how would you populate this ID into an email when it's not the last modified Data Card? This is where the Data Card Evaluator Cloud Component can help you. You can use it to write a value from a Data Card to the Eloqua Contact Record based on the criteria you choose.


  1. If you are new to cloud components you will need to have an Eloqua user with API access and register at
  2. Install the DataCard Evaluator Cloud Connector - see: Data Card Evaluator | Eloqua AppCloud
  3. Make sure you identify the Contact Field that you want to write data to from the Data Card. If you need to, create a new Contact Field.
  4. Create a Campaign (something like this):

9-21-2012 12-36-23 PM.png

4. Configure the Cloud Connector Step

In this scenario I'm going to write the Subscription ID of a certain Data Card to a Contact record (I've chosen to write this to the PromoID contact record) if the Data Card has a certain Product Name.

Step 1 - choose the option below "Field A where Field B = X". This means that it will write data to a contact record from Field A if criteria from Field B is met. We're assuming you have a Data Card Set already with some data you want to evaluate.

9-21-2012 12-22-25 PM.png

Step 2 - In the next step, we defined the Data Card field to evaluate (Field A = Product), the Data Card field data that we want to write to the contact (Field B = Subscription ID) and the Contact field we want to write the data to (PromoID). If Field A equals "Eloqua Training 101" the data will be written to the Contact Field:

9-21-2012 12-26-18 PM.png

That's really it. Run a test to see how it works.


5. Create your email and add a field merge (using a Contact field) to the email with the data that you pushed over from the Data Card to the Contact record.

6. Test and launch your Campaign


The Data Card Evaluator can be used for many purposes - this is just one of them. It will give you an idea of how you can personalize your emails with Data Card information. cl

With the new lead scoring module in E10, you'll need to map a different lead scoring field in Eloqua to your CRM field.

It depends on the CRM you integrate with but you'll want to do this for the Update Contact, Update Lead and Create Lead calls.

Go to: Setup > Integration > Outbound (tab) > External Calls (tab) and update each call separately.


Choose the Default Scoring Model field and drag it to the Lead Rating field (or whatever you have called it in your CRM). That's it.

8-31-2012 4-40-26 PM.png

This is a non-official post that may or may not work. I've been reviewing some old folders on my laptop and thought this material may be helpful based on some recent posts I've seen. If it doesn't work, post comments and let's work as a community to figure this out. With all that said, here we go!


The following post explains how Eloqua users can have content dynamically change on their event landing pages depending on whether or not the event is full. For example, if an event is full, you may want to have a message that lets web visitors know this right away (rather then sending them an email which Eloqua can be configured to do very easily).


Before starting this process, ensure that you have the necessary training from EloquaU and have access to the Events Module. This assumes that you have an advanced knowledge of Eloqua forms, landing pages, JavaScript, web data lookups and web design.


  1. Create an event using the Events Module - You need at least one session. Be sure to set the max number of registrants for the event.
  2. Create an Eloqua form.
  3. Add the following processing step (for events): Update Event Registration. Select the Event you created in Step 1
  4. Add the form to an Eloqua hosted landing page or to a web page that has Eloqua tracking scripts on it
  5. In order to setup a condition that will allow you to display different content if the event is full, you need to create a data card data lookup. Setup > Website > Web Data Lookup
  6. Create a new Data Look up. Make sure you select “Data Card Sets”. Select "Data Cards" from the Data Lookup Type drop down and the name of your event from the Data Card Set drop down.
  7. Once it's created, in the top right of the screen, go to Data Lookup Options > Get Data Lookup Scripts.
  8. Take the script on the lower half of the page and paste it on the web page or Eloqua hosted page (you'll need to use a Cloud Component in E10 for this). If possible, ensure the scripts are placed under the Eloqua tracking scripts.
    8-30-2012 6-47-05 PM.png
  9. You now need to customize the scripts so the Lookup will be associated with the appropriate Datacard Set (event). Within the <DataCardSet> tags, enter in the ID of the Datacard Set. You can find the ID from the scripts at the top of the page:
    8-30-2012 6-48-51 PM.png
  10. Just add in the ID so it would look like this (you can just remove the “Enter__here” between the “GroupByFieldValue” tags:
    var elqDLLookup = '<DataCardSet>48</DataCardSet><GroupByFieldValue> </GroupByFieldValue>';

    An important item to note is that one Lookup can be used for multiple Datacard sets (events). This is what it would look like: <DataCardSet>11,14,15,16</DataCardSet>

  11. Now you need to add the script that will change the content based on whether the event is full. Below is an example of the script that was added for a sample event (the code doesn't work). It displays alternative text if the event is sold out based on the limit you set in the event. For your event, ensure that you substitute the Datacard Set ID (it’s 48 below) with the correct ID. This was added in from the top section of the page.

<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript'>

if (GetElqContentPersonalizationValue('IsCourseFull48') == 'False')


  document.write('<p><b>Wednesday, July 11, 2017<br> Steve Miller Band</b> (Main Stage)<br> <b>Dog Power </b>(Rogers Stage)</p>'); }



  document.write('<b><span style="font-size: 11pt;">These tickets are sold out. <br> <a href=""><u>Select an alternate date</u><img src="" border="0" hspace="5"></a></b></span><br>  <br><br>');




In a normal situation, the page will display:

Thursday, July 11, 2017

Steve Miller Band (Main Stage)

Dog Power (Rogers Stage)


If the event is full, the text will be substituted with:


These tickets are sold out.

Select an alternate date


EXTRA: Using JavaScript, you can get even further complicated. For example, when the page loads, you can check if the event is full and disable the form fields. Here is another code sample of a multi-city event:



<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript'><!--//



window.onload = initPage;

function initPage(){


  if (GetElqContentPersonalizationValue('IsCourseFull11') == 'True')


  document.forms["Event_Registration_TEST"].elements["AppeonPowerBuilder_flag"].disabled = true;

  document.forms["Event_Registration_TEST"].elements["AppeonPowerBuilder_flag"].checked = false;



  if (GetElqContentPersonalizationValue('IsCourseFull14') == 'True')


  document.forms["Event_Registration_TEST"].elements["PocketPowerBuilder_flag"].disabled = true;

  document.forms["Event_Registration_TEST"].elements["PocketPowerBuilder_flag"].checked = false;



  if (GetElqContentPersonalizationValue('IsCourseFull16') == 'True')



  document.forms["Event_Registration_TEST"].elements["ASE_flag"].disabled = true;

  document.forms["Event_Registration_TEST"].elements["ASE_flag"].checked = false;



  if (GetElqContentPersonalizationValue('IsCourseFull15') == 'True')


  document.forms["Event_Registration_TEST"].elements["RepConnector_flag"].disabled = true;

  document.forms["Event_Registration_TEST"].elements["RepConnector_flag"].checked = false;





There is a simple feature in Eloqua that allows you to take an existing landing page that contains a form and have a form automatically created in Eloqua with all of the proper HTML names. For example, say you're looking to take the existing Contact Us page on your site ( and have it integrate with Eloqua, do the following:


1. Open Eloqua and go to Assets > Form. Choose the option highlighted below:

7-31-2012 9-13-51 AM.png

2. Insert the URL

7-31-2012 9-20-58 AM.png

3. Create your form (choose the fields you want to create in Eloqua)

4. Update your page with the proper form code as instructed and you're done


Remember - it's very important to integrate your web forms with Eloqua to ensure that Eloqua is capturing the digital body language of your prospects and customers. This feature helps marketers and the web team work together more efficiently and makes integrating existing web forms to Eloqua a snap

There are times that you'll want to automate the process of importing data into Eloqua from sources other then standard CRMs such as SFDC or MS CRM. For example, you may have a customer database or data from your product that you want to import into Eloqua via an SFTP file. In this case, you would have your IT team setup a schedule so that the data would be posted to a secure site in a .csv file format and you would tell Eloqua how and when you wanted to import that data into the Contact table in Eloqua. All of this is outlined in the article "Eloqua 10 Data Export and Import" which is located in Eloqua's Customer Central (click in the "?" symbol in the top right hand corner when you login to Eloqua.


One area not covered is automating the import process of different data sources into Custom Data Objects in Eloqua10. I wanted to provide a brief overview of that process if you wanted to try this out. If you were trying to understand why you want to use a Custom Data Object, check out: Best Practice – Custom Data Object Records (Data Cards) - Definition and Recommendations for Usage

Here is an outline of the steps involved in setting up the import process (creating an Auto-Synch):


  1. Create the Data Source. Setup > Integration > Inbound (tab) > Create Data Sources (drop down) > Create Data Sources. Choose "Remote File Over SFTP" as the "Transfer Type", select "Data Cards" as the priority and check off the "Can be scheduled for Automatic Execution"
  2. Create the Custom Object. Contacts > Custom Objects > Events (Drop Down) > New Custom Data Object
  3. Configure the automatic upload process. Go to the Custom Object you created in Step 2. Data Card Set > Upload Data Cards. Complete the wizard. Make sure you select the right mapping and you choose a certain unique identifier. You will need the SFTP info so that Eloqua can pull in your data.


This wasn't meant to provide the exact step by step but to at least outline the general process. Let our Support team know if you have additional questions.


On a side note, there is a Cloud Connector called the Data Card Evaluator which will allow you to pull data from Data Cards into the Contact record. This is helpful if you want to send personalized emails that contain data from a Contact's associated data cards.

I came across a form that was created where the validation on the country field didn't work. You need to ensure that the Default value in the Field settings is blank for your picklist (select list). Go to Setup > Fields & Views and ensure that you set this up correctly.


6-25-2012 3-32-11 PM.png

This is a quick post to describe the different numbers you may see on a Campaign in the Campaign Canvas. Hope this helps.


  1. Segment Members - the number you see is the number that the Segment is currently returning. It's not the number of the total contacts added to the Campaign. Because a Segment can be dynamic (Criteria can change, new people added to your database etc...), this number can also change. It will change if you go into the Segment and view the number of Contacts that the Segment returns.

  2. Email - This number tells you the number of contacts that have been excluded from getting the email. Contacts may be excluded if they have unsubscribed, hard bounced or received the email previously (based on how you have configured this step).If you happen to delete a Contact that was excluded from receiving an email, that Contact will still be represented as part of this number.

  3. Wait Step - This tells you how many people are waiting in this step. As outlined by Mike Garcia, you can add a wait step at the end of a Campaign to visually see the total number of contacts that have flowed through a Campaign.

6-25-2012 11-02-09 AM.png


Other useful discussions:

A recent Forrester study indicated that only 8% of the email recipients surveyed agreed that the email they they receive is relevant. In the same survey, 77% of these same email recipients indicated that they want to control the type of email that they receive.

What does this mean to you as a marketer? It means that if you want email to be a successful marketing channel the days of “spray and pray” are over. You need to focus on sending relevant, personalized  communication to your opted-in database. Subscription management allows email recipients to establish a respectful and trustworthy relationship with you. This can decrease global unsubscribes, improve communication effectiveness and increase customer loyalty. The overall benefits lead to improved overall campaign results and ultimately increased revenue for the company as email should be part of your ongoing lead generation and retention efforts.

Keep these items in mind when thinking about building an email subscription / preference center:

  • Just having a global opt-out is too restrictive and may result in a higher opt-out rate
  • Email recipients want increased flexibility and control into what communications they want to receive
  • Allowing more granular subscription options to email recipients will allow you to better segment your communication resulting in higher response rates

Recommended Eloqua Education Course(s) (available in EloquaU):

  • Revenue Lifecycle: Contact Management Essentials


Related Articles:

Filter Blog

By date: By tag: