Adding the script
Add these two tags to the<head> of every page where you want recordings to work:
YOUR_WORKSPACE_ID with your workspace ID. You can copy the exact snippet with your ID pre-filled from Workspace Settings > Domains in the Userplane dashboard.
Place the tags as early as possible in <head>. The Userplane script can only capture console logs and network requests that occur after it initializes — placing it early gives you the most complete recording context.
Sensitive data
To blur an element in recordings, add thedata-userplane-blur attribute:
content values for the meta tag:
| Value | What is blurred |
|---|---|
inputs | All <input>, <textarea>, and <select> elements |
images | All <img> elements |
all | The entire page |
URL parameters
When a customer opens a recording link, Userplane appendsuserplane-token, userplane-action, and userplane-workspace to the URL. For a static HTML site, these are read automatically by the embed script — no additional configuration is needed.
If your site redirects users to a login page before they reach the recorded page, carry the userplane- prefixed parameters through the redirect so the recording session can start after login. See Installation for an example.
Example app
A complete static HTML example is available at github.com/wizenheimer/userplane-sdk-examples/tree/main/examples/static-html. No environment variables or build step are required. Openindex.html directly in a browser or serve it with any static file server:
Related articles
- Installation — script placement, CSP, iframes, and browser support.
- Domain Verification Guide — verify domain ownership after installing the script.
- Sensitive Data Redaction — blur sensitive content in recordings.
- Web SDK — programmatic SDK for apps with a build step.