Display problems and other issues sometimes occur in the Adobe Target Visual Experience Composer (VEC) and the Enhanced Experience Composer (EEC) under certain conditions.
Be aware of the changes that impact the VEC and EEC when using the following Chrome releases:
The following change affects all three updates outlined below:
Chrome 94 (September 21, 2021): With the impending changes planned for the Chrome 94 release (September 21, 2021), the following change impacts all users with Chrome 94+ browser versions:
--disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecurewill be removed.
Chrome 91 (May 25, 2021): With the changes implemented for the Chrome 91 release (May 25, 2021), the following change impacts all users with Chrome 91+ browser versions:
#cookies-without-same-site-must-be-securehave been removed from
chrome://flags. This behavior is now enabled by default.
Chrome 80 (August 2020): With the changes implemented in August 2020, all users with Chrome 80+ browser versions:
adobemc.com domain. Without this attribute, the browser rejects these cookies, causing the EEC to fail.
To determine which cookies are blocked because of the SameSite cookie enforcement policies, use the Developer Tools in Chrome.
To access the Developer Tools, while viewing the VEC in Chrome, click the ellipsis icon at the top-right corner of Chrome > More Tools > Developer Tools.
Click the Network tab > then look for blocked cookies.
Use the Has blocked cookies checkbox to make finding blocked cookies easier.
The following illustration shows a blocked cookie:
Starting with version 0.7.1, the Adobe Target VEC Helper browser extension adds the
Secure attributes to all cookies on responses originating from webpages edited inside the VEC when the “Cookies” toggle is turned ON in the extension UI:
Use one of the following options to ensure that your VEC and EEC continue to work as expected:
Download and use the updated VEC Helper extension.
Use the Mozilla Firefox browser. Firefox is not yet enforcing this policy.
Use the following flags to run Google Chrome from the command line until September 21, 2021. After September 21, features that require cookies will no longer work in the VEC, such as login or cookie consent popups. If you update to Chrome 94, you must manually generate cookies with
Secure on your websites.
Target does not support multi-level iframes. If your website loads an iframe that has a child iframe, at.js interacts with the parent iframe only. Target libraries do not interact with the child iframe.
As a workaround, you can add a page in the experience with the URL of the child iframe.
This situation can happen if the URL contains a # character. To fix the issue, switch into Browse mode in the Visual Experience Composer, and then switch back to Compose mode. The spinner should go away and the page should load.
If your website’s CSP headers block Target libraries, then loads the website but prevents editing, ensure that the Target libraries are not blocked.
In addition to the following information, you can use the Adobe Target VEC Helper browser extension for Google Chrome.
As a workaround, you can configure a Requestly rule to remove CSP headers, as shown below:
You can configure a similar Requestly rule for any header that causes a resource to not load inside the VEC.
For Requestly, whenever there is a need to remove headers, you should do either of following:
If the website has changed outside of the Visual Experience Composer after the experience was defined, selectors on which actions were taken earlier cannot be found when the activity is opened for re-editing. The page appears broken, and no warning displays.
If the same DOM element ID is used on multiple elements on the page, changing one of those elements changes all elements with that ID. To prevent this from happening, an ID should be used only once on each page. This practice is a standard HTML best practice. For more information, see Page Modification Scenarios.
This issue can be addressed by enabling the Enhanced Experience Composer. Click Administation > Visual Experience Composer, then select the check box that enables the Enhanced Experience Composer. The Enhanced Experience Composer uses an Adobe-managed proxy to load your page for editing. This proxy allows editing on iFrame-busting sites and allows editing on sites and pages where you have not yet added Adobe Target code. The activities do not deliver to the site until the code has been added. Some sites may not load via the Enhanced Experience Composer, in which case you can uncheck this option to load the Visual Experience Composer via an iFrame.
Your locally hosted pages or pages that are not accessible outside your network are not accessible to the Adobe proxy server and cannot be opened in the EEC. These pages might include staging URLs, User Acceptance Testing (UAT) URLs, or locally hosted pages.
See “I can’t edit experiences for an iFrame-bursting site” above.
If you use Edit Text/HTML in the Visual Experience Composer for A/B or Experience Targeting activities or Change Text/HTML for Automated Personalization or Multivariate Test activities to make text bold or italic, those styles might not be applied on the page or the text disappears from the page in the Visual Experience Composer. This happens because of the way the rich-text editor applies these styles might interfere with the website markup.
If you see this issue:
Click the HTML button in the rich-text editor to enter source editing mode.
Find the styles text elements.
For bold text, change
<strong> elements to
For italic text, change
<em> elements to
Adding an image offer to a location takes the full dimension of the original image space in the VEC or EEC. On delivery, the image is not expanded and is shown as it is, so there is no impact on delivery.