Highlighted

Personalisation within AEM with Target vs Target VEC

venkataraog3404

15-10-2018

Wanted to understand are there benefits using AEM with Target vs Target Visual Experience Composer. As per my understanding, I see the following pros and cons with both the approaches, But not sure which one is better for Business/Marketing Users.

This is all based on the 6.3.2.2 AEM with Feature packs

Personalisation using AEM + Target

Pros

  1. Leverage full potential of the AEM Authoring capabilities while authoring the personalised content
  2. Can create offers with in Offers library and/or from page authoring in Target Mode itself
  3. Content will be delivered right from the AEM

Cons

  1. Complex configuration with AEM Target and AT4JS
  2. Integration issues (Sometimes integration is not working well)
  3. Cannot target multiple pages at the same time
  4. Multi page workflow is not possible
  5. Limitations of the targeting mode to personalise based on the Breakpoints
  6. Cannot leverage Auto-Target

Personalisation using Target with VEC

Pros

  1. Easily change/swap content visually.
  2. Multiple pages can be targeted at the same time
  3. Multi page workflow can be created
  4. Personalisation for multiple breakpoints for the same experience
  5. Can use experience fragments

Cons

  1. Coding skills required to create offers that contains html and css by business/marketers
  2. Modifying/configuring an AEM component is not possible as it is in the AEM. Need to modify either  element by element or swap with HTML offers.
  3. Cannot reuse offers created in AEM from with in Target (Can be achieved if experience fragments are used)

Is my understanding correct?

Are there best practices when using both AEM and Target together or individually leveraging each platforms capabilities?

Replies