Visual editor diagnostics alert you when you modify an element that has changed location or structure on a dynamic page. This will help you diagnose problems with your experiments on dynamic pages.
How it works
Editor diagnostics keep a copy of the original document and apply each change to both the current document and the original document, so that the editor knows if the elements have been changed between when the document loads and when the editor applies the change.
Two types of Optimize containers
- Stored containers include all draft, ended, and archived experiences (and their metadata) created in a given container and contribute to its overall "stored container" size. Stored containers aren't compressed. To reduce the size of a stored container delete some of its draft experiences.
- Served containers only include the running experience(s) and the data is compressed. To reduce the size of a served container: end some of its experiences.
If elements on the web page have changed since initial loading, Optimize displays the following diagnostic alerts in several areas of the visual editor:
An alert icon appears in the app bar:
Clicking the alert icon in the header will reveal the Diagnostics slider, with more information:
In addition to the alert icon in the header, diagnostic alerts will also appear in the change list next to any change where an error is detected.
Click on the alert icon in the change list to see more details about the alert:
|This page is not tagged with the Optimize snippet. To run experiments on this page, you must install the Optimize snippet with the ID: GTM-123X||No Optimize snippet found. Check that the Optimize snippet has been added to the page.|
|This page is not tagged with Google Analytics snippet. To run experiments on this page, you must install the Analytics snippet for the tracking ID: GA-10000-1||No Analytics snippet found. Check your Google Analytics tracking code setup.|
|No matching elements found. Please update your selection.||The selector in the change doesn’t match any elements. This is likely caused by a change in HTML structure after the edit was created in the editor.|
|The original elements used to create this change are not included. Make sure your changes are rendering correctly by using preview mode.||When you edit a change and change the selector, it may not select the element that was used to create the change.|
|The number of target elements for this move operation has changed. The number of target elements selected in the editor is different from the number of target elements selected when the experiment would run. Make sure your changes appear as expected using preview mode.||For the move change, there are selectors for the source elements and selectors for the target selector. This warning occurs when the number of elements selected by the target selector is different than the number selected when the page loads.|
|There are more target elements than source elements in this move operation. Remaining target elements will be ignored.||Just a warning that there are more target elements than source elements selected in the move change and the remaining target elements will be ignored.|
|This change cannot be applied, as the page may have been modified after this change was created.||A text change selects an element first and then changes the text node at a specified childIndex position. This warning occurs when the childIndex is out of bounds or does not point to a text node. Most likely caused by structure change in the page after the change was created.|