Skip to main content
Sign in

Interpreting Eloqua Post Out Responses & Common Errors

Emily Higgins
  • Updated

Relevant to: Demand Acceleration Platform

Routine monitoring to check for errors is highly recommended to ensure leads are successfully posted to integrated systems. This can be done by reviewing the Eloqua Response, which is received by the Demand Acceleration Platform whenever a lead post out is attempted.

The Eloqua Response can be found in both the testing modal (when testing your integration) and as a column in a post out log report (generated once the Source/Campaign has started to collect data).

Eloqua form responses can be customized, so it is recommended to work closely with your Marketing Ops team to understand your responses and troubleshoot any errors.

 

 

Understanding the Eloqua Response

Whenever you send a test lead or routinely monitor post out lead flow, you are checking two things:

  • The request - the data that was sent to Eloqua.
  • The response - the information that Eloqua sent back to the Demand Acceleration Platform.

 

The request

In the Test Integration modal (displaying Sandbox Test Results) - see the Request section.

dap-postouts-interpretingeloqua-01.png

 

In a Post Out Log Report  - see the RequestContent column.

dap-postouts-interpretingeloqua-03.png

 

To read the request code:

  • This displays the Eloqua field name and corresponding value that was sent into it.
  • Review this section in detail to confirm all the fields have attributed values and that any list value mappers are working properly.

Example: field and value highlighted in bold.

"elqFormName=IntegrateForm&elqSiteID=123456789&elqCustomerGUID=&elqCookieWrite=0&
firstName=Jane&lastName=Doe&emailAddress=test%2b8%40integrate.com"

 

The response

The response code displays the exact response that was received from Eloqua. It will look different depending on whether or not the test lead has been successfully received and/or if a custom response has been set up. 

Within each Eloqua form, responses (success and error indicators) can be customized by your Marketing Ops team. Sometimes these are set up as redirects to a webpage that will return the associated HTML as the responses. Below are examples of a few common responses and how to read them.

Eloqua form responses can be customized, so it is recommended to work closely with your Marketing Ops team to understand your responses and troubleshoot any errors.

In the Test Integration modal (displaying Sandbox Test Results) - see the Response section.

dap-postouts-interpretingeloqua-02.png

 

In a post out log report - see the ResponseContent column.

dap-postouts-interpretingeloqua-04.png

 

A successful response

Although they can be customized, successful responses typically contain the value submit.

Examples: values indicating success are highlighted in green.

"\r\n<script type='text/javascript'>\r\ndocument.location.href = 'https://s123456789
.t.eloqua.com/e/DefaultFormSubmitConfirmation.aspx';\r\n</script>\r\n"
<!DOCTYPE html><html><head></head><body bgcolor="#FFFFFF" class="">
<div style="MARGIN: 60px" align="center" class="">

<!-- CONFIRMATION PAGE TITLE -->
<div style="FONT-WEIGHT: bold; FONT-SIZE: 14pt; WIDTH: 400px; FONT-FAMILY: Tahoma, 
Arial, Helevtica" align="left" class="">
<img height="50" src="http://now.eloqua.com/EloquaImages/ConfirmationPage/Success
.gif" width="32" align="left" border="0" class=""> Your information has been &nbsp;
submitted successfully!
</div>

<!-- CONFIRMATION PAGE INFORMATION -->
<div style="WIDTH: 400px" align="center" class=""><br></div>

</div>
</body></html>

Your response may not look like this and still be a success.
Eloqua form responses can be customized, so it is recommended to work closely with your Marketing Ops team to confirm and help troubleshoot if needed.

Success! Now check that the lead has been received in Eloqua and confirm that it is properly routed and the data is complete.
If you don't have access to Eloqua, collaborate with your system admin to confirm that test lead(s) have been received in Eloqua.

 

A failed response / unsuccessful code

Although they can be customized, unsuccessful responses typically contain the value error.

The error reason will be included in the response code; common errors can be seen in the table below.

Example: values indicating a sample failed response highlighted in red.

"<body bgcolor=\"#ffffff\">\r\n<script language=\"JavaScript\">\r\n<!--\r\
nfunction loadTrainingWindow(strURL){\r\n\tvar wndTrainingWindow;\r\n\
twndTrainingWindow = window.open(strURL, \"PopupWindow\", \"personalbar=no,
toolbar=yes,status=no,scrollbars=yes,location=no,maximize=yes,resizable=yes,
menubar=no,width=550 ,height=445\") ;\r\n\twndTrainingWindow.focus();\r\n}
\r\n//-->\r\n</script>\r\n<div align=\"center\" style=\"margin: 60px;\">\r\n
\r\n<!-- CONFIRMATION PAGE TITLE -->\r\n<div align=\"left\" style=\"width: 400px; 
font-size: 14pt; font-family: Tahoma, Arial, Helevtica; font-weight: bold;\
">\r\n<img src=\"http://now.eloqua.com/EloquaImages/ConfirmationPage/error.gif\" 
width=\"32\" height=\"50\" border=\"0\" align=\"left\">  The error response reason 
will be included here*.\r\n</div>\r\n\r\n<!-- CONFIRMATION PAGE INFORMATION -->
\r\n<div align=\"left\" style=\"width: 400px; font-size: 10pt; font-family: Arial, 
Helevtica; padding-left: 45px; padding-top: 10px; padding-right: 45px;\">\r\n<p>
</p>\r\n</div>\r\n\r\n</div>\r\n</body></html>"

Eloqua form responses can be customized, so it is recommended to work closely with your Marketing Ops team to understand your responses and troubleshoot any errors.

 

 

Error responses seen most often in the Demand Acceleration Platform

* The table below shows the error responses that are most commonly encountered in the Demand Acceleration Platform. If you have received one of the responses noted here, follow the action as described in the solution column.

If the Source is live and you are reviewing this in a Post Out Log Report, first check all instances of the Lead ID to see if a successful post out has been subsequently recorded.
If not, follow the recommendation in the 'Suggested solution' column below.

Response Description Suggested solution 
[Field] ... This field 
is required.
 The test lead is missing a value in a required field. Add a value to the required field in the test lead form. 
Email Address... A valid 
email address is required.
 The test value contains an invalid email format. Check the email address used in the test lead is correctly formatted (xxx@xxx.xxx). 
[Field]... Invalid length 
for field value.
 The test value contains an invalid number of characters.

In Eloqua, check the validation for the form field and adjust if needed.

See Configuring form fields in the Classic Design Editor.

 
[Date field]... Value 
must be a valid date.
 The test value contains an invalid date format. In the Demand Acceleration Platform, check the field is set as a date field and matches the format required in Eloqua. 
A problem has occurred 
with this form. 
The system administrator 
has been notified...
 The test lead contains an elqFormName value that does not exist. In the Demand Acceleration Platform, check that the Eloqua form name value is correct in the integration field mapping section.
The test lead contains an incorrect elqSiteID in the field mapping. In Eloqua, check that the elqSiteID value has been accurately copied.

 

Speak with your Customer Success Manager if you need help understanding or correcting an error.

 

 

Recommended Reading

 

For more help, get in touch with our Support Team or your Customer Success Manager.

Related articles