- Inject Marker.io widget in your web app
- Full control of the widget (hide / show, trigger captures, ...)
- Identify reporters (Learn more)
- Inject custom metadata in issues (Learn more)
- Silent mode (Learn more)
- Delayed server-side capture (Learn more)
- Disabling keyboard shortcuts (Learn more)
- First install the package from npm:
npm install -s @marker.io/browser
- Setup the SDK in your code:
import markerSDK from '@marker.io/browser';
const widget = await markerSDK.loadWidget({ project: 'abcd1234567890' });
Shows the Marker.io feedback widget.
Hides the Marker.io feedback widget.
Returns wether the feedback widget is currently visible or not.
Captures a feedback on the current page.
-
mode
: Type of capture to trigger. Available modes:fullscreen
,advanced
.fullscreen
captures the entire visible areaadvanced
shows the advanced capture options: limited area, entire page and desktop.
Example
widget.capture(); // or
widget.capture('fullscreen');
widget.capture('advanced');
Cancels current capture.
Returns a Promise<Boolean>
that indicates if the Marker.io extension has been detected. Having the extension installed allows more accurate screen captures and provides more capture options.
Example
widget.isExtensionInstalled().then((installed) => {
if (installed) {
// ...
} else {
// show install Marker.io extension button
}
});
Sets the current reporter information given a reporterInfo
object:
reporterInfo.email
: the email address of the reporterreporterInfo.fullName
: the full name of the reporter
Example
widget.setReporter({
email: '[email protected]',
fullName: 'Gabrielle Rose',
});
Unloads and cleans up Marker.io SDK and all used resources.
Marker.io exposes a variety of events that can be listened to using the methods described below.
Usage:
widget.on('eventName', function listener() {
// event handler code
});
Triggers once Marker.io is loaded.
Triggers if an error occurs while loading Marker.io.
Triggers right before Marker.io unloads.
Triggers when the feedback button becomes visible.
Triggers when the feedback button becomes hidden.
Triggers when a feedback is captured.
Triggers before submitting the feedback, i.e. when the user clicks Submit feedback.
Triggers once the feedback is successfully submitted.
Triggers if an error occurs while submitting feedback.
Triggers when the user discards a feedback by clicking on the "Close" button in the widget.
Whenever your application knows about your reporters' identity, you should provide that information through the Marker.io snippet code.
The reporting experience will be much better for your guests as they will not be prompted to provide their contact information while reporting their issues.
Identifying your reporters is dead-simple: all you need to do is to provide their reporter information in the configuration object of your snippet code.
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
reporter: {
email: '[email protected]',
fullName: 'John Smith',
},
});
widget.setReporter({
email: '[email protected]',
fullName: 'John Smith',
});
While Marker.io automatically captures various metadata about the issue (page URL, browser context, console logs, …), it is also possible to pass custom metadata to your issues using the SDK.
For example, this can be useful to help developers debug issues by adding more details about the current state of the application.
Supported types of custom metadata:
- number
- boolean
- strings
- arrays
- objects
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
customData: {
storeId: 123,
storeName: 'Organic Fruits',
},
});
widget.setCustomData({
product: 'Orange Juice',
price: 3.99,
stock: 130,
});
By default, Marker.io will log some useful information in the console to help you identify configuration problems and better understand how it functions.
However, in certain situations you may want to disable them all together so that it doesn't add noise to your recorded console logs.
To do so, you will need to enable silent mode directly inside your snippet code configuration:
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
silent: true, // <~ Enable silent mode
});
Delay the server-side capture so that your CSS animations can run before the screenshot is taken.
You can enable delayed capture adding a special parameter in your snippet code configuration:
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
// Add the following to delay the server-side rendering
ssr: {
renderDelay: 3000, // 0 - 15000 (ms)
},
});
In some particular cases, our keyboard shortcuts may conflict with your web app, you can easily disable all our shortcuts by passing a specific property in the JavaScript snippet configuration:
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
// Toggles off all keyboard shortcuts
keyboardShortcuts: false,
});
Need help integrating Marker.io with your web app? Feel free to contact us via your Marker.io account.
For every bugs, improvements or feature requests related to this SDK, please report a GitHub issue.
Released under the MIT license.