Sentry
Sentry provides the error and exception data that makes Shingo's causal model dramatically more accurate. When Shingo can see the errors users encounter, it can trace revenue loss directly to specific bugs, stack traces, and code changes.
What Shingo reads
Issues
Error groups with stack traces, frequency, and affected users
Events
Individual error occurrences with context and breadcrumbs
Releases
Deploy data to correlate errors with code changes
Tags
Browser, OS, and custom tags for segmentation
Setup
Create an auth token
In Sentry, go to Settings → Auth Tokens → Create New Token. Select read-only scopes: project:read, event:read, org:read.
Copy the token
The token will look like sntrys_... — copy it from the token creation page.
Paste in Shingo
In the Shingo onboarding flow, paste the token in the Sentry connector field.
Key format
# Sentry auth token (read-only)
sntrys_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Why Sentry matters
Without error data, Shingo can still find revenue issues through behavioral patterns. But with Sentry connected, it can pinpoint the exact error, stack trace, and code location causing the problem. This is the difference between “mobile checkout conversion dropped” and “checkout.tsx:142 throws a TypeError on iOS Safari since deploy v2.4.0.”