⏱ Estimated Time To Completion: 2 minutes
1
Get your new DSN by creating a project in Decipher
Log in to Decipher with your work email. On the Settings page, choose a project name and click “Create New Project”.
On the following screen, decide where you want to send data. We recommend choosing Decipher only to avoid double charges.
We auto-create a Decipher-only project called “FirstFrontendProject” when your organization registers with Decipher, but that is separate from the Sentry project you’re about to add.

I want to send data to Decipher only
I want to send data to Decipher only
Sending data only to Decipher is the recommended option for many as it:
Decipher will give you a new
- Avoids duplicate charges from multiple providers
- Provides all the functionality you need in one place
- Simplifies your monitoring footprint

dsn
to copy and paste in the following step.I want to send data to Decipher and Sentry
I want to send data to Decipher and Sentry
Sending data to both Decipher and Sentry requires your existing Sentry DSN and may result in charges from both services.To get your existing Sentry DSN, look for the value of the 
On the next screen, enter your Sentry DSN. Then click “Add this project”.
Your Sentry DSN is only used to compute your Decipher DSN which you’ll use in the next step, and while your Sentry DSN is public, Decipher never stores it.Decipher will create a new project with a dedicated new DSN for you.
Using this new DSN will result in data being sent to both Decipher and Sentry.
dsn
parameter in your codebase’s call to Sentry.init
.

2
Update your Sentry initialization to use the new DSN and configuration
NextJS
NextJS
Update your
instrumentation-client.ts
to use your new dsn
and make sure replayIntegration and replaysSessionSampleRate are set
.Additionally, update sentry.edge.config.ts
, and sentry.server.config.ts
files to use your new dsn
.On older
@sentry/nextjs
versions update your sentry.client.config.ts
instead of instrumentation-client.ts
.Other Frameworks
Other Frameworks
In your codebase, update the line that sets the
dsn
field of your existing Sentry initialization to use the new value you got from Step 1, and ensure that replayIntegration
and replaysSessionSampleRate
are set.
For example:3
Identify Users
If you aren’t already doing this, make sure to identify users where user information is available in your application frontend, typically after authentication or login.Once you’re done, simply use your website to validate that Decipher is collecting session replay data (and that Sentry is too, if you selected that option).