Custom Metadata Overview

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.

Note: You may also like to identify your reporters automatically.


Custom Metadata can be useful to help developers debug issues by adding more details about the current state of the application.

Custom Metadata Supported types.

Custom Metadata methods.

Custom Metadata examples.


Custom Metadata Supported types


Supported types of custom metadata:

  • number

  • boolean

  • strings

  • array

  • objects


Custom Metadata methods

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',
}
};


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',
],
});


Custom Metadata examples

Custom Metadata example in your PM tools.

Here's what happens when running our example code.

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


Custom Metadata example in the feedback page

On the Marker.io feedback page, custom metadata is displayed on the Metadata tab.

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

You may also like to identify your reporters automatically.


Did this answer your question?