Could someone please explain the difference between VEC and Enhanced Composer?
Our site uses WURFL device detection and mobile viewports are not working with Target.
Sometimes we manage to get into mobile view by switching to Enhanced Composer and it stays in mobile view until Enhanced Composer is switched off (even when changing viewport to desktop again).
Any other solutions or workarounds than moving from adaptive to responsive?
Solved! Go to Solution.
Hi there and thanks for your question! You might find this chart helpful:
Choosing between the Visual and Enhanced Experience Composers
The table below shows which experience composer option best supports frequently encountered issues.
Visual Experience Composer Support
Enhanced Experience Composer Support
|Mixed Content||Mixed content can be enabled for the current session.||Supported.|
|X-Frame-Options||Use browser add-ons, such as Requestly on Chrome, to bypass x-frame-options.||Supported.|
|Cross Origin Issues||Supported.||Not supported.|
|Authentication Workflow||Supported. If authentication works in an iFrame, it will work in the Visual Experience Composer.||Depends on implementation.|
|IP Blacklisting||Supported.||Proxy server IP addresses must be whitelisted.|
You can read more on this page on Experiences in the Adobe Target Help Documentation. Feel free to reach out here if you need more information!
Unfortunately this does not answer my question. I would like to figure out, why mobile viewports occasionally work with EEC, but not with VEC?