Difference Between Visual Experience Composer and Form-Based Experience Composer in Adobe Target

[VishnuPriya98]

Hi everyone,

I'm currently working with Adobe Target and I'm trying to understand the key differences between the Experience Composer's Visual and Form modes. Could someone explain how these two modes differ in terms of functionality, use cases, and when it's best to use each one?

Thanks in advance for your help!

[pradnya_balvir · Accepted solution]

Hi @VishnuPriya98 ,

• VEC

  Allows users to create responsive websites, preview experiences, and use overlays to highlight elements. Users can also rename and duplicate experiences, create redirects, and target activities to specific URLs or groups of URLs. 
• Form-Based Experience Composer

  Allows users to create non-visual experiences that can be delivered in emails, kiosks, and other places that don't work with the VEC. It also enables Target Standard A/B tests, Experience Targeting, Automated Personalization, and Recommendations activities. 

  You can refer below links for more information.

  https://experienceleague.adobe.com/en/docs/target/using/activities/activities#vec

  https://experienceleague.adobe.com/en/docs/target/using/experiences/form-experience-composer

[Ryan_Roberts_]

Hi @VishnuPriya98,

You got a good response already from @pradnya_balvir. I might add this:

• VEC works with typical out-of-the-box client-side deployments of Target on websites
  • Can use visual (point and click) methods to create and edit experiences, or you can use custom modifications with custom code
  • Generally this is easier to use
  • Designed for business/marketing users, but has features for all types of users
• Form composer works with custom, mobile, iOT, server-side, etc deployments of Target
  • Experiences are composed with code, text, JSON etc.
  • Suitable for more technical users
  • Can also be used in OOTB Target deployments