Integrating Roundtable
This guide shows how to drop Roundtable’s behavioral‑biometric & (optional) replay tracker into any web app.
Quick start – 2‑line install
The Roundtable tracker dispatches a roundtable:ready
event on window
as soon as it finishes loading. Block 2 listens for that event so you can safely call window.setRoundtableUserId
once the script is loaded.
Script‑tag attributes
The tracker recognizes three data‑attributes that let you tailor its behavior:
data-site-key
(required) – Your workspace’s site key (find it in the Roundtable Dashboard).data-user-id
(optional) – A stable identifier for a logged‑in user to track them over multiple sessions (a hashed value is fine).data-replay
(optional) – Set to “false” to disable replay capture (if omitted, replay data is collected).
React / SPA example
Add the Roundtable tracking script in public/index.html
:
Then wire the user ID in React:
Call the hook in your auth/provider component; it runs every time currentUser
changes, so it sets the UID immediately on page‑refresh and again right after a fresh login.
Using the Session ID
Every page‑view (or SPA session) gets a unique session ID that Roundtable stores in
sessionStorage under rtSessionId
. You can reference this ID from your own backend or logs to pull the exact biometrics and
replay for that visit.
Because the session ID is stored in sessionStorage, the value is scoped to the current tab and cleared automatically when the tab is closed. Roundtable does not use any cookies or local storage.
Next steps
- Visit your Roundtable Account to access your public API key.
- Learn how to Access Session Data to retrieve user actions and replay recordings.
- Explore our API Reference for more details.