Skip navigation

Email Signature Rules [KB.E.1.2.4]


This article includes:


Creating Email Signature Rules

Signature FAQs


Overview of Signature Rules


Signature Rules are used to support sending on behalf of many different people at once in a batch email deployment, and have the senders be dynamically defined based on the recipients of the email. A Rule can be used to map a specified field Value in a Contact record or Data Card to a specified Sender. For example, you could use the value of the City or State field to map to the reps for specific territories. You can also assign a default Sender if there is no territory assigned to a City or State Value.

When creating a Signature Rule, which is a mapping between a field value and a Sender, you are essentially making the following statement:

“When I send an Email Batch to a Segment, I want my Emails to look like they’re coming from different people so that they’re personalized for each recipient. Specifically, when an Email in a Batch is being sent to a person whose City is listed as “New York”, I want it to look like the Email was sent from “Active Salesuser.”  Additionally, if the contact does not have a value in the 'City' field, or their value is not listed in the rule, then the email will be sent on behalf of "Advanced Marketing.".  As displayed in this image:



Creating Signature Rules

  1. Navigate to Assets > Component Library > Signature Rule.
  2. Click the 'New' button in the top-right corner of the Signature Rule screen.
  3. Set parameters in the Signature Rule window.
    • Rule Name - Provide a name for identifying the Rule on the Manage Signature Rules page.
    • Key Contact Field… - Select a field from a Contact record in which the value can be used to identify the right Signature to use in an Email. For example, you could map specific Lead Ratings to Signatures for different Salespeople so that you can target specific types of Leads with the correct personnel.
    • Key Data Card Field… - Select a field from a Data Card in which the value can be used to identify the right Signature to use in an Email (this value will be referenced when an Email is being delivered using Data Card rather than a Contact).
    • Email Headers - The Email Headers include the following:
      • Sender Display Name - The name of the sender shown to the recipient.
      • Sender Display Address (“From”) - The email address from which the Email originated as shown to the recipient.
      • Reply-To Display Name - The name of the person to whom to send replies to the Email shown to the recipient.
      • Reply-To Address - The email address that recipients reply to as displayed to them.

        If you select Personalize all email Headers when Rule is applied to a batch, then when you send a Batch Email with the Signature Rule applied, the dynamic sender information generated by the Signature Rule overrides all four of the settings on the Email Details page (to view this page, with the Email open for editing, go to Email > Email Details).
        If you only want to override specific settings within this group, then click Show Advanced Options; the page expands to show the individual headers (as shown in the diagram above). Select the specific headers that you want to override according to the Signature Rule.
    • Mapping - Map each Value for the specified field found in the Contact record or Data Card to an individual Sender. Click the button in the Sender field and find the sender (or create a new one) in the Search window. You must also set a Sender for cases where the field value is not recognized or is empty (a default Sender) . In addition, you can edit the details for a user selected in the picklist (Edit User).
      You may add additional mappings as required by clicking the Add New Mapping button at the bottom of the table.

      The Autofill Values option will look at all the Contacts in your database, and in particular, in the Contact field you have defined as the Key Contact Field (above), and the list all the different values it finds in order of the most frequent to least frequent appearance.

      For instance, if you have defined the Salesperson field as the key contact field defining the sender of the email and you press the Autofill Values button, the system will bring back all the values currently listed in the Salesperson field of all your contacts. Then, you can simply assign a sender to match up with all those values.
  4. When you have set all the parameters for the Rule, click Save and Close.



Q: How do I define which Signatures go out in which Emails?

A: Before we talk about how you define what goes where, you need to understand the general architecture of Signatures. One of the most important concepts to understand is that there are really no such things as “Signatures” in the Eloqua system.


You will never create, manage or insert a thing called a “Signature”. A Signature is the combination of SENDER INFORMATION + A TEMPLATE THAT DEFINES HOW THAT INFORMATION SHOULD BE DISPLAYED IN AN EMAIL. Or, in Eloqua terms, a User + a Signature Layout.

So in short, you do not define what Signature goes out in which Email; instead, you decide:


Q: The available fields in the User Profiles don’t match up with what I need in my Signatures. For instance, I need to put 4 different phone numbers in my Signatures, but there are only 3 phone number fields in the User Profile. Can I add fields to the User Profile?


A: No, you cannot add User Profile fields like you can Contact fields and Email fields. We recommend that if you run into this problem, use another field (like “Personal Message”) for a purpose other than that indicated by its name. So if you need a 4th phone number, for example, enter it in the Personal Message field for each user and insert it into the layout that way.

If we are blatantly missing fields that you think most people will need to use, please let Eloqua’s support team know and they will pass the message along to Product Management so they may try to incorporate the additions into a future release.

Q: How do I make it so that the Sender Display Name is the same for all Email recipients, but the “From” address and Reply-to headers are dynamic? Or in other words, how can I apply a Signature Rule without affecting the Display Name?

A: Yes, you can split up all the Email headers and define them individually—the From Address, Reply-To, Display Name, etc.

Capture.PNGAfter a year of 'beta' testing, I'm now very pleased to invite you to Eloqua's space on --!


AutomatedMarketing is the place to discuss marketing automation solutions, strategies, demand generation, providers, and market conditions. This includes web marketing, email marketing, marketing segmentation, revenue growth, software capabilities, and more.


AutomatedMarketing is a great place to find out what Eloquans are reading and talking about including the most recent news, the best content from (75 links and counting!), best practices, and time saving tricks. It's been live for about a year and in that time I have compiled over 286 curated, searchable links! Quickly learn more about complex topics like: EU privacy regulation, lead scoring methodologies, content marketing strategies, and more by searching within AutomatedMarketing.


Have questions? Updates to the article? Advice? Links of your own that are too good not to share? Leave comments or submit content and get shiny upvotes for your efforts! Reddit is an astounding communication and information sharing platform that you can access in moments. Then, engage with other marketers, other Eloqua users, and the general internet! Vote on the things you like, downvote the things you don't, and customize your experience - Reddit is all about adapting to your interests and tastes, and hopefully, you'll want AutomatedMarketing as part of your own "front page"!


There is a ton of great stuff already in place over at AutomatedMarketing, all that we're missing is you! If you are already a Reddit user, please visit the page and subscribe. If you are new to Reddit but curious, the first step is a quick account registration (astonishingly painless). Sign up and start subscribing to 'sub-reddits' (AutomatedMarketing is an example of a 'sub-reddit'), and importantly, unsubscribing from the content areas you don't want. For example, I have one Reddit account - EloquaEmployee - for work and another for home. They use the same platform, but provide different experiences.


The Preferences page in the top right corner of any Reddit page will be important to read; there are a lot of valuable settings to familiarize yourself with.


Please consider this short list of other 'sub-reddits' you may wish to subscribe to, but there are thousands more to choose from:



For some idea of what to expect, here are the 5 most recent submissions for AutomatedMarketing:



The top 5 all time submissions at AutomatedMarketing by votes:



Please stay tuned to AutomatedMarketing and for more news about Reddit and the growing AutomatedMarketing community as I have some great ideas to come! I'd be happy to address any questions you may have and do feel free to private message me on Reddit with any questions or requests!


Thanks and happy Redditing!



*A big thanks to Egan Cheung, Michael Gray, and Heather Foeh for their assistance and encouragement on this project so far!

Come and join the discussion at the Eloqua University group -


We are currently designing a suite of courses that are based on case studies.

Did you design a killer campaign in the past six months? Have you used dynamic content in a unique way to personalise customer experience?

Just think what an honour it would be to have YOUR work featured at EloquaU?

Of course, credit would be given to your organisation, and any requests for proprietary privacy and discretion would be respected.

Reach out to me at education -

Can't wait to hear your ideas!


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



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

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

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

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

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

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

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

Run Step:

Run step has 3 separate sub tabs:


Step Members:

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

The step shows 3 "statuses". They are:

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

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

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

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

Run Step:

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

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

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

Sample Data:

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


The history area shows the following information:

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

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

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

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

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

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


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

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

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

For example, the twitter page looks like this:

twitter SSO.jpg

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


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

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

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

twitter custom app.jpg


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



The URL for Twitter is the following:

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


The following fields are required:

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


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



The URL for LinkedIn is the following:

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


The following fields are required:

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

  • Agreement Language: Set this to the appropriate language

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

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

Ali Siena-Oracle

Email Signatures

Posted by Ali Siena-Oracle Feb 13, 2012

Email Signature Layouts [KB.E.1.2.2]


This article includes:


Creating Signature Layouts

Deleting Signature Layouts

Managing Signature Layouts

Examples of Using Signature Layouts


Overview of Signature Layouts

Signatures allow you to attach sender identity information to an email in a specific format. Each salesperson can include his or her picture, signature, personal message and contact information in the email. This personal touch builds the relationship that they have with their prospects and clients, and increases response rates.

Here are some examples:



Personalizations can be created for the signature for each of the agents using the Eloqua application, so that their identity information and personalizations (such as a customized message for a specific client) can be added to each email sent out. Agent signatures and personalizations can be created one at a time or in bulk mode using signature rules that automatically apply the correct signature to each email based on specified criteria.


Signatures are a powerful way to allow your sales personnel to cultivate and grow relationships with their prospects. Each outgoing email can be signed as coming from a particular salesperson, with that salesperson’s Sender Name and Reply-to Email info in the email headers and their personal details in the body of the email message. It is also possible to automate Signature personalization so that when sending to a distribution list of thousands of people, either manually or through an automated program, you can display, for each recipient, the signature that is most appropriate for them—for example, the signature of their account manager.


Signatures are easily created for several employees by designing a Signature Layout that defines how Signatures should look within an Email and what information they should contain. Offering the ability to easily manage consistent corporate branding as well as the ability to create Signatures in bulk, a single Signature Layout can be created which then dynamically pulls in details of the sender (e.g., if the “Sender” is Ray, then the system will pull Ray’s information into the Signature Layout; Name, Phone Number, etc.).


Signatures can include employee pictures, digital signatures, personal messages, and contact information. This personal touch builds the relationship that your company and sales representatives have with their prospects, contacts, and clients and helps to increase response rates to marketing and sales campaigns.


Creating Signature Layouts

You can create new signature layouts or edit an existing layout by using the inline editor. The procedure below outlines building your Signature Layout in WYSIWYG Mode, but you can also build it directly in the HTML code by clicking the Switch to Source Mode button and adding to or altering the code.


To create a new signature:

  1. From the navigation toolbar at the top of the page, select Assets > Component Library, then click Signature Layouts in the Component Library (the left-hand pane).
  2. Click New. The Signature Layout Editor window opens.
  3. Enter the Signature Layout Display Name (the name by which you will be able to find this signature layout).
  4. Add the elements you want to include in the signature layout, including the following:
    • Text - You can type in plain text at the cursor location, then format the text using the controls at the top of the editor window.
    • Insert User Field - By clicking on this button at the bottom of the window, you can select a dynamic user field to insert as part of your Signature Layout . The inserted dynamic field , at the time of preview or email deployment, draws information from that field within a user’s/agent’s profile (the person eventually chosen as the sender of an Email)—this way, Signatures are dynamically populated by the user profile information for the different senders of the email. Examples of the types of fields that might be available in your implementation of Eloqua® are shown in the diagram below. When you have selected a field, click Insert, and repeat for additional fields as required.
      Placeholders for the user fields appear as boxes with text in the Signature Layout (see the following diagram), and have a shaded background.
      Note: Some user fields (link-based fields, and fields with optional labels) provide different options upon insertion, depending on the nature of the data that will be eventually populated into that area.
      • Link-Based User Fields - When inserting either the Website URL user field or the Personal URL user field, the options are provided to have display text for the link and to make the link trackable (accounted for in Email Reports) as long as the linked page has Eloqua tracking scripts. Note: You can also insert other fields from the list (for example, First Name or Last Name), but only Website URL and Personal URL will have all of the options shown below (if the Display Text checkbox is selected).


      • Fields With Optional Label - Not all fields need labels. However, information such as a telephone number is commonly preceded with a label. Therefore, when you choose to insert a telephone-based field, the system will automatically insert a field label with the field. That label is editable, and will also disappear automatically (indicated by the grey background) on email deployment if the user profile of the sender does not have a value in that field (e.g., if sending on behalf of Mike and Mike’s user profile doesn’t have any data in his “Cell Phone” field, but in your Signature Layout you have both the Cell Phone field inserted as well as a label that reads, “Cell Phone”, the term “Cell Phone” will disappear when the system finds nothing in that field of Mike’s profile).

        Tip: Be careful when inserting additional punctuation such as commas between the fields in the Signature. If there is no content to populate a field, both the field and label will disappear, but punctuation that you added will remain. If you do use punctuation between fields, make sure that all possible senders using that Signature Layout have field values for every field in their User record.

      • Insert/Edit Image - You can insert an image such as a picture of the sender, a logo, or a banner at the cursor location in the Signature. Click the Insert/Edit Image button, then select a picture using the search tools in the Image Selector dialog box.


        You can View All images and scroll through the pages using the forward and back buttons, or search for an image Name, creation Date, or Owner using the search functions at the top of the page.

        Once you have chosen an image, click Select, then OK, to insert the image in your Signature and close this dialog box.

        Once an image has been inserted, you can also edit image attributes. Click on the image, then click Insert/Edit Image.


        You can manage the following image attributes:

      • Image Dimensions - Enter values for the Height and Width. Maintain the ratio of the Height to Width by selecting Maintain image proportions or Reset the image to the original dimensions.

      • Image alignment - Control the positioning of the image relative to the text around it. For example, you can Left Justify the image so that the text wraps around it on the right. The thumbnail shows you the relative positioning of the image and text.

      • Image Borders - Set the width of the Border, the Type (for example, dotted, dashed, groove, ridge, etc.), and the Color. Click Show Advanced Options to set the border attributes separately for each of the four sides of the image.

      • Text Alternative - Enter the ALT text to be shown if the image does not render or if the recipient moves their cursor over the image area.


    • Insert/Edit Hyperlink - You can insert one or more hyperlinks in the Signature (using text or images), including links to website pages, Eloqua Microsites (Landing Pages), email addresses, or ICS calendar files (so that the recipient can download an Event directly into their email client calendar). You can also allow your recipients to share a URL through a social media channel. Place the cursor where you want to put the hyperlink, or select text that you want to configure as a hyperlink, then click Insert/Edit Hyperlink. Select the following parameters in the Insert/Edit Hyperlink dialog box (they may change depending on the selections you make):

      • Link Type - You can select Text Link, then type in the Text for Link, or chose Image Link and Select Image for Link by clicking the button in the next field. Note: If you selected text or an image in the Signature Layout before clicking Insert/Edit Hyperlink, then the link will automatically

        be set to the right type and the Link Type field is not displayed.

      • When link is clicked - Select the action that will occur when the recipient clicks on the link. The action may be to send the recipient to a webpage or activate an email message (mailto:).

      • Insert as Redirect Link - If you choose Send to Webpage as the action, and you are linking to a page that does not contain Eloqua tracking scripts, you can select this checkbox to make sure that click-throughs are still tracked in Eloqua

        When you have configured this element, click Insert to add it to your Signature Layout. The Insert Hyperlink dialog box closes. If you want to change settings for the hyperlink, select it in the Signature Layout and click Insert/Edit Hyperlink.


  5. Repeat step 4 in this procedure as required to insert additional elements or to edit them in your Signature Layout. Click Save after adding each element and when you have finished building or editing the Signature Layout.

    Note: If you try to leave the page without saving an edited Signature Layout, you will be prompted to save the Signature Layout before proceeding.
    Click Cancel to return to the current Signature Layout in the Editor so that you can save your changes (click Save in the Editor).
    Click OK to leave the Editor without saving your Signature Layout.


Deleting Signature Layouts

To delete a signature layout:

  1. From the navigation toolbar at the top of the page, select Assets > Components, then click Signature Layouts in the Component Library (the left-hand pane).
  2. Find the signature layout you want to delete in the list and select it.
  3. Click the Delete button at the top of the window.
  4. Click Delete in the confirmation window. The signature is permanently deleted from the application.


Managing Signature Layouts


To edit a signature layout:

  1. From the navigation toolbar at the top of the page, select Assets > Component Library, then click Signature Layouts in the Component Library (the left-hand pane).
  2. Double-click on an existing signature in the list of signatures. The Edit Email Signature window opens.
  3. You can change the Name and/or the contents for the signature. When you are done, click Save. The signature layout is saved to the list of signature layouts using the new information you provided. Note that the signature layout will be shown alphabetically under the new Name (if you changed it) in the list.


To rename a signature layout:

  1. From the navigation toolbar at the top of the page, select Assets > Component Library, then click Signature Layouts in the Component Library (the left-hand pane).
  2. Double-click the signature layout you want to rename and change the name in the Signature Layout Display Name field.
  3. Click the top Save button to save your changes, then click the bottom Save button to close the window.


Examples of Using Signature Layouts

Signatures are the templates for automatically inserting Eloqua sender information in emails. Using the inline editor, you can create signatures. The signature content is drawn from data contained at the user/agent profile level into the fields you use in the signature.


Here are examples of how the signatures might be used:


Example 1: Email Personalized for Recipients

Marketing is launching a new Campaign to a segment of their contacts (just over 60,000 contacts). To begin the Campaign, they will be sending out one email to all contacts, but they want each email to be personalized for each recipient so that the email appears to be from that contact's regional sales representative, and when they reply to the communication, the reply goes directly to that representative.


Example 2: Enforcing Standard Practices and Branding

As a final step towards unified corporate branding within marketing collateral, the marketing team creates a single signature that is to go out in all email marketing communications, containing all the standard formatting (e.g., standard corporate font for digital collateral), information and content: Name, Title, Department, Office Number, Cell Number, Company URL and Company Logo.


Example 3: Localization

Three different corporate regions require 3 different Signatures due to variations in the company logo or tagline across the regions, so 3 different signatures are created so that when emails go out and are personalized for the recipient, each rep's signature follows their own region's brand standards.


Example 4: More Information and Sharing Social Media Links

Recipients can click on links or banners to see current information that is relevant to them, or click on different social media links provided in a signature to share specific content to social media sites. This helps to drive traffic back to company content such as blogs posts or web pages.


Ali Siena-Oracle

Email Field Merges

Posted by Ali Siena-Oracle Feb 13, 2012

KB.E.1.2.1 Email Field Merges


This article includes:


Creating Field Merges

Deleting Field Merges

Managing Field Merges

Examples of Using Field Merges



Field merges are useful for drawing information from contact records. These data are used for personalization in an email or on a landing page (for instance, referring to the recipient or visitor by their first name, first and last names, company, country, or other specific information that is in their contact record). Note that field merges are highlighted in yellow in order to quickly distinguish them from normal text.



Creating Field Merges

To create a field merge:

  1. From the navigation toolbar at the top of the page, select Assets > Component Library, then click Field Merges in the Component Library (the left-hand pane).
  2. Click New. A new, untitled field merge is added to the bottom of the list of field merges.
  3. Enter the field merge name and press Enter.
  4. Double-click the new field merge in the list. The Field Merge window opens.
  5. The Name is shown in this window. If required, you can edit the name.
  6. Select the field type from which you want the merge to occur: Contact Fields or Account Fields.
  7. Find and select the name of the field for the merge in the Contact Field or Account Field drop-down list.
  8. If required, enter a Default Value that provides the data for the field if no other field data is available.
  9. When you have set these parameters, click Save. The field merge is stored in the list.


Deleting Field Merges

To delete a field merge:

  1. From the navigation toolbar at the top of the page, select Assets > Component Library, then click Field Merges in the Component Library (the left-hand pane)
  2. In the list, right-click the field merge you want to delete, then click Delete in the menu.
  3. Click Delete in the confirmation window that opens. (Note: If this field merge is included in another Eloqua asset, the Dependency Viewer will display, indicating that you must resolve the dependency(ies) before being able to delete the field merge.) Once all dependencies have been resolved (if applicable), the field merge is permanently deleted from the application.


Managing Field Merges


To edit a field merge:

  1. From the navigation toolbar at the top of the page, select Assets > Component Library, then click Field Merges in the Component Library (the left-hand pane).
  2. In the list, double-click the field merge you want to edit. The Field Merge window opens.
  3. Make any changes required. For details about the changes you can make, see Creating Field Merges.
  4. Click Save when you are finished editing. Note: If you have changed the Name of the field merge, it will be in the list in alphabetical order under the new name.


To rename a field merge:

  1. From the navigation toolbar at the top of the page, select Assets > Component Library, then click Field Merges in the Component Library (the left-hand pane).
  2. In the list, right-click the field merge you want to rename and select Rename.
  3. Fill in the new name for the field merge and press Enter.


To create a new folder in the list:

  1. From the navigation toolbar at the top of the page, select Assets > Component Library, then click Field Merges in the Component Library (the left-hand pane).
  2. In the list, right-click an existing field merge or folder and select New Folder. Note that the folder will be created at the same level as the field merge you have selected, or as a sub-folder if you chose a folder.
  3. Fill in the name for the new folder and press Enter.
  4. If you want to add any field merges to the folder, either drag-and-drop existing field merges onto the folder or select the folder and click New to create a new field merge in the folder.


Example of Using Field Merges

You can use field merges to insert personalized information into an email or landing page. This increases the likelihood that the visitor or recipient will interact with your content. The following are a few examples of the most common uses for field merges.


Example 1: Inserting a Personalization such as a First Name Field Merge

By far the most common use of field merges is to insert personalization (such as the visitor's or recipient's first name) into the email or landing page. By inserting their first name, you are aiming your communication directly at them. This turns even simple emails into customized "one-to-one" conversations Note that field merges are distinguished from regular text by their yellow background shading.


Example 2: Inserting the Company Name

You can insert a visitor's or recipient's Company name into an email or landing page to point out features of your product or services that might be particular valuable to their employers. This is usually done within the framework of increasing productivity or helping to boost their careers.


Example 3: Account or Service Information

Customers or your own staff can be provided with information related to a specific account or company, including modification dates or time stamps for various activities, billing address information, or sales/service representatives information.


Example 4: Event Information

By drawing field data from Data Cards (which are used for Events and Surveys), you can provide event information, such as confirmed times and dates, to your registrants or respondents.

****Information on Browser Support been updated and moved to the following location:  Please refer to the new URL for all currently supported and certified browser and operating system information.*****

Ali Siena-Oracle

Profile Confusion

Posted by Ali Siena-Oracle Feb 9, 2012

Important:  The product documentation is available on our new help website.

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


SurveyGizmo Cloud App


This article will describe the individual pieces of the SurveyGizmo Cloud App, and how to use them within your instance of Eloqua.


In order to use the SurveyGizmo Cloud App, you will need an existing account on SurveyGizmo, with surveys already created.  You must also be registered at  When creating your account on, 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


SurveyGizmo Cloud App Components


The SurveyGizmo Cloud App consists of the following:


  • SurveyGizmo Embed - this Cloud Component allows you to embed a SurveyGizmo survey or poll into an E10 landing page.


  • SurveyGizmo Feeder - allows you to pull into an Eloqua group, all the people who have filled out a specified survey, along with a select number of responses to questions (currently, you can track up to 10 questions).


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


Installing and Configuring the Cloud App


SurveyGizmo Embed


The SurveyGizmo Embed component is already available for use in E10, but may need to be enabled.  See here for more information.


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


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


Now, drag and drop the SurveyGizmo Embed component onto a landing page:




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


Enter your credentials and click Log in.  The configuration screen for SurveyGizmo Embed will then be displayed:



On the configuration page, do the following:

    • Enter the Admin Email Address (your email address).
    • Enter your SurveyGizmo Username and Password.
    • Click “Save Settings”, and a list of your SurveyGizmo surveys will show in the Survey Name drop-down list.
    • Select a survey and then press Save Settings. 
    • If your credentials are accepted, a list of embed codes will display in the Embed Code drop-down (see note below).
    • Select an Embed Code
    • Select a size for your survey and click “Save Settings”. You can now close the configuration page.


Note: In order to see an embed code in the list, you will first need to create one in SurveyGizmo.  To do this...

      1. Log into your SurveyGizmo account, select a survey, and click on Publishing
      2. Click on IFrame Embed.


A screen will appear where you can name your embed and press Save.



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


SurveyGizmo Feeder


  • The SurveyGizmo Feeder does not require installation, as it is a standalone application that runs outside of Eloqua, and connects to your instance.
    • Make sure that the Eloqua user account that is being used for the feeder had Eloqua API access. 
    • Create a Contact Group in Eloqua (called a Contact 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 in Eloqua, to store the Event information returned by the feeder. For more information about creating a DataCard Sets, please search the knowledge base for an article named "Database Management".


     To access and configure the feeder, first visit and log in.


     Once logged in, select Products...Feeder, and choose "SurveyGizmo Feeder”.


Click New Step on the screen that appears:



The configuration screen will then appear:


Enter your Eloqua Client Name, Query Frequency (how often the feeder should run), Eloqua User Name (make sure the user has API permissions), Password, and Admin Email Address. Click Go.


The Setup screen will then be displayed.


On the Configuration tab, do the following: 

    • Enter a description for the feeder (optional) and choose your.
    • Enter the Admin Email Address (your email address).
    • Enter your SurveyGizmo Username and Password.
    • Click “Save Settings”, and a list of your SurveyGizmo surveys will show in the Survey Name drop-down list.
    • Select a survey and then press Save Settings.
    • If your credentials are accepted, a list survey questions will be populated in each of the Question drop-down lists.
    • Choose the survey question that holds the Email Address (required) , First Name (optional) and Last Name (optional).
      • Note: In order for the feeder to create contacts, you MUST have a question on your survey that asks for the survey taker's email address.
    • Choose the survey questions (a maximum of 10) that you wish to track answers to.
    • Choose the existing Contact Group (E9) or Contact List (E10), in which to place the newly created contacts.
    • Choose the existing Custom Data Object in which to store the returned survey data.
    • Click on Save Settings, and then click on the Field Mappings Tab.



On the Mappings tab, choose which Eloqua Contact and Custom Data Object fields to map to corresponding data from the SurveyGizmo system into when the feeder runs. 

    • For the Custom Data Object, the field list selections will be populated based on the existing Custom Data Object chosen on the Configuration tab.
    • Note: for Display Name Fields (Custom Data Object) field, the field you choose MUST be set as Unique in Eloqua in order for the feeder to function properly.



On the Test tab you can test the feeder. You can choose between a “Dry Run” (no data will be changed in 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 SurveyGizmo feeder is configured and enabled, leads will begin to flow into Eloqua based on your Surveys.

Ali Siena-Oracle

Email Status Codes

Posted by Ali Siena-Oracle Feb 8, 2012

Email Status Codes


The following list is a breakdown of the Email Status Codes:


2Has not responded to subscription request
3Subscription request accepted. No emails sent
10Forced Complete
11Global Unsubscribe
18Excluded from Email: Resend
19Excluded from Email: Master Exclude
20Excluded from Email: Bounceback
22Excluded from Email: Unsubscribe
23Excluded from Email: Global Exclude (eloquas master list)
25Excluded from Email: Email Group

[The Eloqua9 version of this guide can be found at].


If you’ve maintained your marketing database for a length of time, it may be valuable to do some spring cleaning by deleting contacts you’re unable to reach or engage. If a large portion of your database is no longer of use, this may be skewing your reports and analysis of the overall health of your database.


What kinds of contacts might be candidates for deletion?

  • Contacts whose email addresses have hard bounced. A hard bounce means that the address was rejected by the receiving email server because either the account or the domain did not exist, or there was a network problem on the recipient's end.
    • Before deleting, you may want to investigate if the bounce was caused by a malformed email address (e.g., that could easily be corrected.
  • Prospective customer contacts that have unsubscribed from receiving any email from you, and you have exhausted alternative channels with which to reach them, e.g., by phone, or they are not valuable enough to attempt to re-subscribe.
  • Contacts that are no longer at the company.
  • Contact records that have been deleted from your CRM system.
  • Contacts that have been disqualified as prospective customers. However, if these contacts are currently engaging with your broader communications, such as newsletters, you may want to keep them in your database – they may be interested enough to become customers at their next job.
  • Contacts that have not engaged with either your outbound or inbound channels in a long period of time, especially if it exceeds your average length of sales cycle.
    • For these types of contacts, it is strongly recommended that you attempt to re-engage them one last time before deleting their records: Create an Automated Reengagement Campaign in Eloqua10. If they are a valuable prospect, you should attempt to re-engage the Contact through channels other than email before considering deletion.


As you go through the exercise of identifying which contacts to delete, consider whether the cost of keeping them has exceeded to cost of acquiring them. For example, if your company spends an average of $250 to generate an inquiry, but only $25 a year to keep them, you could afford to keep them in your database for up to 10 years for the same cost.



Please take a moment to read through this entire document before proceeding, so you’re aware of the full ramifications of deleting your Contact records in Eloqua.


How do I delete Contact records?


1.   Add the Contacts to a Segment

Once you’ve identified the criteria for the Contacts you wish to delete, you will need to add them to a Segment. You can add Contacts to a Segment using Filter Criteria (using Contact field data as well as activity and/or inactivity), searching for Individual Contacts, through a list upload, or Shared Filters or Lists.


For instructions on how to create and manage Segments, see Article Number 1152 in Customer Central titled “Eloqua 10 Segments”. Note that you can enter this number directly into the search.


2.   View the Contacts

From your Segment, click the “View Contacts…” button:


3.   Export the Contacts

In the “View Segment Members” window, click the “Export” button in the lower left corner. In the pop-up, make sure your email address appears and that you select “All contact fields” for export. Click the “Export” button to send an email with your list of Contacts.


Eloqua will send you an email with your Contact list, which you’ll need to perform the Contact deletion.


As a best practice, you should also:


  • Save this list within your organization’s systems as a backup, should you need to access the Contact data at some point in the future.
  • Export all Custom Objects (see Article 1012 in Customer Central titled “Data Cards”, section “Viewing and Managing Data Card Set Reports”) for these Contacts, as this information will not be re-created by Eloqua, should the Contact record be re-created.
  • If you track communication preferences (e.g., Do Not Call, Plain Text Email Only) solely in Eloqua, upload this information into your CRM. Consider doing this for both the Contacts you are deleting at present, and as part of the update process for Contacts going forward.


4.   Delete the Contacts from Eloqua


Please note that deleting Contacts is an irreversible action. If you accidentally delete any Contacts, we may not be able to recover all your data, and you may incur additional fees to do so.


For the actual deletion, navigate to the Contacts section and click the “Upload…” button:


In the Contact Upload Wizard, under “Import Purpose”, select “Delete Contacts”:


Continue through the Contact Upload Wizard steps – see Article 1148 in Customer Central titled “Eloqua 10 Contacts” for more detail.


IMPORTANT: If you have CRM Autosynchs, you will need to prevent these Contacts from returning to your Eloqua database via the synchs. You have two options:


  1. Create a field on the CRM record to mark them (for example, a checkbox “Do not sync”), and add a Filter to your Autosynchs to bypass those records that have the field checked (see Article 1003 in Customer Central titled “CRM Integration”, section “Retrieve Data”). You can find detailed explanation on accomplishing this here: Effectively Removing Records from Eloqua. Or,

  2. Delete the same Contacts in your CRM system. Note that this document does not discuss any considerations or ramifications around deleting records from your specific CRM system.


What affect will this have on historical reporting?

It is strongly recommended that you export any reports (Article 1278 titled “Eloqua Insight Analyzer User Guide”, section “Exporting Reports”) that include Contact fields, Profile data or Custom Objects associated with these Contacts. Once the Contacts are deleted, the following types of reports will be affected:


  • Reports using Contact attributes – any report rows for a deleted Contact will display “Deleted Contact”
  • Reports on Program Builder Program membership, entry, exit or paths
  • Reports using Custom Object linkages to Contact records


What happens if a deleted Contact comes back into my database?

If a deleted Contact is re-created, for example, if a deleted Contact comes back into your database from a Form submission, the following data is maintained and will return:


  • Subscription Status (Subscribed/Unsubscribed)
  • Email Status (Bounceback/Valid)
  • Bounceback history
  • Profile data (only if the Contact’s Eloqua cookie is still active), including:
    • Email sends, opens, and click-throughs
    • Form submissions
    • Web visits
    • Referrers
    • Content Tags
    • Query Strings


If a Contact had a Status of Unsubscribed or Bounceback at the time of deletion, the re-created Contact record will have the same status, which will need to be reset before you can send any email.


The following data will not return:


  • Shared List memberships
  • Subscription Group memberships
  • Program Membership history (entries, exits, paths through programs)
  • PURL Names (a new PURL Name will instead be created)
  • Custom Object linkages to Contact record (note: the Custom Objects remain in Eloqua, but will no longer be linked to the Contact)
  • Datestamp values, such as “Date Created” (these are re-set to the new date)
  • Expired Profile data (if the Contact has no activity on their Eloqua cookie for more than 4 months)
  • External Call history


If the Contact record is re-created from the CRM via an Autosynch, those Contact fields populated by the Autosyncs will be re-populated. Any fields populated only by Eloqua (e.g. from Form Processing Update Rules) will not be re-populated. Any Custom Objects created by Autosynchs will also be re-created, but with the same caveat that data in Eloqua-populated fields will not be re-populated.


If you have any questions about the information in this document, please contact our Support team at 866.327.8764 or online via Customer Central.

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

Slideshare Cloud Connector


This article will describe how to install and use the SlideShare Cloud Component, allowing you to easily pass leads that are generated from forms on SlideShare back into Eloqua; these leads can then be sent a follow up email, entered into a nurturing campaign, scored or sent to sales for follow up.


In order to use the SlideShare Component, you will need to have a Pro SlideShare account. You will also need to register at and have a API enabled Eloqua user account.


- Example of a form from Slideshare


What is the difference between


Slideshare Components


The SlideShare Component consists of the following Feeder

  • SlideShare: Lead Queryallows you to query Slideshare for all leads who have visited any campaign or a particular campaign. This Cloud Connector is a feeder and does not require a program builder step to work.


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


How to Install the App


To get started, go to Feeder > SlideShare Lead Query within  Feeders do not require a Program Builder step as they just run on their own and feed data directly into the Eloqua system.



Next you’ll be asked to create a new SlideShare Lead Query step, add your Eloqua credentials and specify the details of how often you would like the Feeder to run.




On the next screen, you will be asked to enter your SlideShare account details. Note – this MUST be an PRO account.  You have the option to enter a specific SlideShare CampaignID (you can find what this is by looking at the number at the end of the SlideShare item URL. E.g. In addition, you can also define the Eloqua Contact Group you would
like to add the contacts to.




Next, select the Field Mappings tab and specify the contact fields or custom data fields you wish to use to store the information from SlideShare.




You can now select the Run tab to test run your SlideShare Lead Feeder. If you now open Eloqua and navigate to the Contact group you chose to store your SlideShare leads in you will be able to see all the people who filled out a form from SlideShare.




If you are happy with the results being imported to your contact group, you can now have this feeder to run automatically on the schedule you originally indicated; by going to the Credentials tab and selecting the Enable Step checkbox.




With this automated connection set up, you will now receive regularly schedule updates to your contact group for all leads that have filled out a form from Slideshare in real time. 

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


Brainshark Cloud App


This article will describe the individual pieces of the Brainshark 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.

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

What is the difference between and


Brainshark Cloud App Components


The Brainshark Cloud App consists of the following Cloud Component:

    • Brainshark Embed - allows you to embed an Brainshark Presentation into an E10 landing page.
    • Brainshark Feeder - allows you to import viewers of your Brainshark presentation into Eloqua.


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


How to Install the Cloud App


The Brainshark 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 be displayed.



Drag and Drop the Brainshark Embed 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.


Next, a page will display that will ask for your Eloqua credentials (Note: the credentials entered MUST be for an API enabled Eloqua account).



Once the details are entered, click Go, and the configuration screen for the Brainshark Embed component will then be displayed:



On the configuration screen, do the following:

Enter your:

      • Brainshark Username
      • Brainshark Password
      • Brainshark Company Name


Click Get Presentations


If you have entered your Brainshark credentials correctly, your presentations will show up in the Presentation drop-down list.


Finally, select a Presentation from the list, and choose an Embed Size.


Note:  you will have to play with the size of the component on the landing page to make your presentation fit


To help with this, here are the actual dimensions for the different size options:




Click on Save Settings and close the Configuration screen.


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



When a  known Eloqua contact visits the landing page and views the video, the component will pass viewer data to Brainshark.  This data will then be included in your presentation reporting in the Brainshark system.


I'm uploading a group of contacts who have subscribed to newsletters in a previous system. Is there a way to subscribe a batch of exel contacts to particular email group? Of course I can upload them to a shared contact list and use it in segmentation but it would be simpler if I could mark all of them as subscribed.

Filter Blog

By date: By tag: