Surfacing Integration Errors in the Debugger
Our mission is to give you the power to send data to new tools with the flip of a switch. Giving you visibility into what happens after you flip that switch is critical. So, as of today, any errors returned from our 90 server side integrations are visible in your debugger!
This means you can diagnose issues with many of the tools in your marketing and analytics stack, right from inside Segment.
In the past, you’ve been able to see basic errors for your data hitting the Segment API, but you couldn’t see what happened when that data was sent to downstream tools.
This was a problem because small issues could cause your data not to make it to an enabled integration. For example, maybe you turned on an email tool, but you never called
identify with an
Whatever the reason, sometimes data doesn’t appear in the tool you’ve enabled. And when it doesn’t, it shouldn’t be a mystery why. You also shouldn’t have to contact us to figure out what’s going on!
Now, you can see what’s happening directly.
If you go into your debugger, you can click into individual calls and see if there are any errors returned from downstream server-side integrations.
We’re working on ways to summarize the quality of service for each of your integrations, and we’re excited to find and expose better ways to proactively warn you of issues — be they an expired webhook server certificate, sudden
402 Payment Required errors from a third party integration, or even dropoffs in a crucial event’s volume.
And if you have any feedback or suggestions, please shoot us an email. We’re all 👂👂!