Unbounce offers native integrations with a number of third party platforms, which is fantastic for sending data where you need it to go outside of Unbounce. But what happens if instead of a lead being submitted to a third party CRM you instead get an error?
The first step in troubleshooting an integration error is to check the field mapping to make sure all the form fields are correctly mapped to the third party service being integrated with.
The best way to troubleshoot an integration error is to look at the error message returned from the service the lead is being sent to. The specific error message will differ depending on the service being integrated with. Some messaging is useful, some not so much. The key though is to understand where the error is coming from and what first steps can be taken to resolve the issue. In most cases both these bits of information can be inferred from the error message.
An integration error refers only to a lead not making it to a third party system. The lead will still be collected in Unbounce and available in the view leads table. Leads can also be resubmitted by viewing the integration error from the page overview screen.
Viewing Integration Errors
If one of your pages has an integration error you will see a notification on the All Pages screen in your account.
More detail on the specific error(s) can be found on the page overview screen in a couple of places. You can view the raw error data coming back from the third party integration from the page overview screen or drill down for more info via the view leads table.
In the Integrations section at the bottom of the page overview click the view details link for the specific integration in order to launch a modal with options to ignore (dismiss) the error, resubmit the specific lead, and to view more details. The data under the show details tab is the raw data coming back from the service the integration is setup with. In the case of the below screenshot the error message is coming back from MailChimp:
Find The Error Message In "View Leads"
Click the view leads button on the right side of the screen to open the view leads table. From there navigate to a lead that has an integration error and click on it. This will open a Lead Details window on the right. Scroll to the bottom to the "Integration Details" section and click to expand the error messaging for the specific integration displaying an error.
Interpreting Integration Errors From the View Leads Table
When viewing the details of the error in the lead data you will be given various pieces of information that can be used to gain insight into what's causing the error. There will be an error code and message and two tabs that can be clicked to see what exactly is being sent by Unbounce and what is being returned by the service that the page is integrated with.
The information in the request tab shows what Unbounce is sending via the integration. The Headers contains the meta information sent in the request and the Body contains the actual data being sent. The Body of the request will contain the form data and any other information sent to the third party platform. This information can be used to confirm that Unbounce is sending the correct data through the integration.
The information in the response tab is formatted the same as in in the request tab, with Headers and Body tabs. The difference with the response is that the information coming back from the service the integration is sending data to, and not being generated within Unbounce. For example in the above screenshot, the information in the response tab is what MailChimp is returning. The response tab is the best place to find information on what's causing an integration error.
In the event of an integration error the response tab will contain any error messages or error codes specific to the service being integrated with. The important thing to understand about this is that the error is being generated outside of Unbounce and displayed within the view leads table.
The 400 error noting a blank email address is coming back from MailChimp due to a requirement within MailChimp that all leads must contain an email address.
The solution in this case would be to make the email field required in Unbounce. However the issue itself involves satisfying a MailChimp requirement for lead delivery. Every service will have different requirements or expected data and it is important to know what these requirements are for a given service to avoid potential errors.
Webhook Integration Errors
POST to URL Webhook errors can be viewed by clicking the View Details link under the webhook integration on the page overview screen or by viewing a specific lead in the View Leads table. With a webhook Unbounce does is send the form data as JSON and XML to the specified URL entered into the field. This means that anything returned as a result of this POST request is entirely dependant on the server the webhook is pointed to.
The type of response returned for a webhook error can vary wildly depending on where the webhook is pointed and how the server is configured. Unfortunately it isn't possible to troubleshoot issues with an external server from directly within Unbounce. Reaching out to the server admin where the webhook is pointed may be required to resolve any issues.
Unhelpful Error Messages
An error message may not always be very specific or indicate what the exact issue is. In cases where the error message is unclear it may help to look up the HTTP status code found in the response tab for more information.
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.