A Sentry error tells you that something broke and roughly where. It rarely tells you what the person was doing when it broke: which button they clicked twice, what the page looked like as it failed, or how slow checkout already was before the crash. That gap is where a session replay sentry setup earns its keep — the error report and the session behind it become one trail you can follow in two clicks.
This guide covers how to connect the two without putting user data into your error tags: which identifier to attach, where it lives, and what to look at once you land in the session. It assumes you already send errors to Sentry and want a recording beside each one.
What connecting the two records actually means
Your error tracker and your replay tool store different things. Sentry keeps the exception, the stack trace, the release, the route and whatever tags you attach. A replay keeps the timeline: navigation, clicks, scrolls, JS errors, form interactions and Web Vitals, plus heatmaps and rage, dead and error clicks in Prynt Replay.
Connecting them means writing one shared identifier onto the error event, so whoever reads the issue can open the session that produced it. You can do that with a tag your Replay search understands, or with a share link dropped into the issue. Prynt Replay ships a Sentry integration, and the pieces underneath — session id, share link, embedded player — are the same whether you use the integration or wire it by hand.
Link a Sentry error to its session in three steps

Step 1: expose a stable session identifier
Call identify(userId, { accountId }) when the session starts. That is what lets you list sessions per company or per user later, and it is the difference between “a session happened” and “the Acme account’s session on release 4.2.1”. The exact call and the player embed live in our docs.
Step 2: attach it to every error event
Set the identifier once per page load on the Sentry scope so it rides along with every exception after that:
Sentry.setTag('prynt_session', sessionId);
Sentry.setTag('account', accountId);
Do it in one place — your app shell or your error boundary — so a new route cannot forget it. Keep the values opaque: internal ids only.
Step 3: open the session from the issue
When the error lands, paste the tag value into Replay search, or add the session’s share link as the first comment on the issue. Support teams can go further: sessions can be listed and opened inside your own admin, per company or per user, so the person answering the ticket sees the recording without a second login.
What to look at once you are inside the session
- The click before the error. Was it a single action or a rage click after three failed attempts?
- JS errors on the timeline, matched against the Sentry stack trace and release.
- Web Vitals for that page. A slow page and a broken page produce different fixes.
- Dead and error clicks around the failure, which show where the interface stopped responding.
- Py’s summary. Prynt’s AI explains what went wrong in the session and can send a daily brief; it is included with Replay up to a monthly limit per plan.
Two minutes inside the recording usually replaces a round of “can you reproduce it?”
Keep personal data out of error tags
Replay masks every form field in the browser and again on the server, and there is no unmask option — that is a design decision, not a setting. The protection only holds if you do not copy the same data into the tag you just created: no emails, no card numbers, no OTP codes, no raw payloads. Use internal ids, and if you need to join to a request, log a requestId and match on it later. The privacy model is documented on our security page.

Turn it into a triage loop
Sentry alert → issue → tag → session → share link in the comments → fix → confirm the same pattern stops appearing. Native mobile replay (iOS, Android, React Native, Flutter) follows the same path, so a crash reported from an app gets the same context as a web error. Bot sessions do not count against your quota, which matters on pages that get scanned constantly.
Volume decides the plan: the free plan records 1,000 sessions a month with 14-day retention on one site; Pro is $279/month for 10,000 sessions, 30-day retention and three sites, with a 14-day trial; volume plans go up to 1M sessions. Details are on our platform page.
FAQ

Does connecting Sentry and Replay replace Sentry?
No. Sentry keeps grouping, alerting and release tracking. Replay adds the human timeline to the error you already received, and you keep both.
Can I see what a user typed in a field that failed?
No. Every form field is masked in the browser and again on the server, with no unmask option. You see which field was used and when, not its value.
Do bot visits use up my session quota?
No. Bot sessions are excluded and do not count against the Replay quota.
Start small: pick the error type that costs you the most, tag it with the session id, and open the next issue in your inbox from the session instead of from the stack trace. You can create an account and record your first sessions at https://pryntid.com.
Try it free
Prynt is device intelligence with a free plan: 5,000 identifications a month, visitor IDs with confidence and bot detection — no credit card. Upgrade to Pro for VPN, proxy, tampering and behavioral signals.