Once you’ve installed one of our Invoca integrations, we want you to have full confidence that it’s working as intended. With any integration that passes data back and forth between your different apps, errors are certainly possible. This article will help you identify exactly what data your Invoca webhooks are sending to other systems, so you can confirm whether your integrations are working correctly — or diagnose any potential errors.
The webhook deliveries chart is a visual representation of each instance a webhook fired. It is a stacked bar chart where the green indicates the end system received the data and returned a success response and the red indicates the end system returned an error response. You should use the chart to understand fluctuations in:
Here's how to access your webhook deliveries chart:
There are a few important points to keep in mind as you reference the webhook deliveries chart.
If you find you need to troubleshoot further, you can dig into more delivery details in the Delivery History tab.
Your webhook delivery history is a tool in your Invoca account that presents an audit of the recent 100 instances when one of your webhooks fired — along with what data it contained, and whether it was received successfully. This makes it a great first step for troubleshooting your integrations.
Here's how to access your webhook delivery history:
Here are a few things you can use your webhook delivery history to troubleshoot:
If you don't see any recent deliveries in your webhook stats or delivery history, and you expected to see some deliveries within that time frame, the problem likely lies with your Invoca configuration. Here are a few things you can check to address the problem:
As we mentioned above, your webhook delivery history shows the HTTP status code for each of your recent webhook transmissions. These can be helpful to figure out issues with the data being sent or formatting errors, especially if all of your webhook deliveries show a status code that indicates an error.
Expand a few delivery rows to view the Response tab. The Response is what is returned by the end solution to provide more information about the error. This is a great place to start, but if it isn’t quite enough information to understand how to fix the issue, it can be very helpful to take the message in the Response and search the web for more information. Popular technical forums, like Stack Overflow (external link), or the end solution’s API documentation often have more details about how to go about fixing common issues.
When reading response codes, keep in mind that some solutions, like Google Campaign Manager, can return a 200 success status code even when the webhook wasn't actually properly received. In these cases, check the webhook response for a message relaying an error in processing the API request (for example, encrypted user ID is missing, etc.).
If the Response is not verbose enough to fully understand the issue, here are a few potential solutions you can try depending on your status code:
Invoca integrations often work by sending a record of a call or signal that occurred in your Invoca platform to another system, where it's matched with an independent record in that other system. It’s important to distinguish between (a) successfully sending data and (b) processing the data to determine if it should be attributed or actually show up in that end system.
It is possible that Invoca successfully delivered data, but the end solution could not attribute the event or conversion in their system based on the data provided or rules set in their system. Even in a successful integration setup, we expect those records to match up less than 100% of the time — sometimes significantly so, depending on the integration.
If your webhook successfully sends data, but you want to understand why some or all information is not showing up in the end system, you might consider trying the following:
As mentioned above, the best way to get a granular view of the data eligible to be sent to another system is to run a Transactions Details Report for the date range and then filter for the different conditions that must have been met. If you are checking to see if your Signals have been transferred, double check that you have included the Signal Value column and filter for True.
If this guide didn't do the trick, our Customer Success team will be happy to look at your problem. You can click the “Contact Support” button at the bottom of this article to create a new ticket and get in touch right away.