[Troubleshooting] QA Assistant doesn’t load on my website

🛠️ [Troubleshooting] QA Assistant doesn’t load on my website

This article will explain how to solve specific issues with the QA Assistant.

⭐ Tip: You can trigger the QA Assistant module by pressing ctrl+Q+A or by adding ?abtasty_qa_assistant=true at the end of your website URL.

To access the QA Assistant, your campaign doesn't specifically need the "in QA" status. You can view all campaigns that are live on your page or website. Press Ctrl+Q+A on your website to open the window and check your campaigns.

If you have tried to launch the QA Assistant from AB Tasty or the keyboard shortcut but nothing appears on your page, this could come from one of the following reasons:

The tag is not present on the page

To function properly, the tag must be present on the page where you want to apply your changes. To check if the tag is present on the page, read How to check if the AB Tasty tag is installed?

My browser configuration doesn't allow third-party cookies

We use cookies to validate your authentication. If you see the "Disabled cookies" error in the QA Assistant, it means that you need to enable third-party cookies:

Enabling cookies in Safari (desktop or mobile):

1. Go to the Safari drop-down menu

2. Select Preferences

3. Click Privacy in the top panel

4. Turn off Prevent cross-site tracking and Block all cookies

If the issue persists, open Safari’s Preferences > Privacy and disable the Prevent cross-site tracking, and Block all cookies options.

Enabling cookies in Mozilla Firefox:

1. Go to the Firefox drop-down menu

2. Select Preferences

3. Click Privacy

4. Under Cookies, select Accept cookies from sites

5. You may need to restart your browser to proceed

If the issue persists, open Firefox’s Settings > Privacy & Security > Enhanced tracking protection and select the Custom option, then change Cookies to Cross-site tracking cookies.

Enabling cookies in Google Chrome:

1. Open Chrome’s Preferences, click Settings, then Show Advanced Settings

2. Near the bottom of the page, select Show advanced settings

3. Under Privacy and security, click Cookies and other site data

4. If Allow all cookies is not enabled, Add [*.]abtasty.com in the Sites that can always use the cookies section

There is a cache issue on your browser

1. Check whether the QA Assistant opens on an Incognito browser window. If the module appears when your browser is set to Incognito, your cache might be blocking the display in the regular browser.

2. If so, clear your cache on your browser by performing a hard reload:

• Type Ctrl+F5 (on Windows) or Cmd+Shift+R (on a Mac)

• Or click on the browser’s page reload button while holding Ctrl

A browser extension is blocking the QA Assistant

In Chrome, Firefox, and Safari, various extensions may prevent the QA Assistant from loading.

To disable Chrome extensions, follow these steps:

1. In your Chrome browser, click > More tools > Extensions

2. Switch Off the push button

3. Repeat step 2 to disable each extension manually

The Ghostery extension may cause multiple issues.

There is a Content Security Policy (CSP) error in the console

If you notice Content Security Policy errors in the console when you try to load the QA Assistant, there is a problem with your server configuration. Content Security Policy may be blocking everything on your website. This means that you have to individually approve every external request and allowlist them on the server configuration.

To resolve this issue, consult the back-end developers of your website and allowlist the *.abtasty.com domain in your Content Security Policy.

Other authorizations may be needed, such as blob, and so on. All details are visible in the console errors.

As a workaround you could try downloading the Disable Content Security Policy Chrome Extension.

In most cases, if QA Assistant doesn’t load on your website, it is due to one of these reasons. If this article doesn’t resolve the issue, contact the Support Team or your dedicated CSM.