Skip to main content
Sign in

Using Outbound Forms - Interpreting HubSpot Post Out Responses & Common Errors

danny.latour
  • Updated

Relevant to: Demand Acceleration Platform

This article relates to the use of Outbound Forms to set up an integration with HubSpot.
If you are unsure which integration method to use, see HubSpot Post Out Methods.

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 HubSpot Response, which is received by the Demand Acceleration Platform whenever a lead post out is attempted.

The HubSpot 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).

HubSpot 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 HubSpot 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 HubSpot.
  • The response - the information that HubSpot sent back to the Demand Acceleration Platform.

 

The request

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

dap-postouts-interpretinghubspot-01.png

 

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

To read the request code:

  • This displays the HubSpot 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.

"firstname=Jane&lastname=Doe&email=test%2b1%40integrate.com&company=Company+Inc.
&industry=Manufacturing&jobtitle=Budget%2fAccounting+Analyst+II"

The response

The response code displays the exact response that was received from HubSpot. 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 HubSpot 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.

HubSpot 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-interpretinghubspot-02.png

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

A successful response

If a post-submission form has been set up in HubSpot, the response will include the associated HTML. Successful responses can also be empty.

HubSpot form responses can be customized, so it is recommended to work closely with your Marketing Ops team to confirm the the lead(s) has been successfully received and to troubleshoot if needed.

 

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.

"\n\n <!doctype html>\n <html>\n <head>\n <!-- FORM_NOT_FOUND -->\n 
<meta charset=\"utf-8\">\n <link rel=\"shortcut icon\" href=\"//static.
hsappstatic.net/StyleGuideUI/static-3.60/img/sprocket/favicon.ico\" 
type=\"image/x-icon\">\n\n <title>Form not found</title>\n\n <style>\n html, body 
{ height: 100% }\n body {\n padding: 0;\n margin: 0;\n color: #425b76;\n 
font-size: 0.875rem;\n line-height: 1.65rem;\n background: #f9fbfd;\n font-family: 
\"Avenir Next W01\",Helvetica,Arial,sans-serif;\n }\n .outer-container {\n position: 
relative;\n height: 100%\n }\n .inner-container {\n position: absolute;\n top: 50%;
\n left: 50%;\n transform: translate(-50%, -50%);\n max-width: 640px;\n margin: 0 
auto;\n background: white;\n box-shadow: 0 1px 4px 0 rgba(0,0,0,0.1);\n 
border-radius: 0.1875rem;\n padding: 2rem;\n }\n h1, h3 {\n font-weight: 500;\n 
-webkit-font-smoothing: antialiased;\n -moz-osx-font-smoothing: grayscale;\n 
font-smoothing: antialiased;\n text-shadow: 0 0 1px transparent;\n line-height: 
normal;\n }\n h1 {\n font-size: 1.65rem;\n margin-bottom: 1.25rem;\n margin-top: 
0;\n position: relative;\n }\n h1::after {\n background-color: #cbd6e2;\n bottom: 
-10px;\n left: 0;\n width: 100%;\n content: ' ';\n height: 1px;\n position: absolute;
\n }\n h3 {\n font-size: 1.45rem;\n margin-bottom: 0.8rem;\n margin-top: 0;\n 
position: relative;\n }\n a {\n color: #00a4bd;\n text-decoration: none;\n }\n 
a:hover {\n text-decoration: underline;\n }\n </style>\n </head>\n <body>\n <div 
class=\"outer-container\">\n <div class=\"inner-container\">\n The error response 
reason will be included here*.\n </div>\n </div>\n </body>\n </html>\n"

HubSpot 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.

 

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