Skip navigation

I often find that I need to test multiple Eloqua forms within a short window of time, or I want to test one form using multiple submission data variations back-to-back to make sure the form processing logic I've created works correctly.  Of course to do this quickly, I often need 10 different email addresses (Eloqua's unique contact identifier), so I don't overwrite the data on a contact record before I have a chance to audit it.

 

Having a Gmail email address makes this easy! You can insert a period anywhere in your Gmail address before the @ symbol to create a unique Eloqua contact, and the best part is that this email address will still work for auto-responders and other emails your testing may trigger. Therefore, you only have to check one email account for triggered emails. Yay!

 

For example:

If your base Gmail address is betsytestemail@gmail.com, you can use periods to create multiple contacts in Eloqua using variations like

 

UPDATE - additional tip from Rebecca Baker:
You can also add a + sign followed by a number directly before the @ in your base email address (e.g. betsy.test.email+1@gmail.com, betsy.test.email+2@gmail.com, etc.). The email address is functional for triggered emails using this method, too.  Thanks for this additional tip, Rebecca!

 

As I test, I just make notes for which email variation I used for different submission scenarios, so I can confirm if the desired actions and processes occurred as planned.

 

This is an awesome time saver for testing and auditing forms, as well as campaigns and programs. Enjoy!

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

 

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

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

2. Insert the URL

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

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

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

 

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

bradh

Custom Data Objects

Posted by bradh Jul 31, 2012

Custom Data Objects are used to store data that may be related to a Contact or Company's record. Some examples of data you might want to store in a custom object include: Product Purchase history, Registrations, Warranty Expiry.  Custom objects can be synchronized with your CRM system on a scheduled basis.


Creating Custom Data Objects

To create a custom data object:

  1. From the navigation toolbar at the top of the page, select Contacts > Custom Objects, then click the Events dropdown and choose New Custom Data Object.
    cdo-1.png
  2. Enter a Display Name. This is the name of the Custom Object (also referred to as a Data Card Set)
  3. Enter a Description. This is information to help you and your colleagues determine the use of this Custom Object.
  4. If desired, select a folder to store your Custom Object in.
  5. Choose the Entity Type. This is either Contacts or Companies, and your Custom Object will be linked to whichever you select.
  6. Select the Entity Field. This is the field used to create a unique match to your selected entity.
  7. When you have set these parameters, click Next. The Custom Object is created, and you are taken to the Data Card Fields section.
  8. Select the Data Card Fields dropdown at the top right of the screen. Select Add New Field. Note: You can also add existing contact fields, or fields from existing forms. Enter your desired parameters, and click Save and Close. In most cases you will want to be sure to create a field for email address, as this will be your unique identifier, as set in step 6 above.
    cdo-2.png
  9. Add additional Data Card Fields as required.

Adding Data Cards to Custom Data Objects

To add a data card:

  1. Click the Data Card Set dropdown at the top right of the screen.
    cdo-3.png
  2. Select New Data Card to manually enter information, or select Upload Data Cards to upload a list of data cards as you would with contacts. When manually adding your data cards, be sure to click Save and Map to tie your data card to your contact record matching on email address. Similarily, when uploading be sure in step 4 of the wizard to select Map data cards.

Writing Form Submission Data to Custom Data Objects

To write form submission data to a data card:

  1. Navigate to your form's processing steps - Assets > Forms > Open an Existing Form > Processing
    cdo-4.png
  2. Click the + icon and select Update Custom Data Object - With Form Data
    cdo-5.png
  3. Edit your new processing step as you would with the standard Update Contacts - With Form Data step.
    cdo-6.png

Example of Using Custom Objects

You can use Custom Objects and Data Cards to store additional information for your contacts, without cluttering up the contact record. This helps to keep your database clean and organized, and provides the opportunity to store data which will later help you to segment your contacts. The following video provides an example of how Custom Objects are useful.

 

Example 1: Storing Product Warranty Information for Purchased Products.
A customer purchases a product from you, and at the same time purchases a 2-year extended warranty. You would like to store this warranty information in your database, but because there could be many purchases by one client, you do not want to clutter your contact's record. Instead, you store this warranty information in a Custom Object.

 

Video 1 - Creating your Custom Object

Video 2 - Creating your Form and mapping to your Custom Object

Video 3 - Testing the Form, and viewing the newly created Data Card in the Custom Object

 

Example 2: Storing Product or Communication Preferences from CRM

You have contact records in your CRM system which hold a large number of preference related fields. You have check boxes for communication preferences, product preferences, likes, dislikes, etc. You don't want to clutter your contact records in Eloqua, so you store this information in a Custom Object. Because Custom Objects can be created automatically via Auto Sync, this makes keeping your contacts' preferences up-to-date a real breeze. Create your Custom Object, add your fields, create a new Data Source and Auto Synch, and that's all there is to it!

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

 

Static HTML App

 

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

 

In order to use the Static HTML app, you will need to be registered at http://cloudconnectors.eloqua.com

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

What is the Static HTML App?

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

 

Static HTML App Components

The Static HTML app consists of a single Cloud Component

 

How to Install the Cloud App

 

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

 

Using the Components on a Landing Page

 

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

  

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

 

static1.png

 

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

 

static2.png

 

 

 

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

 

CCLogin.PNG

 

Enter your cloudconnectors.eloqua.com credentials and click Log in.

 

The following screen will appear:

static3.png

 

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

 

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

 

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

 

 

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

Rolling out Eloqua to a Global Enterprise

 

Marketing-Command-Center-Map-of-Earth.jpg


You’ve labored for months, maybe even years, working at a large enterprise company in finally securing budget to purchase Eloqua.

 

Despite all the internal challenges, approval hoops, endless committee meetings and ROI calculators, it is finally, finally a reality. Not only is it approved but the shiny new tool is now installed! It’s been a long, long road but it’s time to celebrate!

 

But wait.  Even before the champagne stops bubbling it starts. Word gets out. Suddenly C-Level wants it, sales divisions all want it, every marketing division and business unit wants it, APAC wants it, Latin America wants it, EMEA wants it, partners, distributors and resellers all want it…in short, now everyone wants it. And they all want it NOW. In fact everyone is suddenly desperate to start using it.

 

SCENARIO 1:

 

You start by kindly saying NO. You explain that you need time to formulate new processes, provide training, manage the change. But no one takes NO for an answer.

 

“These are desperate times and we NEED it NOW!”, is the mantra from above and below. So after constant bombardment and pressure, you finally give in and (gulp) release it to the world. You are everyone’s best friend.

 

Fast forward 1 year later…

 

The data apocalypse is in full swing, leaving a huge mess. Bad data is overwriting good data. Data is deleted. CRM integration is full of errors and unresolved failures.   Divisions upload bad lead lists because they can no longer nurture and grow their own. Hard bounce rates go through the roof. Deliverability is down the drain. Files are all over the place, with new folder structures appearing daily.  What’s left of the good database is being bombarded with multiple emails from multiple divisions offering multiple deals. Subscription management is nonexistent as no one could ever agree on the right process. Unsubscribes are rampant. No one knows where to allocate budget. Sales and marketing no longer have confidence in the tools they used to use. Sales must revert back to the old days of mostly cold calling, prospecting for leads. A global Eloqua “Do-Over” is eminent. You have moved on.

 

 

SCENARIO 2:

 

You somehow manage to hold your ground. No means NO. You launch the tool systematically one division at a time. You work out the kinks. You fully vet the scoring and nurturing programs. You evaluate the CRM integration for effectiveness. You wait until sales enablement tools are up and providing value. Only 1 division is best friends with you.

 

Fast Forward 1 year later…

 

Data is standardized globally. Checklists and processes are consistent. Dynamic content is maximized. Training is routine. The global marketing calendar is monitored, measured and analyzed to constantly improve message relevance and value. Sales and Marketing adore each other. Revenue goals are exceeded. Budget allocations are a no-brainer. You are everyone’s best friend (and hero). Three other companies want to hire you.

 

Summary:

 

Trust your instincts. Don’t give in and don’t give up. Ask anyone who has lived through Scenario 1. They will usually start the conversation by saying…”if there was one thing I should have done differently…”


Let’s connect on Linkedin

Let’s Connect on The Front Porch

Let’s connect on Facebook

Let’s connect on Google+

 

Steve Kellogg

Eloqua Certified Marketing Automation Best Practices Consultant, Astadia

This is the method I use to customize my forms inside of Eloqua. If anyone has other methods, please share.


Some Eloqua forms need to be customized using custom HTML. For example, one form being used for two separate landing pages, one with an offer and one without an offer. You want to segment which leads come in from the offer landing page, so you hard code a value onto both landing pages forms that indicate which page the lead is coming from.


You will use these same steps for any forms used inside Eloqua that use custom HTML.

  1. Create the form in Eloqua. If you want to pass through a custom value, include a hidden field on the form that you can pass the value into.
  2. Save the form.
  3. Generate the form HTML. Click the widget drop-down and choose View Form HTML…
  4. The form HTML will be displayed in a dialogue box. Copy everything in the Form HTML area and paste into a Notepad document.
  5. Eloqua will not accept the JavaScript that comes pre-populated in the form HTML, so you’ll need to remove it before you can use the HTML code. Search for “script” in the HTML and remove the below script tags.
    • <script src="https://secure.eloqua.com/Include/livevalidation_standalone.compressed.js" type="text/javascript" ></script>
    • <script type="text/javascript" >var field0 = new LiveValidation("field0", {validMessage: "", onlyOnBlur: true});field0.add(Validate.Presence, {failureMessage:"*"});var field1 = new LiveValidation("field1", {validMessage: "", onlyOnBlur: true});field1.add(Validate.Presence, {failureMessage:"*"});var field2 = new LiveValidation("field2", {validMessage: "", onlyOnBlur: true});field2.add(Validate.Presence, {failureMessage:"*"});var field3 = new LiveValidation("field3", {validMessage: "", onlyOnBlur: true});field3.add(Validate.Presence, {failureMessage:"*"});var field4 = new LiveValidation("field4", {validMessage: "", onlyOnBlur: true});</script>
  6. If there is custom HTML you want to add to the form, add that now. In this example, I hard coded a “Y” into the field titled “offer”.
    • I changed value=”” to value=”Y”
  7. Now the HTML is ready to be placed onto the Eloqua landing page.
  8. Open the landing page and add a new text box. This will be where you paste in the custom form HTML. Right-click the text box and choose Edit Source
  9. Paste your new form HTML into the source code and click Save.
  10. Your form should now appear in the text box.
  11. The JavaScript that was removed was for field validation. You will now need to add back the field validation in order for your required fields to remain required.
  12. Open the Page Snippet Tools and click on the JavaScript tab.
  13. Copy this JavaScript and paste it into the box.
    • <script type="text/javascript" language="javascript" src="http://img.en25.com/Web/SurePayrollInc/{87e32192-95cd-4c06-a53f-167d3716d51b}_jquery-1.7.2.min.js"></script><script type="text/javascript" language="javascript" src="http://img.en25.com/Web/SurePayrollInc/{e31aa31a-b94b-4250-9374-feac454e61c2}_jquery.validate.min.js"></script><script type="text/javascript" language="javascript"> $(document).ready(function() {jQuery.extend(jQuery.validator.messages, {required: "*",email: "*"});$("#form129").validate();});</script>
  14. Update the ID of the Form in the JavaScript. In the code above you'll be changing this line:
    • jQuery("#form129").validate(); ---> jQuery("#XXXX").validate();
    • Where XXXX is the id of the form
    • You can find the form ID in the form HTML.
  15. For each field that you want required, you'll add a class into the HTML.  For example, for the Last Name field, I changed this:
    • <input id="field0" value="<eloqua type='emailfield' syntax='LastName' />" type="text" name="lastName" class="" style="width: 50%"  />

to this:

    • <input id="field0" value="<eloqua type='emailfield' syntax='LastName' />" type="text" name="lastName" class="required" style="width: 50%"  />
    • For email fields, you can use "required email" as the class and it will validate that the email address is formatted correctly.

Fresh from the Cloud... We've just launched the "It Only Takes One" Eloqua AppCloud Sweepstakes! 

 

Newbies and power users alike, we want you to try out an app (or 2, or more!) from the Eloqua AppCloud this summer - and we're going to give you a little extra encouragement to prioritize that on your to-do list!   For more info and to review the contest rules, please visit - http://appcloud.eloqua.com/it-only-takes-one

 

appcloud_onlytakesone.png

 

Contest Closes August 1, 2012!   What are you waiting for?  Try one today!  

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

 

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

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

 

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

 

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

 

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

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

Social Sign On

This guide will go over how to install and configure Social Sign On.

Social Sign On allows visitors to your Eloqua landing page to "Sign On" to view content using Facebook, Twitter or LinkedIn. Behind the scenes, an Eloqua form will be submitted, which will capture the fields passed back from the social network, as well as determine the next action (ie - what page to display, which campaign to add the record to, etc...).

In order to use Social Sign On, you must have an account at http://cloudconnectors.eloqua.com. It's free.

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Social Sign on App Components:

The Social Sign On Apps are made up of the following Cloud Components:

  • Twitter Signon
  • LinkedIn Signon
  • Facebook Register

As well, a form will need to be created in Eloqua to capture the correct information. For information regarding form creation, please see this video:

Eloqua 10 Form Editor Overview

 

Social Sign On fields returned

Each social network provides a different set of fields. See this article for the standard fields that are returned. For each provider, it is possible to add additional, custom fields.

 

How to Install the Cloud App

Please see the following article on how to install Cloud Apps:
The specified item was not found.

 

 

Using Social Sign On

 

Creating the form:

The first thing that you should configure is the form. The form is used to map the fields from the App into an Eloqua contact, as well as determine where the contact will go after the submission.

Please see the following video on creating a form:

Eloqua 10 Form Editor Overview

 

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

Creating HTML Form name

 

You will need to create all the fields that you are capturing via Social Sign On as "Form Fields" within the design component of the form. If the social provider returns a field that you aren't interested in, just do not create one here. Ensure that you have a contact (or data card) field to map to each field returned. IF one does not exist, you can create fields by following these instructions:

The specified item was not found.

 

It is recommend that you have, at a minimum the following processing steps defined:

Update Contact - with Form Data - Here you will map the Social Sign On fields to the Contact

Redirect To Web Page - Here you will define where the submitter will go AFTER they have signed on

 

Placing it on the landing page

Social Sign On elements can be dragged onto a landing page in E10. Please see this video to familiarize yourself with Eloqua Landing Pages:

Landing Page Overview Video

 

Once the landing page has been configured, you can drag the App on, and place it wherever you would like. To find the App, click the "Cloud Components" button along the left hand side.

Cloud Components Button.png

This will pop up a "Cloud Components" selector window, where you can search for the correct app:

chooser.png

Drag the app from the selector window, and drop it onto the landing page. The actual size of the button is determined by the configuration of the app, but you can resize the window as you see fit. When you preview the page, you will see that you might need to adjust the size.

Once the app is placed, it is recommended that you save the landing page.

 

Configuring the App

To configure the app, double click on the icon on the landing page. This will pop up a window, that looks like the following:

login.png

Type in your CloudConnector.eloqua.com username and password. IF you do not have one, click the "Create User" button, and follow the instructions.

 

Once you have logged in, you will see the following screen:

login2.png

Login using your Eloqua credentials. You must have API access on your user. If you do not, please log a case with Eloqua support.

 

Once you are in, you will see a page similar to this:

 

config.png

  • Eloqua DB: This is the Eloqua install that is being connected with. It is the same as submitted on the previous screen
  • Eloqua Username: This is the Eloqua user name that is being used to connect with. It is the same as submitted on the previous screen
  • Eloqua Password: This is the password for the Eloqua user. It is the same as submitted on the previous screen
  • Component Owner: This is the cloudconnectors.eloqua.com user that created this app (ie - you!)
  • Admin Email Address: This is the email address where any admin communications (ie - API errors etc...) will be sent
  • App to Use:  Twitter and Linkedin require an "app" be set up in order to access their API. This app controls the look and feel of the 3rd party login page. Eloqua has created an app for ease of use, but it is branded as an Eloqua. IF you would like to create a custom app for your company (With custmized name and logo) please select "Define a Custom App" and see this article : Social Sign On - Custom Apps (For Twitter, and LinkedIn)
  • Icon (Twitter Only): Several different icons are available. See this article (Twitter Icons)
  • Page Title/HTML Prior to the Form/HTML After the Form/Submit Button Name/CSS Content: These fields allow you to skin the secondary form page, which will only appear IF you are asking custom fields.
  • Target Form: The data can be posted to either an Eloqua hosted form, or an external form. It is recommended that you select "Eloqua Form"
  • Eloqua Form: Here you will select the form that was created earlier
  • Form Field Mappings: This is where you map the fields from the third party (Twitter, LinkedIn or Facebook) and the custom fields you defined to the Eloqua form fields. More information below
  • Form Submit Mode: It is recommended that you leave this as the default "Production (Automatically submit form)".

 

Form Field Mapping

The form field mapping screen is broken up into 2 sections, "Standard Fields" (fields returned by the third party) and "Custom extra fields" (additional fields that are being asked on the form:

field mapping.png

To see a list of standard fields returned, please see this article (Social sign on fields returned)

To add a standard field, select the field from the drop down, and click "Add Standard Field". You will now be able to map it to any field you have defined on the form.

To add a custom field, click "Add Custom Field". Input a name and a type, and select the form field you would like to map it too.

 

Once you are done, click "Set Values".

 

You must map either an email field as a custom field OR an Eloqua Social ID as a Standard field.

 

Additional Questions?

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

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

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

Social Sign On - Installation Guide

 

Twitter:

Dark Color, Large:

https://cloudconnectors.eloqua.com/Scripts/Images/sign-in-with-twitter-d.png

 

Dark Color, Small:

https://cloudconnectors.eloqua.com/Scripts/Images/sign-in-with-twitter-d-sm.png

 

Light Color, Large:

https://cloudconnectors.eloqua.com/Scripts/Images/sign-in-with-twitter-l.png

 

Light Color, Small:

https://cloudconnectors.eloqua.com/Scripts/Images/sign-in-with-twitter-l-sm.png

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

 

What is Social Sign On?

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

 

 

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

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

 

 

What are the main differences between each provider?

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

 

 

What fields are returned?

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

 

 

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

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

 

 

How do I tie this to a contact?

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

 

 

How much does it cost?

It's free for any user of E10

 

Great, how do I get started?

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

 

 

 

 

 

 

 

What about signing on via XYZ?

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

 

 

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

Filter Blog

By date: By tag: