Debugging website widgets

Due to the amount of variables it's not always straightforward to figure out why exactly a survey triggers/doesn't open for a visitor.

To find out more about the underlying reasons, Feedbackly provides the means to debug this.

If you need to check the installation status of a widget, please see Verifying installation.

List all triggering options available to the visitor

When on your website and with Feedbackly widget installed, open up the dev tools for the browser. In Chrome, this can be done via the command ⌘ + option + J

Run the following command:

FBLY.getConfiguration();

The console should print out an array of configuration objects similar to this:

This is in essence the JSON-representation of your website triggering parameters available on the Feedbackly UI's widget triggering parameters. All the objects in this array are the potential surveys to be shown to the user when conditions are met.

Listing client data

To find out what data the widget has recorded of the visitor, run

FBLY.getClientData();

This data can be useful in determining whether the visitor has met the conditions for a survey to be triggered.

A few remarks on the properties:

• session.declinedActivations lists whether the user has declined a survey, its id and timestamp

• session.sampledActivations shows whether the visitor fits to the sample of the survey

• visitedUrls shows all visited urls of the visitor

• scroll shows the current page scroll of the visitor

Automatic debugging with Universal Widget Script (2024->)

To see loading information and created objects in a browser console, enable automatic debug mode by adding this to the end of your page URL (can also be set as a URL parameter):

#debug=true

or edit the original script tag to add following configuration for dev/test sites:

fblytag('debug', 'true');