We’ve implemented a series of changes to optimize our first-party insight, and this has allowed us to add a new insight to identify issues on third-party tools. Third-party issues are difficult to resolve, as your team doesn’t have direct access to the code causing the issue and must instead go through the third-party’s support team. With this update, you can see at a glance whether an issue is first-party or third-party, and prioritize its resolution accordingly.
Please note that our current logic is to mark any issue that is not first-party as third-party. We’ll make changes to this logic as we surface exceptions and fringe cases.