This document will go through the differences in field merges between Eloqua9 and Eloqua10. You will be able to see how the source code for the different
field merges change after the update.
Eloqua9 had many different types of field merges. Below is a list of these field merges:
Eloqua9 | Eloqua10 |
Email Field Merges | Contact Field Merges |
Contact Field Merges | Account Field Merges |
Prospect Field Merges | Event Session Field Merges |
Company Field Merges | Event Field Merges |
Data Object Field Merges | Custom Object Fields Merges |
Profile Field Merges |
|
Event Header Field Merges |
|
Form Field Merges |
|
Generic Field Merges |
|
Custom Field Merges |
|
PURL Field Merge |
|
These field merges were used in different areas of the application. For example, Form, Generic, and Custom field merges were used on Confirmation Pages;
PURL field merges were used on PURL hypersites, etc. Eloqua10 was created with a more simplistic approach in mind so only one type of field merge was
retained, Email field merges. Please see the above table for Eloqua10’s Email field merges.
Below is a comparison of the HTML code for Eloqua9 field merges and Eloqua10 field merges:
Field Merge | Eloqua9 Source Code | Eloqua10 Source Code |
Email Field Merges (E9, E10) | <span class="eloquaemail">Email</span> | <span class="eloquaemail">Email</span> |
Contact Field Merges (E9, E10) | <span class="eloquaemail">Contact</span> | <span class="eloquaemail">Contact</span> |
Prospect Field Merges (E9) | <span class="eloquaemail">Prospect</span> | N/A |
Company Field Merges (E9) | <span class="eloquaemail">Company</span> | N/A |
Data Object Field Merges (E9, E10) | <span class="eloquaemail">Data_Object</span> | <span class="eloquaemail">Custom_Object</span> |
Profile Field Merges (E9) | <span class="eloquaemail">Profile</span> | N/A |
Event Header Field Merges (E9) | <span class="eloquaemail">Event_Header</span> | N/A |
Form Field Merges (E9) | <span class="eloquaemail">F_ Form</span> | N/A |
Generic Field Merges (E9) | <span class="eloquaemail">Generic</span> | N/A |
Custom Field Merges (E9) | <span class="eloquaemail">Custom</span> | N/A |
PURL Field Merge (E9) | <span class="eloquafieldmerge">contact</span> | N/A |
Event Fields (E10) | N/A | <span class="eloquaemail">Event_Fields</span> |
Event Session Fields (E10) | N/A | <span class="eloquaemail">Event_Session</span |
Account Field Merges(E10) | N/A | <span class="eloquaemail">AccountFM</span> |
If any type of field merge other than an Email Field merge is used in Eloqua9 please make sure to update the asset to contain Email Field merges before
updating to Eloqua10. If the field merges are not changed in advance the field merge will not work after the update. You will still see the field merge in
the HTML, but when the asset is viewed no value will be inserted into the field merge, it will remain blank.
Activity Driven Content (ADC) and Include Content
ADC in Eloqua9 will migrate to Dynamic Content in Eloqua10. Include Content and Shared Content from Eloqua9 will convert into Shared Content in Eloqua10.
Below you will see the changes in the source code:
| Eloqua9 Source Code | Eloqua10 Source Code |
ADC | <ELOQUA dynamicContentID="72" entity="dynamicContent" /> | <span elqId="2" elqType="DynamicContent" class="remove-absolute" style="display: block" ></span> |
Shared Content | <SPAN class="eloquaincludecontent">Include_Content</SPAN> | <span elqId="115" elqType="Section" class="remove-absolute" style="display: block" ><Items within the shared content.><br></span> |