Console logs and network requests give your developers the same debugging context they'd get from opening browser dev tools themselves, attached directly to the feedback or replay.
Turn it on for the widget
Go to Feedback > Settings > Widget > Design > More.
Under Tracking, choose which console log levels to capture (Log, Error, Warning, Info, Debug), and separately, whether to capture Network Request data.
Place your widget's install code as close as possible to the opening <head> tag.
Capture starts from when the widget loads, so code placed later in the page misses anything that happened before it.
Turn it on for session replay
Go to Replays > Settings, and open the Dev Tools tab.
Toggle Network Requests on if you want session replays to capture outbound calls (CSS, JS, images, fonts, XHR, and similar). This is off by default.
Session replay's dev tools capture is available on the Business and Business Plus plans.
Where to view what's captured
From a feedback item: open its detail panel and click </> Dev Tools to open the drawer, with Console Logs, Network Requests, and Events tabs.
From a session replay: open the player and click </> Dev Tools for the same drawer, scoped to that recording. Here it shows Console Logs and Network Requests tabs.
Console log and event data is included when a feedback item is sent to an integration like Jira; network request data currently isn't.
What's next