The FullStory integration with Bugsnag lets you see the FullStory session associated with the JavaScript exception. If you haven't already, sign up for Bugsnag

After you setup your Bugsnag account, make sure the Bugsnag script is installed.


  1. Login to FullStory
  2. Navigate to Settings > Integrations & API Keys
  3. Toggle on Bugsnag under Available Integrations.


Now, when you open a Javascript exception in Bugsnag, you'll see a FullStory tab containing a clickable play-back link to the session in which the Javascript exception occurred.


If you would like to be linked directly to the exact moment in the session that the Javascript exception occurred, you can modify your Bugsnag implementation code. Here's some sample code, that was passed along to us by one of our users, to help you get started (thanks, Cameron!).

If you're using version 3 of the Bugsnag API, add the following code after you set up the Bugsnag script.

// capture fullstory url at current time	
// make sure fullstory has started recording (the getCurrentSessionURL method exists)	
bugsnag.beforeNotify = (payload, metaData) => {	
    // our existing beforeNotify block...
    if (window.FS && window.FS.getCurrentSessionURL) {	
        if (!metaData.fullstory) {	
            Object.assign(metaData, { fullstory: {} });	
        Object.assign(metaData.fullstory, { urlAtTime: window.FS.getCurrentSessionURL(true) });	

If you're using version 4 of the Bugsnag API, use the following code to create the Bugsnag client.

window.bugsnagClient = bugsnag({
    apiKey: 'API KEY',
    beforeSend: function (report) {
        // Make sure FullStory object exists.
        if (window.FS && window.FS.getCurrentSessionURL) {
            report.updateMetaData('fullstory', {'urlAtTime': window.FS.getCurrentSessionURL(true)});

Need to get in touch with us?

The FullStory Team awaits your every question.

Contact us