Once you have entered the information related to your campaign in the Main information step, you need to apply your changes via the AB Tasty editor.

The editor enables you to modify the disposition, appearance, and content of your pages.

If your website won’t load in the editor, it may be due to one of the following reasons:

A Chrome extension is blocking the editor
There is an unexpected JavaScript behavior
There are AB Tasty related errors in the console
There is a Content Security Policy error
The tag is not present on the page

A Chrome extension is blocking the editor

In Chrome, various extensions may prevent the editor from loading.

Disable all Chrome extensions

To disable Chrome extensions, apply the following steps:

From your Chrome browser, click “...” > More tools > Extensions.
Switch OFF the pushbutton.
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 easily turn Chrome extensions on and off.

The Ghostery extension may cause multiple issues.

Close existing Incognito windows

Close all existing Incognito windows.
Open a new one (by default, extensions are not loaded in Incognito)
Load the editor.

There is an unexpected JavaScript behavior

If the problem is linked to an unexpected JavaScript behavior on your website, you can try different solutions.

Use the Reset JS behaviors feature

The AB Tasty editor uses native JavaScript functions. On your website, the native JavaScript functions may have been rewritten.

The Reset JS behaviors option available in the AB Tasty Chrome extension is dedicated to websites that rewrite native JavaScript functions.

This feature, when enabled, enables the AB Tasty editor to save the functions before they are rewritten by the clients.

To do this:

Enable the AB Tasty Chrome extension.
Make sure the Reset JS behaviours box is checked.
Click the test in the AB Tasty Chrome extension.
Click Editor.

If this solution doesn't work, try to apply source code with source code.

Apply source code (with source code)

Another solution is to apply the source code. To do so, apply the following steps:

Open the page you want to load in the editor in your browser.
Right click View Page Source.
Copy the HTML code of the page.
Go to the Main information step of your campaign (step 1) in AB Tasty.
Paste the code into the Apply source code section.

For more information, refer to How can I test a page that requires a login, or one that requires session information?

Apply source code (with executed code)

To apply source code with executed code, apply the following steps:

Open the page you want to load in the editor in your browser.
Right click Inspect.
In the Elements tab, look for the <html> tag that must be located at the very top.
Right click Copy > Copy outerHTML.
Go to the Main information step of your campaign (step 1) in AB Tasty.
Paste the code into the Apply source code section.

Apply source code (on an existing campaign through the AB Tasty Chrome extension)

To apply source code on an existing campaign through the AB Tasty Chrome extension, apply the following steps:

Open the page you want to load in the editor in your browser.
Click the AB Tasty extension.
Select your test.
Click Apply HTML.
Click Editor.

Applying source code is also an effective method to load funnel pages.

There are AB Tasty related errors in the console

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

Open your browser’s console.
Right click Inspect and click the Console tab.
Make sure there are no AB Tasty errors or server errors.

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

There is a Content Security Policy error

If you notice Content Security Policy errors in the console when you try to load the editor, the current problem must come from your server configuration.

Content Security Policy may be blocking everything on your website. This means that you have to individually approve every single external request and whitelist them on the server configuration.

To address this issue, refer to the back-end developers of your website in order to whitelist the *.abtasty.com domain in your Content Security Policy.

Other authorisations may be needed such as "unsafe-eval" / "unsafe-inline" / “blob“, and so on. All details are visible in the console errors.

The tag is not present on the page

In order to work properly, the tag must be present on the page which you want to apply changes to.

To know if the tag is present on the page, apply the following steps:

Open a private browser window.
Enter the URL of the page you want to load in the editor.
Right-click and select Inspect:
The console is displayed.
Go to the Elements tab.
In the HTML code, look for try.abtasty.com.

Console_try.abtasty.png

If there is no answer, this means the tag is not present on the page. In this case, open the AB Tasty extension and click Inject script.

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

In most cases, if your website doesn’t load in the editor, it is due to of these reasons. If this isn’t the case, please contact your dedicated CSM.

How do I install AB Tasty on my site?

How can I test a page that requires a login, or one that requires session information?

The AB Tasty Chrome Add-on

Articles in this section

My website won’t load in the editor