Hi @piyushvidhate ,The extension is disabled in the browser."frame-ancestors" directive is configured by the application team on the web server side. 

Update: Adobe support recommended updating the extensions, which solved the problem.

Hi,It looks like it is something more complex than the extension configuration or the contents of the library. The team decided to contact Adobe Support; we are waiting for the results of their investigation.

Hi,I am integrating Target into a mobile app. I have an existing Launch property where "Mobile Core", "Identity", "Profile", and "Adobe Analytics" extensions are added and promoted to Production.I added Target extension, placed it to in new library, and built the library to Development. The Developm...

It turns out that it was "Adobe Experience Cloud Visual Editing Helper" extension that prevented setting the current view. I disabled the extension and added "frame-ancestors" directive to the CSP header, and it now works.

Hi Everyone,I am trying to get an Angular-based SPA working in Visual Experience Composer. The application has the following in targetGlobalSettings:{ cookieDomain: <domain here>, viewsEnabled: true, pageLoadEnabled: true }The application uses AEP Data Collection (Adobe Launch) to load Target a...

Ok, it turned out that I just needed to set cspScriptNonce in targetGlobalSettings. const nonce = <getting-the-nonce-value>; window.targetGlobalSettings = { . . . cspScriptNonce: nonce }; 

Hi Everyone,I am currently integrating Adobe Target into a site that uses Content Security Policy (CSP) headers with nonce values for third-party and inline scripts:Content-Security-Policy: script-src 'nonce-<value>' I am using Adobe Launch to load Target. Adobe Launch supports nonce and successfull...

@Gokul_Agiwal, the correct answer is "2" (Visitors are able to fulfill their purpose on the page and leave) if it is a content page. For pages that are part of a flow, like a purchase flow in eCommerce, that's not the case.

"Goals and Settings"