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.
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.
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.
Drag and Drop the Form Population 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 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.
Click Go, and the configuration screen for Form Population will then be displayed:
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)
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.
- 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.
- Next, choose the Form Field that you wish to populate.
- For Contact Data, Visitor Data, DataCard Field, or Email Group select the appropriate field from the list provided.
- For Static Value, simply enter the text that you would like to put into the form field.
- 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.
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.