What is an Integration Error?


If you're here, you've probably seen this message within the Unbounce Conversion Intelligence™ Platform, explaining that one of your pages has an integration error. 

Unbounce app with yellow border surrounding a landing page, stating that 'The following has logged errors with an integration'.

We're happy to help. To start, it's essential that we first understand what integrations are and how they happen.

What is an Integration Error?

Unbounce offers native integrations with a number of third-party platforms (MailChimp, Salesforce, Marketo, etc.), which is fantastic for sending data from your landing page form where you need it to go outside of Unbounce. But what happens when there's an issue on data sent from Unbounce to a third-party platform? 

An integration error appears when a third-party platform sends back a response code to Unbounce's servers, indicating that there might've been an issue with accepting the lead (from a form submission).

Such errors can appear if there's an issue with the integration or how Unbounce is sending the information.

What Can Cause an Integration Error?

There are several reasons an integration error could occur. Here are some instances:

  • A page visitor may not have filled the form on your landing page correctly.
  • A failed connection between the Unbounce platform and your third-party integration (i.e., the server is down)
  • There might be certain form requirements that your integration requires before your user can submit a lead.

To understand what caused the error, we need to read the response code sent along with the lead and form submission.

Locating Integration Errors

The best way to troubleshoot an integration error is to look at the error message returned from the third-party platform, CRM, or tool.

There are two ways to locate integration errors: Within the Integrations tab or within the Leads table.

Integrations tab

  1. Navigate to the Page Overview of the landing page where the integration error messages occur.
  2. Click the Integrations tab at the top of the Page Overview.
  3. Locate the integration with a triangle warning sign next to it; this is where the integration error is occurring:
    MailChimp integration annotated with a red box, and highlighted in yellow.
  4. Click the View Details button to open the integration error pop-up.
  5. Here, you'll see a list of the integration errors. To learn more, click the Show Details drop-down button:
    This includes the raw data coming back from the service the integration, as well as an error message from the service:
    A list of MailChimp integration erorrs.

Here, you have the option to ignore (dismiss), resubmit, or show more details about the error. 

The Leads Table

The Leads table will provide more details about the integration error, such as the HTTP response code, and the Request and Response from both servers: Unbounce and the third-party app.

  1. Navigate to the Page Overview of the landing page where the Integration Error Messages occur.
  2. Click the Leads tab at the top of the Page Overview.
  3. Select a lead from the list. A window will appear on the right-hand side of the page.
  4. Scroll down the Integration Details section.
  5. Here, you'll notice another yellow warning triangle, and details about the integration error:
    A gif of a user clicking  the 'Leads' tab at the top of the Unbounce Page Overview; the leads load. A lead is clicked, and a page launches on the right-hand side with details about the lead.

Interpreting Integration Errors From the Leads Table

When viewing the details of the error in the Leads table, you will notice various pieces of information that can help you gain insight into what's causing the error.

There will be an error code and message, including two tabs that detail precisely what Unbounce sent to the third-party platform, and how the third-party platform responded to that data sent over:  The Request tab and Response tab:

Two red boxes anotating the integration errors relating to the lead: one highlighting 'Response', and another highlight 'Request'.

The information in the Request tab details what information Unbounce sends via the integration. Within the Request

  • The Headers contain the meta information sent in the request 
  • The Body contains the actual data sent. The Body of the request will collect the form data and any other information sent to the third-party platform.

The Request tab highlights what information Unbounce will send (or plans to send) via the integration, to your third-party platform. 

The Response tab highlights how the third-party platform responded to the information sent over from Unbounce. Meaning, the message is not from Unbounce, but rather the third-party platform communicating the status of the lead sent. 

The Response tab is the best place to find information on what's causing an integration error.

Integration Error Response Codes

Within the Response tab, you'll notice a string of numbers also highlighted in yellow, known as HTTP response status codes.

A few different response codes can further explain why the integration errors occurred and why the lead did not go through to the third-party platform or CRM. Here are some examples:

Successful HTTP Responses

200-level codes (200, 204, etc.)

These codes indicate a successful transmission of data. No further action is required, as your response went through successfully.

Other HTTP Responses

301 or 302-level codes

Depending on the integration type, these codes can vary. Review the response within the Leads table for more information on what this error means exactly. At times, it could mean that the lead was successful.

For more information, check-in with the Support team of the third-party platform regarding the status of the lead (meaning, did it go through, was information missing? etc.).

400-level codes (400, 401, 404, 410, etc.)

The lead data count not be transmitted successfully due to a problem with the request.


  • Unbounce sends the lead data in a format that the third-party platform cannot accept.
  • The lead data that Unbounce sends is missing fields required in the third-party platform.

500-level codes (500, 502, 504, etc.)

The lead data could not be transmitted successfully due to a problem with the third-party platform's server. Examples:

  • The third-party platform's servers at one point failed, are currently failing, or are under maintenance and cannot respond.

For more information on different HTTP status codes, see this reference: HTTP response status codes.

Troubleshooting Integration Errors

Different integration errors may require other troubleshooting methods. To learn more about troubleshooting these response codes and other integration errors, see the following article: Troubleshooting Integration Errors.