Debugging
To troubleshoot issues with AB Split Test, you use your browser's developer console together with AB Split Test's built in debug mode.
Turning on debug logs
Console logs are hidden by default and to turn it on, add ?abstdebug=1 to the end of any page URL where your test is running.
Example:
yoursite.com/your-page/?abstdebug=1
Once you load that URL, open your browser console and you will see AB Split Test log messages showing exactly what the plugin is doing: which test is running, which variation was assigned, whether a conversion fired, and any errors encountered.
The debug parameter only activates for that browser session on that page. It does not affect your visitors or your live test data.
How to open your browser console
Google Chrome
- Open the Chrome menu (three dots, top right).
- Select More Tools, then Developer Tools.
- Use the shortcut
Option + Command + Jon Mac orShift + Ctrl + Jon Windows and Linux. - Select the Console tab.
Mozilla Firefox
- Click the Firefox menu (three lines, top right).
- Select More Tools, then Browser Console.
- Use the shortcut
Shift + Command + Jon Mac orShift + Ctrl + Jon Windows and Linux.
Apple Safari
- Go to Safari, then Preferences, then Advanced.
- Check the box that says "Show Develop menu in menu bar".
- Click Develop, then Show JavaScript Console.
- Use the shortcut
Option + Command + C.
Microsoft Edge
- Open the Edge menu (three dots, top right).
- Select More Tools, then Developer Tools.
- Use the shortcut
Ctrl + Shift + I. - Select the Console tab.
What to look for
Once debug mode is on and the console is open, load your test page. You should see messages from AB Split Test showing the test ID, the assigned variation, and conversion tracking activity.
If you see no AB Split Test messages at all even with ?abstdebug=1 active, clear your website cache and reload the page.
If you find errors or need further help, send a screenshot of the console output to support@absplittest.com and the team will take a look.