Skip navigation

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

 

Form Population Cloud App

 

The Form Population Cloud App allows the marketer to pre-populate a form that exists on the landing page.  When dragged onto the page and configured, the Cloud Component will populate hidden or shown form fields with contact data, visitor data, static values, or query strings.  Note: In order for the Contact data or Visitor data to work, the visitor to the page must be known to Eloqua.

 

This article will describe the individual pieces of the Form Population Cloud App, how to have it enabled in 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 App, you must be registered at cloudconnectors.eloqua.com.

 

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

 

Form Population Cloud App Components

 

The Form Population Cloud App consists of the following Cloud Component:

  • Form Population - allows you to auto-fill form fields with data from a visitor, contact, query strings, or static values.

 

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

 

How to Install the Cloud App

 

The Form Population 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.

FormPop1.png

Drag and Drop the Form Population component onto the landing page:

FormPop2.png

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

CC_Login.png

 

Enter your cloudconnectors.eloqua.com credentials and log in.

 

A screen will appear asking for your Eloqua credentials.  These credentials will be used to make calls to the Eloqua API to retrieve Visitor Profile and Contact data.

FormPopCreds.png

 

Click Go, and the configuration screen for Form Population will then be displayed:

FormPopConfig1.png

 

On the configuration screen, select the form that you want to pre-populate (NOTE: this form must also be placed on the same Eloqua landing page as the component).

 

If you would like to map a DataCard field, you will need to select the Custom Data Object you wish to pull the field(s) from.  If an object is selected from the list, the following additional settings will be displayed:

(NOTE: this step is completely optional, and is only required if you wish to population form fields with information from Custom Data Objects)

FormPopConfig3.png

 

Due to the fact that a contact can have multiple DataCards mapped to them in a set, we will need to use a rule to determine which one to use.

 

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

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

 

We also need to map the Email Address so that the component can look at the contact visiting the page, and find any DataCards mapped to them.

 

Now that the component knows which Custom Data Object to look in, the Email Address field for determining mapped objects, and a Selection Rule and Field to Evaluate, it is possible to pull a field from the object to pre-populate a form field.

 

Click Save Settings, and then click Map Fields.

 

The Edit Form Population Mappings screen will then display.

FormPopMappingsNew.png

 

 

  1. Start by selecting a Type.  Choices are as follows:
    • Contact Data: fields from the Eloqua contact record.
    • Visitor Data: fields from the Eloqua visitor profile.
    • Static Value: a value that you provide.
    • Query String: a value that you pass to the landing page on the query string.
    • DataCard Field: fields from an Eloqua DataCard that is linked to a contact.
    • Email Group:  email groups from Eloqua.
  2. Next, choose the Form Field that you wish to populate.
  3. For Contact Data, Visitor Data, DataCard Field, or Email Group select the appropriate field from the list provided.
  4. For Static Value, simply enter the text that you would like to put into the form field.
  5. For Query String, enter the name of the parameter that will be passed to your page, without the "=" sign.

       (NOTE: The app supports populating checkboxes from static values.  If the form field you are populating is a checkbox, enter a Data Field value of true to check the box, or false to un-check it)

 

Once your mappings are completed, click Save and the screen will close, returning you to the configuration page.

 

The count of mapped fields will be shown next to the Map Fields button.

FormPopConfig4.png

 

Note: Clicking the Preview button, with the email address of a contact that already exists in your Eloqua instance, will pop up a window that will be blank.  Since this is a non-visual component, you will need to view the page source to see the results of your setup.  The page source will show you the code that will be inserted into the landing page to fill in the form fields.

 

Now that the configuration is complete, when the landing page is rendered, the fields should be filled with the data that you set up in the mappings.

 

Things to note:

  • This is a non-visual component, meaning you do not actually see anything on the page.  (Note: If you view the page source, you will find the code returned by the component inside the CloudComponentInstance span tag).
  • The component does not actually submit the form, it simply populates the form fields with data.
  • The Contact Data and Visitor Data options will only work if the Visitor or Contact is known to Eloqua.  For DataCard Field and Email Group the Contact must be known.
  • In order to bring back a DataCard field, the contact must have a DataCard mapped to them in the chosen set.

In order to obtain the previous page URL on a form submission a javascript function needs to be added to the external webpage that hosts the Eloqua integrated form. The Javascript extracts the "previous page" URL address and populates a hidden form field. The hidden form field will need to be added to the page. The field is then passed on the form submit to Eloqua.


To achieve this the following steps need to be made:


1) The webpage hosting the Eloqua form must have the below JavaScript code added. The code obtains the previous "from" URL.

 

<script type='text/javascript' language='JavaScript'>
function refer()
{
    if (document.referrer != "") {
        var referringURL = document.referrer;
        document.forms["aspnetForm"].elements["ReferencePage"].value = referringURL;
    }
}
</script>



2) The same JavaScript must be called as part of the page initiate.

 

<script type='text/javascript' language='JavaScript'><!--//
window.onload = initPage;
function initPage(){
    if (this.GetElqCustomerGUID)
    {
        document.forms["aspnetForm"].elements["elqCustomerGUID"].value = GetElqCustomerGUID();
    }
   refer(); // To be added to the current initPage function
}
//-->
</script>

 

3) A hidden form field that is populate with the "Previous Page" URL must be added to the webpage. The name of the field must be "ReferencePage" as this is the field name used in the JavaScript function. If it is changed here the JavaScript must be updated.

<input type="hidden" name="ReferencePage" value="" />


4) The new form field is to be included in the form submit sent to Eloqua. Therefore, a new Hiddenfield must be added to the Form within Eloqua. The name of the form field must be the same as the form field in Eloqua. In this example the name is ReferencePage

Inline image 3

 

Once all the configuration is complete, the testing will result in the users previous page included in the form submission. This can be viewed under the "Form Submission Data" option in the menu.

Inline image 4

A new feature has been added to cloudconnectors.eloqua.com, that allows you to easily tell if your app is enabled or not.

 

First, some quick background. When you are configuring any app that is hosted on cloudconnectors.eloqua.com, you must configure it, then enable it when you are done, so that it executes. This step was often missed. So, now there is a queue to remind you to enable the step.

 

See how the Credentials tab is red, and has a little red dot? That means it is not currently enabled:

not enabled.png

So, to enable the app, click the "Credentials tab". Under "Settings", click "Enable Step":

make enabled.png

Now, the "Credentials" tab should have changed to green:

enabled.png

Hi!

I've been trying to find a way to see who has downloaded PDF documents that have been placed in E10 Component Library File Storage.

I have placed a document on a landing page without a gated form. In the File Storage there is a Tracked Url link but I have no idea how to see which contacts have downloaded/opened the document.

 

Do I need to use a query sting or create a redirect page for the document? If so, the lack of simple document upload reporting is a major system handicap. There should be an Insight report for documents or a possibility to include the document in the campaign canvas as a reporting item.

Follow these steps for externally hosted forms where the form data is re-posted to Eloqua servers from a server-side form processor. In this case it's not possible to get the cookie from the client's machine so the following instructions provide the necessary code to place on the form page to send the unique ID along with the form data to Eloqua. This ensures that the visitor submitting the form is linked to the Eloqua contact record so you can capture and track their digital body language.

 

Notes:

  • Recommendation – Create a copy of the externally hosted form you will integrate with and create a test page to get functionality in place and tested before it goes to production.
  • You will notice that there is a Form Integration Wizard in Eloqua.  The scripts provided in this Wizard currently need to be updated, so please use the instructions below until they have been updated.  Theoretically, you could use the Form Integration Wizard to build your Eloqua Form… but you will still want to use the scripts and QA process below to implement.
  • This applies if you are using the asynchronous web tracking scripts generated after Dec 11, 2011.

 

Step 1: Build the back-end Eloqua Form.

  1. Create New Form
  2. Turn pre-population off
  3. Create Fields that mirror fields on web form
  4. Set the HTML name (go to gear box, settings – ‘generate; use; save’)
  5. For each form field, set the HTML field name (Field Settings; Advanced Settings).  To retrieve HTML field name, you can ‘view source’ of web page where form is hosted, or request from web resource.

 

Step 2:

Provide the following instructions to the person making the updates on the webpage. You will need to update the ‘elqFormName’ value with each form (this is the unique Eloqua Form ID), the ‘elqSiteID’ will remain constant (this is your instance of Eloqua).  To retrieve the ‘elqFormName’ and ‘elqSiteID’ go to the Eloqua Form, click the gear box, select ‘View Form HTML’ and select ‘Integration Details’.  You will see that you need to plug the ‘elqFormName’ value in twice below.

 

     a) Post URL for the form: action= s<siteid>.t.eloqua.com/e/f2 (supports both http and https posts)

 

     b) Add the following on the initial HTML page within the <Form> tag (no specific location needed so long as they are included as hidden fields on the initial HTML form page and are posted upon the initial post):

 

<input type="hidden" name="elqFormName" value="ENTER ELOQUA HTML FORM NAME" />

<input type="hidden" name="elqSiteId" value="ENTER SITE ID" />

<input type="hidden" name="elqCustomerGUID" value="">

<input type="hidden" name="elqCookieWrite" value="0">

 

     c) Then, place the following code anywhere after the main tracking scripts appear on the page:

 

var timerId = null, timeout = 5;

function WaitUntilCustomerGUIDIsRetrieved() {

if (!!(timerId)) {

if (timeout == 0) {

return;

}

if (typeof this.GetElqCustomerGUID === 'function') {

               document.forms["ENTER ELOQUA HTML FORM NAME"].elements["elqCustomerGUID"].value =

GetElqCustomerGUID();

return;

}

timeout -= 1;

}

timerId = setTimeout("WaitUntilCustomerGUIDIsRetrieved()", 500);

return;

}

               window.onload = WaitUntilCustomerGUIDIsRetrieved;

_elqQ.push(['elqGetCustomerGUID']);

 

 

This code will execute upon the page loading and will wait until the visitor's GUID has been retrieved from the Eloqua servers and then insert it into the elqCustomerGUID form element.

Be sure to replace "ENTER ELOQUA HTML FORM NAME" with the actual html form name as setup in the Eloqua application.

 

 

Step 3: Testing and Verification

Once you submit the form, the first place to check is ‘View Submission Data’. On the Eloqua Form, click the Gear Box, and go to ‘View Submission Data’.

Verify that the form was posted and that each field was received by Eloqua.

screenshot1.png


The next step is to verify that your Form Processing Steps are working as expected.

Wait ~20 minutes and check the Contact to confirm the Form Activity is logged on the Contact Record.

 

Step 4:

Once your QA is complete, ask your IT resource to apply the scripts to the ‘live page’ and re-run QA.

 

These instructions apply to both Eloqua9 and Eloqua10 and to all product levels (Express, Team, Enterprise), although the specific navigation and screenshots provided are specific to Eloqua10.

So what is a Custom Data Object record? Custom Data Object (CDO) records or CDOs store data elements in the Eloqua system that are not part of your account or customer contact record. Custom Data Object records can also go by the name data cards.

 

Custom Data Objects allow you to define data elements that share one-to-many relationships with a contact or an account record.  This data is stored, linked to the contact or account record and made available for many other uses (see below). Custom Data Object records are created in Custom Data Objects (also known as Custom Objects or Data card Sets).

 

Custom Data Object Examples:

  • Point of Sale Information
  • Product Purchase History (Mary Jane has product X, Y and Z)
  • Licensing/entitlement information
  • Subscription/membership data
  • Event/webinar attendance data
  • Social media data associated to a contact
  • Opportunity data, Warranty, Service Contracts, Competitive Intel, BU Segmentation Data (ie RUM/RAD)

 

Custom Data Object Example = Subscription Renewal Information
Custom Data Object fields in the Subscription Renewal object could be:
Renewal Product Name
Renewal Date
Renewal Fee

 

Uses for Custom Data Object Records:
By storing and accessing this data, workflows can be better defined and aligned to what the prospect or customer is interested in.

 

  • Segment and filter contacts for inclusion into an email campaign.  For example, point of sale information stored in a data card shows that Mary Jane bought tickets to Bon Jovi, so now we can offer similar tickets.
  • Build out more sophisticated lead scoring (if they own product ZZ, score higher)
  • Build rules for lead routing (if product X and product Y, send lead/contact to PowerQualifierGroup)
  • Segment into specific nurture or drip campaigns (if contact has product X, drop into Campaign CrossSell)
  • Remove from a specific nurture campaign if a contact has an opportunity stage of ‘sales qualified lead’.
  • Send emails to contacts that have tweeted about a certain topic
  • Send follow up communication to webinar attendees based on the time they spent at a webinar (used as part of a Cloud Connector process).
  • Send subscription renewal emails with all the relevant information including the renewal date, product and renewal fees.

 

Recommendations:

  • How many Custom Data Objects can you have? There is no defined system limit on the number of Custom Data Objects allowed
  • How many records are recommended?  The smaller the better for optimum performance.  Here are some good rules to go by:
  • 1M to 3M per object is good and reasonable
  • 3M – 6M is acceptable
  • 6M- 10M is fine, but if you can keep it below this threshold, that’s better.
  • It is not recommended to go over 10M.
  • How many records can I have in total?  It is not recommended to exceed 20 million
  • You should design a process to clear out old data cards to keep them below the numbers mentioned above.

 

Posts to reference:

 

Recommended Eloqua Education Courses*:

  • *Course: Program Builder – not specific to custom data objects, but most people will use CDOs when building out programs in Program Builder.

* Requires an Eloqua All Education pass

There are times when you just need to send an email blast to a list regardless if they’ve unsubscribed before.  In Eloqua, it’s a default rule that the system will not send any email to Global Unsubscribes or group level unsubscribes.  However, there are those one-off times that you just need to send the email out anyway. There is the option of using Quicksends but this you’ll have to do this individually to every “unsendable” contact which gets tedious if you have lots of them.  So, what we’re looking for is an automated way of temporarily overriding the Unsubscribe status of a contact – send them an email – then reset their status back to what it originally was.

 

What you’ll need:

  1. A shared list or contact group that includes “unsendable” contacts
  2. An email to send out
  3. 2 Filters – one that looks for global unsubscribes and another that looks for email group unsubscribes (for the email group of the email to send out)
  4. A program to do the job.

 

What to do:

 

  1. Build this Program
    send-to-unsubs.jpg
  2. Feed your shared list / contact group into step 100
  3. Activate your program in standard mode.

 

===

MikeGarcia’s Chocolate Factory … probably not the best practices – but good enough!

MG-003-20120411

kirkdiedrich

Re: The April Release

Posted by kirkdiedrich Apr 6, 2012

I've seen the Eloqua Roadmap for 2012, which is great for high-level improvements to requested marketing functions and whatnot, but is there a more down-and-dirty, nuts-and-bolts version of what's going to be in the release for the production/development side of users?

 

Like, improvements to the HTML Editor, improving/simplifying data uploading, working out known bugs, etc.?

Well it certainly is not 1939 and this story doesn’t tell about a single man's effect on American politics as the title conveys, but it is about a bit of the things I did see last week during one of my visits to Washington D.C.


 

For the entire month of March I was in and out of beautiful Washington D.C. meeting with different groups and people who have an effect on marketing and privacy. As you know I was just there for a meeting a few weeks ago where I spent the day at the United States Institute of Peace in Washington D.C attending the EU Conference on Privacy and Protection of Personal Data which today still has a ring in my ear of how fragmented we as a world are when it comes to government imposed privacy regulations that affect the Internet.

 

 

However, last week's visit seemed to focus on “local” issues. The United States Federal Trade Commission (FTC), the nation’s chief privacy policy and enforcement agency for 40 years, issued their final and long awaited industry privacy report. I also did a long day on Capitol Hill (in the middle of the health care debates) with Congresspersons and Senators who are tackling privacy in their committees or offices to help them understand and shape our and customers online marketing landscapes.


 

On March 26, the DMA hosted its annual policy conference, DMA in DC 2012 in which we heard from representatives of the nation’s enforcers of consumer protection laws. We had dinner with Representative Mary Bono Mack (R-CA) who heads the House Energy and Commerce subcommittee taking the lead on the privacy issues. In her remarks she said that Congress has considerable work to do to understand data privacy issues before deciding what, if any, sort of privacy legislation is needed. She did praise us for hard work on self-regulation and she did recognize the need for more security regulations to address the real problems with Internet.


 

That same day in the morning the FTC released their report and within thirty (30) minutes of that release we were treated to a lunch and keynote from FTC Commissioner Julie Brilll covering the report. In her note she said.


 

  • The FTC would be vigilant in enforcing self-regulatory codes of conduct among companies in the area of data privacy
  • A company’s failure to live up to a voluntary code of conduct would act as a scarlet letter in an FTC enforcement action which we’ve already seen heavily in the last year.
  • They were interested in developing of sector-specific codes of conduct, meaning tackling specific issues with specific regulations vs. umbrella regulations.

 

You can see her entire keynote in more detail here

 

To save me time here, I am copying from the FTC site here. The final privacy report also expands on a preliminary staff report the FTC issued in December 2010. The final report calls on companies handling consumer data to implement recommendations for protecting privacy, including:


  • Privacy by Design - companies should build in consumers' privacy protections at every stage in developing their products. These include reasonable security for consumer data, limited collection and retention of such data, and reasonable procedures to promote data accuracy. This is a wonderful concept invented and championed by Ontario Privacy Commissioner Ann Cavoukian and one in which Eloqua is taking head on by having her present it to our engineers last year and us putting into play process to help manage the concept.
  • Simplified Choice for Businesses and Consumers - companies should give consumers the option to decide what information is shared about them, and with whom. This should include a Do-Not-Track mechanism that would provide a simple, easy way for consumers to control the tracking of their online activities. As you know, Eloqua has already done things like this with our Strict Mode release early last year.
  • Greater Transparency - companies should disclose details about their collection and use of consumers' information, and provide consumers access to the data collected about them. This has always been a forefront thinking here at Eloqua and one that we push to many of you to highly consider.

 

The final report also notes that the FTC received over 450 comments on the staff's preliminary recommendations. Based on technological advances and industry developments since the December 2010 staff report and in response to the comments. The report refines the guidance for when companies should provide consumers with choice about how their data is used. While Congress considers privacy legislation, the Commission also urges individual companies and self-regulatory bodies to accelerate the adoption of the principles contained in the privacy framework.

 

Over the course of the next year, Commission staff will work to encourage consumer privacy protections by focusing on five main action items:


  • Do-Not-Track - The Commission commends the progress made in this area: browser vendors have developed tools to allow consumers to limit data collection about them, the Digital Advertising Alliance has developed its own icon-based system and also committed to honor the browser tools, and the World Wide Web Consortium standards-setting body is developing standards. We are confident that we as an industry can continue the self-regulatory efforts without legislation and the FTC agrees in their report
  • Mobile - The FTC urges companies offering mobile services to work toward improved privacy protections, including “short” and meaningful disclosures. To that end, it will host a workshop on May 30, 2012 to address how mobile privacy disclosures can be short, effective, and accessible to consumers on small screens. If you haven’t seen TRUSTe’s mobile-optimized privacy notice, I suggest you check it out here
  • Data Brokers - The Commission calls on data brokers to make their operations more transparent by creating a centralized website to identify themselves, and to disclose how they collect and use consumer data. In addition, the website should detail the choices that data brokers provide consumers about their own information. As a personal note, I’m all for this idea to some extent. As an individual who tends to get a lot of junk and bulk marketing I want to know more about who has my information and how to prevent them from selling it. I’ve never been a huge supporter of data brokers whether it is legal or not. However, in context of what the FTC proposed here this will be a difficult thing to do as a centralized service.
  • Large Platform Providers - The report cited heightened privacy concerns about the extent to which platforms, such as Internet Service Providers, operating systems, browsers and social media companies, seek to comprehensively track consumers' online activities. The FTC will host a public workshop in the second half of 2012 to explore issues related to comprehensive tracking. I know the guys at The Messaging Anti-Abuse Working Group (MAAWG) will be watching this one as it could affect feedback loops and other legal and effective anti-spam services they use.
  • Promoting Enforceable Self-Regulatory Codes - And again, the FTC will work with the Department of Commerce and stakeholders to develop industry-specific codes of conduct. To the extent that strong privacy codes are developed, when companies adhere to these codes, the FTC will take that into account in its law enforcement efforts. If companies do not honor the codes they sign up for, they could be subject to FTC enforcement actions.


 

The following day, I joined DMA’s Government Affairs team and other member companies for a series of Capitol Hill meetings, advocating directly on the issues of privacy and data security proposals. We with the offices of Senators Susan Collins (R-ME), Al Franken (D-MN), Mark R. Warner (D-VA), Michael F. Bennet (D-CO), Tom Carper (D-DE), Jim DeMint (R-SC), Pat Toomey (R-PA), John F. Kerry (D-MA), Scott Brown (R-MA), Joe Lieberman (I-CT), as well as Representatives Cliff Stearns (R-FL), G. K. Butterfield (D-NC), Marsha Blackburn (R-TN), John B. Larson (D-CT), Stephen Lynch (D-MA 9), Elijah Cummings (D-MD 7) and Adam Kinzinger (R-IL).


 

All in all, another wonderful trip to Washington D.C. in which we heard some great news about our ongoing efforts to build transparent and easy choices for consumers in many of our platforms. Most officials seem very happy with the way things are going and asked us to continue to push our objectives forward without the immediate need for government imposed regulations. There is lots more work to be done here though so not much time to relax.

Filter Blog

By date: By tag: