99e71ba04b
Tracker 3.5.13: performance improvements for a case of extensive dom * use of `.nodeType` property instead of `instanceof` when possible * use of `.nodeName` property instead of `instanceof` for Elements * 2 previous also solve issue of non-function `instanceof` under different iframe contexts * use map instead of array for storing recent nodes * check node scrolls on start only |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| .npmignore | ||
| .prettierrc.json | ||
| js_errors.txt | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| rollup.config.js | ||
| tsconfig-base.json | ||
OpenReplay Tracker
The main package of the OpenReplay tracker.
Installation
npm i @openreplay/tracker
Usage
Initialize the package from your codebase entry point and start the tracker. You must set the projectKey option in the constructor. Its value can can be found in your OpenReplay dashboard under Preferences -> Projects.
import Tracker from '@openreplay/tracker';
const tracker = new Tracker({
projectKey: YOUR_PROJECT_KEY,
});
tracker.start({
userID: "Mr.Smith",
metadata: {
version: "3.5.0",
balance: "10M",
role: "admin",
}
}).then(startedSession => {
if (startedSession.success) {
console.log(startedSession)
}
})
Then you can use OpenReplay JavaScript API anywhere in your code.
tracker.setUserID('my_user_id');
tracker.setMetadata('env', 'prod');
Read our docs for more information.