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.

The QA Assistant module doesn’t load on the page

If you have tried to launch the QA Assistant from AB Tasty or the keyboard shortcut but nothing appears on your page, first check the following:

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
  
  

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, follow these steps:

1. Open an incognito (private browser) window
2. Enter the URL of the page you want to QA
3. Right-click and select Inspect – this displays the console
   
4. Go to the Elements tab
5. In the HTML code, look for try.abtasty.com

For more information on the AB Tasty tag, refer to How do I install AB Tasty on my site?

I don’t see my campaign on the QA Assistant

Some changes are automatically saved, such as in the Editor step. Others require manual saving, such as Targeting, Traffic allocation, etc. If the most recent update of the Tag took place before your last changes or is too old, some changes may not be applied to your site and will therefore not appear in the QA Assistant. 

To update the tag from the QA Assistant, click on the Refresh tag button and refresh the webpage.

Ensure you are using the latest version of your tag to include all your recent changes. To do this, click the Refresh tag button on the top barre of the AB Tasty platform.

To find out more, see the following article

A browser extension is blocking the QA Assistant

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

Disable all Chrome extensions

To disable Chrome extensions, follow these steps:

1. In your Chrome browser, click > More tools > Extensions
2. Switch Off the pushbutton
3. Repeat step 2 to disable each extension manually
   

To disable all Chrome extensions at once, you can use the Extensity extension, which enables you to turn Chrome extensions on and off easily.

The Ghostery extension may cause multiple issues.

Close existing Incognito windows

1. Close all browser windows you’ve opened in Incognito mode
2. Open a new one (by default, extensions are not loaded in Incognito mode)
3. Trigger the QA Assistant using the ctrl+Q+A keyboard shortcut or by adding the ?abtasty_qa_assistant=true URL parameter
   
   
   

There are AB Tasty-related errors in the console

There may be errors related to AB Tasty in the console. To check, follow these steps:

1. Open your browser’s console
2. Right-click Inspect and click the Console tab
3. Check for any AB Tasty errors or server errors
   

If you notice the following error in the QA Assistant:

And this error in the console:

If you notice any other errors, please contact your dedicated CSM.

There is a Content Security Policy 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 unsafe-eval, unsafe-inline, blob, and so on. All details are visible in the console errors.

My browser configuration doesn’t allow third-party cookies 

We use cookies to validate your authentication. To enable third-party cookies, follow these steps:

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

Mobile iOS – My status is “QA rejected” when the parameter is valid

When opening the QA Assistant on iOS devices, the campaign status shows QA Rejected even though your IP matches the QA mode value. 

To resolve this, follow these steps on your iOS device: 

1. Go to Settings and select Safari
2. In the Privacy & Security section, turn off Prevent cross-site tracking and Block all cookies
3. Now click Hide IP address and select Off
   
   

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 your dedicated CSM.