Recording Links are shareable URLs that let anyone record their screen and send you a Jam. No browser extension, no account, no downloads required. Generate a link from your dashboard or browser extension, paste it wherever your customers already are, and receive a full recording with technical context the moment they submit.
How it works
1
2
3
4
When to use Recording Links
- Customer support. Replace vague descriptions with visual reproductions.
- External bug reports. Get technical context from users outside your team.
- QA workflows. Capture specific scenarios and environments.
- Remote debugging. See issues that occur only in specific setups.
Create a link
From the browser extension
From the dashboard
1
2
3
4
5
1
2
3
4
Recording Links work anywhere you can paste a URL:
- Email: “Hi there, can you click this link and show us what you’re experiencing? [recording link]”
- Support tickets: paste directly into Zendesk, Intercom, or HubSpot responses
- Chat messages: Slack, Teams, or any messaging platform
- Customer forms: include in help documentation or contact forms
What recipients experience
The recording flow is designed for non-technical users:
- Instant access: the link opens directly in their browser, no downloads
- Simple interface: a large Start Recording button with clear instructions
- One-click recording: captures their screen, showing the bug
- Submit recording: recording uploads automatically and notifies you immediately
View submissions
Jams submitted through a Recording Link appear in your Jam dashboard as regular Jams:
- You receive an email notification when a Jam from your Recording Link is recorded.
- Find the recording in your workspace’s Jam dashboard and in the Recording Links page, where you can see all Jams grouped by link.
Reusable links
Recording Links are reusable by default. A single link can receive unlimited submissions, making them ideal for:
- Ongoing customer support or QA workflows
- Feedback buttons embedded in your product
- Email signatures
- Pinned Slack messages
URL parameters
Customize the behavior of any Recording Link by appending query parameters to the URL.
Set the Jam title
Use jam-title to pre-populate the title of every Jam created from this link:
For a same-domain Recording URL:
Additional parameters
| Parameter | Description |
|---|---|
jam-title=<TITLE> | Sets the title of the recorded Jam |
jam-folder=<FOLDER_ID> | Routes the Jam into a specific folder. Use the 4-character folder ID from the folder’s URL in your dashboard: https://jam.dev/s/<WORKSPACE-ID>/<FOLDER-ID> |
jam-reference=<URL_OR_EMAIL> | Associates a user identifier or URL (e.g., a helpdesk conversation, issue tracker link) |
Adding a reference
Attach a reference to a Recording Link to automatically link the resulting Jam back to the issue you’re tracking.
1
2
3
4
Capture logs from your domain
By default, Recording Links capture only screen recordings. To also collect console logs, network requests, user interaction events, and enable automatic blurring, you need to connect your domain and install Jam’s scripts on your site. Once configured, logs are automatically attached to each submitted Jam.
Privacy and automatic blurring
When your domain is connected, Jam can automatically detect and blur sensitive information during recordings. Blurring happens directly in the browser before the recording is uploaded, so sensitive data never leaves the user’s device unprotected.
What gets blurred automatically
Jam detects and blurs the following by default:
- Password fields
- Credit card numbers (including CVV, expiration, and card number fields)
- Social security numbers and tax IDs
- Bank account and routing numbers
- Passport and driver’s license fields
- Phone numbers and email addresses
- API keys and tokens
Jam also recognizes privacy selectors from popular session replay tools. If you already use FullStory, Hotjar, LogRocket, Sentry, Microsoft Clarity, OpenReplay, Highlight.io, ContentSquare, Matomo, Heap, or Amplitude, your existing privacy configuration works automatically with Jam.
Custom blur rules
If you run Jam on your own domain, control blur behavior with HTML data attributes:
To pass custom CSS selectors using the SDK:
Or using a <meta> tag:
Limitations
- Content inside iframes must be blurred entirely. Selective blurring inside an iframe is not supported.
- Flashes of unblurred content may occur on page load if your UI initializes before Jam.js. Move Jam.js initialization earlier in your page’s execution to prevent this.
- When the browser window is resized during a recording, blurred content may briefly become visible as the page reflows.