While Marker.io automatically captures various metadata about the issue (page URL, browser context, console logs, …), it is also possible to pass custom metadata using the snippet code.


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

  • array

  • objects

Method 1: passing custom metadata while loading your widget

Simply provide a customData object in your Marker.io widget config:

window.markerConfig = {
destination: "<DESTINATION ID>",

customData: {
storeId: 123,
storeName: 'Organic Fruits',
}
};

Method 2: set custom metadata using Marker.setCustomData()

You can set the current custom metadata anytime using the dedicated method:

Marker.setCustomData({
product: 'Banana',
available: true,
price: 1.23,
stock: 131,
brands: [
'The Organic Corp',
'ACME Fruits Inc',
],
});

Result:

Here's what happens when running our example code.

In Jira, our custom metadata shows up as a dedicated section in the description:

In Marker.io, our custom metadata is displayed next to the browser context:

Note: only member and admin roles can see the injected metadata in Marker.io

Did this answer your question?