Troubleshooting Integration Errors


Unbounce offers native integrations with several different third-party platforms, which is fantastic for sending data where you need it to go outside of Unbounce. But what happens when there's an error with your integration? 

The best way to troubleshoot an integration error is to look at the error message returned from the service receiving the lead. 

This article will help you understand how to troubleshoot an integration error.

To learn more about integration errors, what they mean, and how they occur, see the following article: What is an Integration Error?

Before You Get Started

Each integration error varies, so it can be tricky to pinpoint what could be causing this.

This article offers some suggestions, but we recommend reviewing the response from the server within the Leads tab or Integrations tab to learn what it could be.

For steps on locating an integration error, see What is an Integration Error?

Troubleshooting Integration Errors

Some integration errors will present you with a message that is easy to fix, depending on the response code shared by the CRM or third-party tool.

Here are some examples of what can cause an integration error and suggestions on how to resolve them.

300-level Responses

These are relevant to the integration and can sometimes mean the response went through or an issue with the server receiving the information from Unbounce.

Be sure to review the response within the Leads table for more information on how to troubleshoot. 

400-level Responses

Your visitors may be submitting invalid form responses (invalid email addresses, phone numbers, zip codes, etc.).

  • To remedy this, be sure that you're validating the form responses coming from your users.

For more about forms, see our documentation: Working with Forms in Smart Builder or Adding and Editing Forms in the Classic Builder.

Or, it could be that your integration consists of the required form field, whereas your Unbounce form does not have these fields set as required. Or vice versa.

  • Log into your third-party tool or CRM, and double-check that the required fields match the required fields set up in your Unbounce form.
  • For example, if you've set specific fields as required in your Unbounce form, but have not set that as required in your CRM, you'll need to double-check that the two-match for the lead to send correctly.
    • You will need to make changes to your Unbounce form, or make changes to the CRM.

500-level Responses

The server (from the integration) receiving the leads from Unbounce was down.

Often, you can resubmit these errors and try again. You can bulk resubmit errors within the Integrations tab.

  1. Navigate to the Page Overview.
  2. Click on the Integrations tab.
  3. Click the View Details button to open the integration error pop-up.
  4. Here, you'll see a list of the integration errors. To resubmit the errors more, click the Resubmit button:
    Red box around 'Resubmit' button within then Unbounce App's Integrations tab.

For more details on HTTP response codes from integration errors, and what they mean, see What is an Integration Error

If there's no clear error response code

Suppose the error message from the service does not give a clear answer to fixing the integration error. In that case, the next step in troubleshooting is to check the field mapping to make sure all the form fields map correctly to the third-party service.

See our guide to field mapping for native Unbounce integrations here: Setting Up Field Mapping.

There may be other integration errors depending on the third-party platform or CRM. See additional setup or troubleshooting steps in these CRM-specific articles: 





Campaign Monitor

Webhook Integration Errors

To view POST to URL Webhook errors, click the View Details link under the webhook integration on the Page Overview screen, or click a specific lead in the View Leads table:

Red box around 'View Details' button within then Unbounce App's Integrations tab; specifically, a Webhook integration.

With a Webhook, Unbounce sends the form data like JSON and XML to the specified URL entered into the field.

This means that anything returned due to this request depends entirely on the server the webhook points to. The first step to troubleshooting a Webhook integration error is to check the field mapping.

At this time, it isn't possible to troubleshoot issues with an external server (via Webhook and POST to URL) directly within Unbounce. It's best to reach out to the server admin where the Webhook points to better support or troubleshoot the integration error or issues. 

For more information on Webhooks, see our documentation: Using a Webhook

Troubleshooting Powered By Zapier Integration Errors

Zapier integrations are usually incredibly stable and reliable. On rare occasions though errors may occur. Due to the way Zapier connects different platforms troubleshooting any errors will usually require access to Unbounce, Zapier, and the service Zapier is connecting to to determine where the issue in the integration exists.

If you are seeing errors from within Unbounce check that the zap is configured correctly and the correct permissions are enabled to allow for the passing of data between the different platforms. This can be confirmed from within the Zapier account.

If you are not seeing any errors in Unbounce but data is not making it to the expected platform through the integration, the data is most likely making it from Zapier to Unbounce successfully and the issue exists outside of Unbounce directly. It is recommended to look into any potential issues in the platform data is being sent to.