Sentry Destination

Segment makes it easy to send your data to Sentry (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Sentry in the format they understand. Learn more about how to use Sentry with Segment.

Our Sentry destination code is all open-source on GitHub if you want to check it out.

Getting Started

When you toggle on Sentry in Segment, this is what happens:

  • Our CDN is updated within 5-10 minutes. Then our snippet will start asynchronously loading Sentry’s javascript onto your page. This means you should remove Sentry’s snippet from your page.
  • Sentry will automatically start tracking errors in your app’s javascript.

Sentry is only supported on the client-side.


When you call identify we call Raven.setUserContext by passing in the traits you provided. We will map the userId you provide as

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.


The name of the logger used by Sentry.

Maximum Message Length

By default, Raven does not truncate messages. If you need to truncate characters for whatever reason, you may set this to limit the length.

Whitelist Urls

The inverse of ignoreUrls. Only report errors from whole urls matching a regex pattern or an exact string. whitelistUrls should match the url of your actual JavaScript files. It should match the url of your site if and only if you are inlining code inside