Adobe Target - Visual Experience Composer vs Forms Based

Hi @clodo 

I have been using adobe target since 4+ years now and below are my thoughts on your question.

VEC pros -

1. If you are beginner to AT, VEC makes it very easy for you to edit pages, without having coding knowledge.

2. Modifying CSS, layout, content is too easy with help of VEC

3. VEC also allows you to add custom codes in case you want to do something extra which is not available in VEC to edit pages.

4. Adding page delivery to deliver content on multiple pages is easier as compare to FEC.

5. If you use FEC and use HTML offer, trying to edit something on page, you need to write a code to wait for element to load whereas this thing is automatically handles by VEC when you create activity using VEC.

VEC Cons - 

1. You cannot use custom mboxes in VEC.

2. when you click on any element on page to modify, it selects absolute path of the element, for example, div>ul:eq(3)>li:eq(2), now lets say client removes one ul from the page there will be only two uls and "div>ul:eq(3)>li:eq(2)" this selector wont work and changes wont get reflected on page.

3. remote offers does not work in VEC

FEC Pros - 

1. Can use custom mboxes

2. Can use multiple kindof offers. e.g. JSON,remote etc.

FEC Cons -

1. Not a great UI to setup activity.

2. You should have coding knowledge (atleast HTML, CSS, JS)

3. Easy edit options like you get in VEC wont be available (e.g. click and edit different elements)

@clodo please feel free to add up if you have any other queries regarding FEC/VEC.