All articles Fundamentals

Embed Session Replay in Admin: A Per-Account Guide

Support specialist reviewing an embedded session replay panel in a dark admin interface

If support has to leave your admin to watch a replay, they stop watching replays. The fix is plumbing, not tooling: tag every session with the right identity, keep the lookup on your server, and embed session replay in admin screens your team already has open. With Prynt Replay that means one identify() call carrying accountId, a server-side list call signed with your secret key, and an embedded player per session.

The payoff is an answer with evidence. “The export button does nothing” becomes three sessions from that company, in order, with the JavaScript error and the rage clicks visible next to the ticket. You do not need a new dashboard; you need a tab on the company page and the user page you already built.

Why per-account replay beats a global session inbox

A flat list of sessions is a haystack. Support thinks in companies and users: the ticket says “Acme” or an email address, never a session ID. When every session carries an accountId, the company record becomes the entry point and the session list becomes a short, relevant history instead of a search problem.

Start from the record you already have

Add a Sessions tab to the company detail page, and a smaller one to the user detail page. Both read the same source with different filters: accountId for the company, userId for the person. That is the whole information architecture, and it is the difference between a tool nobody opens and a habit.

Tag sessions with identify() and accountId

Call identify() after login, once per page load, with the user first and the account in the traits object:

Developer tagging sessions with an account identifier on a dark dashboard

prynt.identify(user.id, { accountId: user.accountId });

Call it again when the active account changes, so sessions from a second workspace or an impersonated account do not land under the wrong company. Sessions that start before this call stay anonymous, which is what you want for pre-signup debugging.

Keep the secret key on your server

The browser tag is public by design; the secret key that lists sessions is not. Query the session list from your backend only, and shape the response before it reaches the admin:

// pseudo-code, server-side only
const sessions = await listSessions({ accountId, limit: 25 });

Exact request shapes and payload fields are in our docs. Never ship that key in client code or in an embedded player URL built in the browser.

Verify the round trip before you build UI

Ship the identify call, record one session, then confirm your server can list it for that accountId. Everything below depends on that loop working.

Build the company and user session lists

Give each screen its own backend route — /admin/companies/:id/sessions and /admin/users/:id/sessions — that calls Prynt with the secret key and maps the result to the columns support actually asks about:

  • When and how long: timestamp, duration, entry page.
  • What went wrong: rage clicks, dead clicks, JavaScript errors, slow Web Vitals.
  • Who: user ID, device and browser.

Show newest first, paginate, and put the retention window in the label so nobody hunts for a session that aged out: Free keeps 14 days of the 1,000 monthly sessions, Pro keeps 30 days of 10,000. Filter the company view strictly on accountId, so anonymous pre-login sessions never pollute a customer’s history.

Embed the player where the ticket lives

Render the embedded player from your own admin — a modal on the company page, a sidebar panel in the ticket view — so the session opens in context instead of in another product tab. Pass only the session reference your backend resolved; never construct the embed from user-supplied input.

Abstract view of a session player embedded inside a company admin screen

What support sees, and what stays masked

Every form field is masked in the browser and masked again on the server, with no unmask option. Support watches cursor movement, clicks, scroll and navigation while payment and password fields stay unreadable. Say that out loud in your internal docs, because it is the reason you can let first-line support watch sessions at all.

Set access rules before you launch

Replay data is customer data. Decide who may open a player, log every view with the admin’s ID, and treat share links as external: they leave your access control behind, so use them deliberately. Our security page covers the data-handling basics worth putting in that policy.

Wire replay into the workflow you already run

The value compounds when a session is one click from the ticket. Three moves cover most of it: link the session list from your helpdesk macro, attach the session reference to escalations, and hand engineering the JavaScript errors and Web Vitals Replay already collects, so the bug report arrives with a recording.

Then make it a weekly habit: run Py, Prynt’s AI, over the sessions of the accounts that filed the most tickets. Py summarizes a session, explains what went wrong and sends a daily brief, which turns a folder of recordings into a short list of product fixes.

FAQ

Two support agents reviewing a shared session replay under blue light

Does accountId replace userId?

No. Use both. userId identifies the person, accountId the company they are acting in; company pages filter on accountId, user pages on userId. One person in two workspaces produces sessions under both accounts.

Can support watch sessions from before a user logged in?

Those sessions have no account attached, so they stay out of the company view. They are still useful when debugging signup or checkout, where the visitor has no account yet.

What happens after the retention window?

Sessions older than your plan’s retention (14 days on Free, 30 days on Pro) can no longer be listed or played. If a ticket may escalate, open and comment on the session while it exists, and keep your notes in the ticket.

Try Prynt Replay

Start on the Free plan with 1,000 sessions a month and 14-day retention, no card required, or move to Pro at $279/month for 10,000 sessions, 30-day retention and 3 sites with a 14-day trial. Read the embed steps in our docs and start at pryntid.com/products/replay.

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.

Keep reading