Skip navigation

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


Box Cloud App


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


With the Box Cloud App, you can now share files stored in your Box account on an E10 landing page.  You can choose to either display a link to your file, embed an image, or display the Box file previewer right on your page.


In order to use the Box  App, you will need to have a valid Box account, and must be registered at


What is the difference between and


Box Cloud App Components


The Box Cloud App consists of the following Cloud Component:

  • Box File Share - allows you to embed an image, document link, or document previewer into an E10 landing page.


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


How to Install the Cloud App


The Box Cloud App is already available for use in E10, but may need to be enabled.


See here for more information.


Using the Component on a Landing Page


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


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



Drag and Drop the Box File Share component onto the landing page:



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



Enter your credentials and log in.  The configuration screen for the Box File Share will then be displayed:



In order to access your Box files, you will need to grant the component access to your account.  To do this, click "Authorize Account".


The following screen will then appear:


Enter your Box credentials and click "Log In".

(NOTE: If you are using a Single Sign On (SSO) service such as Okta, enter only your Email and leave the password blank)


Once successful, a window will display saying "Thank you. Close this window to continue".  Close the window, you've now granted access to your files!


     Next, select the file you would like to share on the page.  Click on the Select File button.


     The app will search your Box account and display the results.


     Your Box account contents will be displayed as a set of folders and files.  Click on a folder to see the files within it, or click on a file to select it.  You can also page through results by clicking on the numbers below the file list.


     Once you've selected your file, the app will check your Box account to see if the file is currently shared.  If the file is not yet shared, you will be shown the following:


Since the app required you to share the file before displaying in on the landing page, you have a couple options.  You can choose to go to your Box account and create the share there, or the app can create it for you.  If you choose to do this through your Box  account, you simply create the share manually, then come back to the app and click Save Settings again.  The warning will then disappear.  If you choose to have the app create it for you, simply select a share type (Open, Company, or Collaborators) and click  Share.  If the share is created successfully, you will see the following:


     Your file is now shared.  The shared file will show in the File to Share field.


    You're now ready to select your Share Type.


     You will be presented with three options for sharing.  These include:

    • Previewer - Embed the Box previewer directly in your page.
    • Image Embed - Display an image from your Box account on your page.
    • Link to File - Provide a link to a file in your page.


     To embed an image from your Box account, choose Image Embed.


     Click on Save Settings and close the Configuration screen.


     Now, render the landing page, and you will see your Image Embed on the page where you placed it.


     If you would like to embed a link to a file in your landing page, select Link to File.



     For a "Link to File", you can use either the default icon, or a custom icon of your choosing.


     To select a custom icon, select "Custom" from the "Image to display as link" dropdown, and enter the URL to the image.


     Now, render the landing page, and you will see your file link on the page where you placed it.


     The third option is embedding the file previewer on your page.  Select Previewer from the option list.  The following additional settings will appear.


     In the Previewer Settings area, you can use the following to customize the previewer for display on your page.


    • Permissions - Choose to either show or hide the Download, Share, or Print buttons.
    • Dimensions - Set the size of the previewer (Note: make sure that the component on the landing page is at least the dimensions that you set here to allow all of your content to display).


     When you have the settings the way you wish, render the landing page.  You will see the previewer displayed on the page.


The questions has come up more than once recently, what are some best practices and methods for handling inactive or soft bounceback contacts in a database?


Please allow me to explain...


The best place to start is by creating a segment and populating it with filter criteria such as:


  • Has not been sent an email within the last X time (perhaps 1 year, but it can vary) AND
  • Has not submitted a form within the last X time AND
  • Has not opened an email within last X time AND
  • Has not clicked an email within last X time AND
  • etc...


This should create a segment that finds all contacts in the database that are inactive or not interacting with your marketing emails.


This of course can vary, so you may want to find people who have NOT been sent an email in the last 3 months AND who have NOT clicked on an email in the last 6 months. That would find people who have recently been marketed to, but have had no interaction for a longer period. All these criteria can be tuned and refined according to your best judgment taking into consideration the frequency of your marketing emails, business preferences, and so forth.


If you scroll through the list of filter criteria on the right hand side in the segment you will notice there are a significant number of ‘Not’ criteria that can work to find inactive or non-responsive contacts:

12-29-2011 5-14-47 PM.png

There are also several other options not captured not captured here.


From there, you can add other criteria such as:


  • Marked as hardbounceback OR
  • Marked as Soft bounceback


These two are new features introduced in our recent R4 release.


There are also other criteria such as “unsubscribed from groups” which could allow you to locate contacts who may also be unsubscribed from key marketing email groups and would allow you to remove people who have opted-out of your highest value content.

12-29-2011 5-18-40 PM.png

In the end, you will have a segment which has numerous grouped items combining different logical operators. Here is a quick example:

12-29-2011 5-34-57 PM.png

Recall that the AND criteria will only catch people who have not done X AND also not done Y – if a contact has done X, but not done Y, that contact will not be included in the filter as they must meet both criteria for the AND condition. As such, the logic that is used is almost as important as the filter criteria itself. Notice above that the ANDs are grouped together to represent marketing inactivity, and that the ORs are used as separate options based on status (not subscribed to ‘Event Invitations’ OR ‘marked as softbounceback within the last 6 months’).


Once the segment is created to your satisfaction, you could then load it into a re-engagement campaign in the campaign canvas as the top segment step. This campaign would send an email or two with appropriate wait steps to control timing. As well, there would be branching decision rules to determined if contacts took any actions on the specific re-engagement emails. If not, you would then send these inactive contacts to a campaign step that would populate a shared list. At this point, you will need to export this shared list and then conduct a contact upload with the upload purpose set to “Delete contacts.” (If your purpose is to remove inactive contacts from your database, that is.)


Much of this process can be reduced or expanded depending on your individual activity criteria and business objectives, but my hope is that this brief guide will point you in right direction to identify inactive contacts, to attempt to re-engage them, and then ultimately to delete those who are unresponsive from your database.


Please feel free to add comments or questions below!


- Ian

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

Click on the Gear Icon and Select "Settings":


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



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


Then, click "Save"

Can you please fix this color combo?



It's hurting my eyes and my delicate designer sensibility, not to mention that I'm pretty sure Red/Green colorblind people just see that as a grey blob.


Reversed out white text would work.


Thanks in advance. I'll go back to lurking now.

When you first open the Campaign or Email Dashboard in Insight, the metrics for your aggregate activities is displayed. These are very useful benchmarks, but what if you want to drill down in the reporting? You can! You might have noticed the drop-down menus at the bottom of the dashboard here:



In this article, we’ll show you how to configure and use these selectors to segment your dashboards.


First, meet with your campaign stakeholders to determine the categories you want to use for your drill-down reports. Defaults are available in Eloqua for Region, Product, and Campaign Type, but you may want to use your own options.


With this list, navigate to Setup>Campaign Fields (requires Customer Administrator permissions). You’ll see the three default fields:


You’ll need to connect the default Select Lists for each (they have the same name as the Fields), or create your custom Select Lists. When done, your configuration might look like this, for example:


You’ll need to wait about 15 minutes or so before the next step. Navigate to your Campaign, and go to the Settings menu like so:


Toward the bottom of the Settings dialog, you’ll see those same Campaign Field options – pick the one that’s most applicable, like so:


You’ll need to wait a little while again for the updates to populate in your dashboards. Once completed, in your dashboards, you can check the appropriate Campaign Fields and quickly segment your reports like this:


Once selected, all of the reports in that dashboard will only show results for those Campaigns flagged with that Field. Very cool!

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

Webex App


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

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

What is the difference between and



WebEx App Components

The WebEx App is made up of the following Connectors:

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

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

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


How to Install an App


To install the Webex App, visit this page:

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

install app.png


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

add connector.png


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

cloud connector management.png


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



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

all ready exists.png


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

successfully installed.png

Repeat this for any other Connector you would like to install


Installing a Cloud Feeder

Cloud Feeders have a different installation then Cloud Connectors.

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

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


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


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


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


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


To install the WebEx feeder, go to the following URL:

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

cloud login.png

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

You will be brought to the following screen:



Input the information collected from WebEx earlier.

Select the contact group created earlier.

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



Using the Connectors in Program Builder


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



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

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

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

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


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


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

cloud login.png

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


They are as follows:



Register Attendee

Unregister Attendee

Query Attendee







WebEx User Name




From WebEx

WebEx Password




From WebEx

WebEx Session Type




From WebEx

WebEx Session ID




From WebEx

WebEx Organization Name




From WebEx

Source of WebEx ID




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

Send Email invitations




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

Store Join Meeting URL in




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

Store Event Attendance Data in




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





Register Attendee

Unregister Attendee

Query Attendee

Email Address




First Name




Last Name












Address 1




Address 2
























Join Meeting URL




Minutes Attended




Start Time









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


The Program     

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




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

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

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

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

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


CloudComponent – A CloudComponent extends the functionality of Eloqua Landing Pages in E10. It pulls content or logic from 3rd parties, and displays it on a landing page, such as Twitter Feeds or Facebook Single Sign On
– Apps are designed to run outside of the Eloqua application. Some apps, such as the Name Analyzer or the Math Functions are designed by our Eloqua Labs. These apps are hosted at It requires a separate login to Eloqua, but it is free to access.

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


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

On December 11, 2011, the latest release of Eloqua hit production.  Along with this release, a new and exciting method of integration was also introduced.


Introducing Eloqua Cloud Components!


Cloud Components allow marketers to incorporate cloud-based content onto E10 Landing Pages using any number of the pre-built apps.

With just a few mouse clicks, a marketer can:

  • Increase engagement and conversions
  • Increase social engagement and awareness without a huge investment
  • Embed surveys, videos, RSS feeds, social widgets and more
  • Focus on building campaigns, not HTML
  • Increase marketing productivity


How does it work?

It’s as easy as 1-2-3…

  1. Create a landing page (Components are currently only available in the E10 Landing Page Editor)
  2. Choose a Cloud Component from the available list, and Drag and Drop it onto the page
  3. Double-Click to configure



Note: Cloud Components are enabled and disabled by an Eloqua Administrator for a given instance.

See How to turn on additional Cloud Components in your instance... for more details.


Click here more information on connecting social and revenue, and watch the video to get an idea of how the Social Cloud Components are being used today.


While pre-built Cloud Components are generally available for use by Eloqua customers today, coming soon will be a framework for developers to build custom components to integrate with other systems. 


Development documentation will be posted as it becomes available.


I did the autofill, but now I have to manually map the Users email to the User Record?  My Rule has over 120 Users.


If anyone knows of a short cut or workaround, please please please let me know.


I'm in Command + C/Command + V Hell.



A/B testing is a key best practice to help you improve your email engagement rates. You execute an A/B test by comparing a test email, changing only one variable such as subject line, against your baseline email to determine which version drives the best results. Our recommendation is to carve off 10% from your initial Segment to use for the A/B test, and then splitting that portion in half, one half to receive the baseline, and the other the test. After determining the "winner", you send that email to the remaining 90% of the initial list.


For Eloqua10 users, there is capability to run an A/B test in Program Builder, but since you're sending emails, we recommend you use the Campaign Canvas. This article provides step-by-step instructions to create and use a Campaign Template for your A/B testing.



Create your A/B Testing Campaign Template

First, you'll need to create two Shared Filters. These will be used to execute the split of your lists: first, to carve off 10% against which to run the test, and then an even split for the two test emails.


The Criteria in your Filters use the unique Eloqua Contact ID value to determine into which split the Contact will be placed. All Contacts created in Eloqua are given a Contact ID immediately on creation, and the values end in a series of numbers. We're going to use these in an inventive way to create the split -- thank you to Eloqua Product Specialists Ryan Wheler and Anirude Gurcharn for developing this method!


1. Create a Shared Filter for the 90:10 Split

The single Criteria in this Filter is configured like so:


The comparator value is looking for any record with a Contact ID in which the second-to-last number is a 1. The * and the ? characters (an asterisk and a question mark, respectively) are referred to as "wildcards" in this type of application. The asterisk represents any number of any characters and the question mark represents any one character, and your value entered is "*1?" (without the quotes). To illustrate, if the Contact ID is ABC00000000093217, it will match this Criteria, and thus be included in this Filter. NOTE: This is an update from past versions of this article and uses newly-available Filter comparators in Segments.


2. Create a Shared Filter for the 50:50 Split

This Filter has multiple Criteria, and they're joined by ORs -- we want Contact records with an ID that matches any one of these Criteria:


In this case, we're using the last digit of the ID (hence the newly-available comparator of "ends with"), and since we want half of the records, we have Criteria for the odd numbers 1, 3, 5, 7, and 9.


If you're not sure what this means, don't worry. You'll only need to create these Shared Filters once as you see above, as you can reuse them as-is for all your future testing.


3. Create your Campaign.

First, drag the Audience, Assets, and Decisions onto the Canvas and connect them exactly as you see below. We'll go through configuring each following the numbers on the red arrows.


1. Wait

We need to include this "Wait" Action because the Campaign Canvas doesn't allow a Decision as the first action from the Segment. We can configure it for a small amount of time though, like so:


NOTE: If you are entering fractions of an hour in a Wait Action, make sure the value results in a whole number of minutes. For example, 0.25 Hours equals 15 minutes.


2. Shared Filter Member? -- carve off 10% of your Segment

Select the "90:10 Split" Shared Filter that you created in the step above for this Decision. Approximately ten percent of the Contacts in your initial Segment will meet the Criteria in this Shared Filter, and therefore pass down the "Yes" branch from the Decision.


3. Wait -- for the 90% that will receive the winning email

From the "No" branch of the "Shared Filter Member?" Decision, set the Wait for 3 days, or however much time, plus a window, you want to let your test run. You should have a good idea of the winning email in 24 hours after executing your test, and know with certainty by 48 hours after -- at this point, the vast majority of recipients will have responded, if they respond at all.


4. Shared Filter Member? -- split the test group into half

Now let's configure the execution of the split, again using a "Shared List Member?" Decision, but this time with your 50:50 Split, like so:


Approximately half of the Contacts entering this Decision will meet the Criteria in this Shared Filter and move down the "Yes" path, while the remainder go down the "No" path.


5. Save As Template

At this point, you've configured all of the elements you need to turn this Campaign into a Template that you can re-use for your future A/B tests! Your Campaign should look this:


To save your new template, simple select "Save as Template…" from the Settings menu:


Configure the Template for your A/B Test

Before we go to the Campaign Canvas, you'll need to create the following items for your A/B test:

  • Your initial Segment, the full audience to which you plan to send the message
  • Your baseline Email
  • Your Test Email


1. In the Campaign Canvas, create a new Campaign using your Template, like so:


2. Configure your initial Segment:


3. Add your Emails:


4. Change the dates to those appropriate for your Campaign:


5. Activate your Campaign.


6. Wait for the results of your Test. Be sure you do not wait longer than the number of days you configured in the Wait Action for the recipients of the winning Email! Your Campaign members will automatically exit the Campaign otherwise.


7. In Insight, run the report "Campaign Analysis" for your Campaign. You can either select it in the prompt, or create a Filter on the results, or find it by eyeballing the list of Campaigns. Click the value for your Campaign in the column headed "Total Sends" -- this will drill-down to the report with the results for each Email in your Campaign.


The metrics you'll use to determine the winning Email will depend on what variable you tested. For example, if your test was on subject line, you'll likely pick the Email with the higher Open Rate as the winner.


8. De-Activate your Campaign.


9. Add the Asset to send the winning Email:


10. Check that your Campaign Reporting dates are correct, and re-Activate your Campaign. The Contacts sitting in the Wait Action will be sent the winning Email.


Best Practices for Testing

Identify one variable you'd like to improve and develop a plan of attack. Here are some tips for testing:

  • Frame the problem in the form of a question. Propose a hypothesis: an educated guess as to the cause of the results. Then, determine what you'll test to prove or disprove that hypothesis.
  • Try to avoid testing too many elements at once, so as not to cloud your results.
  • Be sure you can measure what you are testing.
  • A technical note: if you wish to test one audience against another (everyone still receives the same email), you will need to have separate instances of your Email for each. At this time, Eloqua Insight is only able to report on Email engagement, not on a Segment.


Here are some suggested targets for your testing:

  • Subject lines
  • Highly graphical versus mainly text emails
  • Email or landing page layout, including offer placement and form length
  • Adding humor
  • Additional or less copy
  • Including segment-specific content


Looking for some great examples of A/B testing on both emails and landing pages? Check out Anne Holland's site "Which Test Won?" -- see if you answer correctly!

This is very basic Eloqua functionality that sometimes gets lost in the shuffle when it comes to form implementation. Some clients do this very well and others will often have a long list of forms that are very similar or even identical in nature. I think it's worth promoting the use of a single form to handle multiple assets and/or campaigns.


To quickly explain, many form processing steps allow you to use form field values to trigger actions rather than using a fixed action within Eloqua. This could be a confirmation email, a redirect page, a contact group, a program step etc. In many cases, these types of processing steps are usually the only aspects of an Eloqua form that change across different campaigns or assets. A lot of the time the form fields will remain the same and the overall functionality is very similar.


Take a resource download page for example:


1) Client has 65 Different PDF's

2) All assets are gated by a form

3) All assets require the same form to be filled out

4) Upon submitting the form, user is redirected to a confirmation page, sent an email, and added to a contact group.


Each asset requires the user to go through the same process. One method to complete this project would be to build 65 Eloqua forms, one for each asset, and change the processing steps for each.


Or, we could build 1 Eloqua form and add a few hidden fields on the front-end pages to handle the form actions.


It's quite simple - List what might need to change between assets:


1) Confirmation page URL

2) Confirmation email

3) Contact Group


Now add hidden fields for each of these items. Create processing steps for each action and then specify these form fields as the identifier of the action instead of the "constant" value.


Then when placing your front-end forms on each page you just need to hardcode the processing step values for each asset into the hidden fields. The confirmation email ID, the contact group ID, and the confirmation page URL.


Then you are all set.


The advantage here is that you save a lot of time building 1 form rather than building 65. You can also easily add new assets without needing to touch the Eloqua form. Also, imagine needing to add or update some fields to the resource pages. Needing to update 65 forms each time a change is requested is time consuming and prone to errors.


Note that not all campaigns are simplified enough to build a form in this way. Some campaigns are just too unique to simplify into one form and it's best to keep them separate.


I hope many people are already using this form method but also hope others who are not aware of this will find it useful.

When it comes to the Eloqua API, the question of how to retrieve marketing activity data comes up from time to time.


Normally, Eloqua is set up to send activity data to an external CRM system, for example, Salesforce.  But what if you want to use a custom system not included “out-of-the-box” with Eloqua? This is where the Processed Activity Queue (PAQ) comes in.

In order to retrieve the activity data, the PAQ will first need to be enabled in the Eloqua instance.  To do this, a support case will need to be created.

Once the PAQ is enabled for the install, activity data will begin being collected by the system going forward.  The data is not retroactive, and the system stores up to 45 days worth before being purged.


Using the Eloqua API, the data can now be retrieved by a custom application, and loaded into an external CRM system.

If CRM integration is already configured for an Eloqua instance, the PAQ can still be enabled, but extra configuration will be required.  Please contact your CSM for details.

Just getting started with using Eloqua for your event invitations, registration, reminders, and follow-ups? Automation will help you gain many hours back in your day, and there are some great templates for the Eloqua9 and Eloqua10 to help you kick off the process!



Campaign Template: BP Basic Event Template

Configuration Guide: In the Knowledgebase, search for article #1267, titled "Eloqua 10 BP Basic Event Template Configuration"



Program Template: BP - Event Registration (Single Session) (alternate names include "00 - Template - Event Registration" or "SYSTEM - Template - Event Registration"

Configuration Guide: In the Knowledgebase, search for article #1268, titled "E9_Managing Events using Program Builder"


Need additional guidance? If you have an Eloqua Education Pass, attend these Eloqua University courses:

  • Eloqua10: E10 - Multi-Touch Email Programs
  • Eloqua9: E9 - Increase Online Event Attendance


Good luck with your events!

Not sure if anyone else has had troubles tracking Google PPC keywords through Eloqua to CRM campaigns. Well, we set it up and realized it wasn't tracking. So, we spent three months figuring out why. Here are the issues we ran into in hopes that if someone else is having problems, they might know where to look.


1. Our query strings were set up wrong. They used the ? instead of the &.

2. Many of our forms were directing to a Contact Us campaign instead of Google Adwords.

3. Lastly, we realized that we needed to add a hidden field on the form to push through the campaign to CRM.


It sounds pretty simple, but when you are dealing with 187 groups of ad words, 37 custom landing pages and many different hands in the pot, it became quite a mess to unravel.


The other thing we did to streamline the process is to add embedded forms to our Google landing pages. We just did this in the last week so our numbers aren't in yet about how that will affect our completion rates, but time will tell.


Hope this helps.


Eloqua does not have built-in 10-10-80 A/B testing in the Campaign Manager, which is a shame. However, there is a workaround, and you do not need cloud connectors, random values, new fields, computed fields, or even Program Builder.


There are four easy steps:

  1. Create a shared filter that represents your market segment.
  2. Create three more shared filters that will represent 10%, 10%, and 80% of your total contact population.
  3. Create A/B/C market segments formed by intersecting your market segment filter with each of those shared filters.
  4. Create three campaigns, one for the A group, one for the B group, and one for the remaining 80% C group.


Step 1: Create a shared filter that defines your market segment.

You should know how to do this.


Step 2: Create 10-10-80 shared filters. Here's one half of the secret sauce.

I saw a couple posts where people are joining out to cloud connectors or generating random values in SalesForce. All of this is completely unnecessary. The Eloqua Contact ID is a uniquely-assigned sequentially-generated numerical value for each contact record. Create a shared filter that looks for Eloqua Contact ID's that end in 1 (equal to "*1"). Create another shared filter that looks for Eloqua Contact ID's that end in 2 (equal to "*2"). Create a third shared filter that looks for Eloqua Contact IDs that do not end in 1 and that do not end in 2 (not equal to "*1" and not equal to "*2"). After you do this, validate that you get 10%, 10%, and 80% of all your contact records in Eloqua.


Step 3: Create A/B/C market segments. This is the other half of the secret sauce.

To create an A segment, first create a new blank segment. Add the shared filter for your market segment and then add the shared filter for the A group. Select them both and then right mouse click on them and select "Intersect". You will see a third filter magically appear that now represents 10% of your market segment. Remove the other two filters, leaving just the intersection. Save and requery, and you should see 10% of your target market in your new A segment. Pretty cool, huh? Do the same thign for the B and C groups.


Step 4: Create a separate campaign for each of the three segments.

Create one campaign for your A segment and one for your B segment. Run them in parallel. Only complete and activate your C campaign after you've picked the winner from the A/B test.


That's it! No connectors, no random numbers, no new fields, no computed fields, and no Program Builder.


And the reason I had you make four shared filters is so that you can reuse your work and not have to reenter your criteria in several times because you will likely want to run A/B testing again in the future.

Filter Blog

By date: By tag: