Regarding MFE component in AEM exported to Target | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Matthew_Ravlich_ACG

@gokul_agiwal - sorry, I assumed from the question it was already exported as an offer in Target. If it is built in a JavaScript framework such as react, it will need to be rendered to HTML and then exported via AEM to Target as an experience fragment.

Matthew Ravlich | ACG Digital | albertacg.com

1 reply

Matthew_Ravlich_ACG
Community Advisor
Community Advisor
July 25, 2024

Hi @devakrishnara2,

 

You can consume Experience Fragments in Target activities using the VEC and form-based composers. Content Fragments can only be consumed by the form-based composer. You should not have an issue using your AEM component exported to Target. Follow the form-based experience composer documentation to build your activity.

 

More about experience fragments and content fragments can be found here: https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/content-fragments/understand-content-fragments-and-experience-fragments#_blank

I hope that helps.

Matthew Ravlich | ACG Digital | albertacg.com

 

Gokul_Agiwal
Community Advisor
Community Advisor
July 25, 2024

Hi @matthew_ravlich_acg - Thanks for the info 

Quick question - if AEM component or in above case Micro Front End component develop using JS framework like ( React and Angular) then how could we use those component as experience fragment into Adobe Target? 

As Adobe Target only accept the Experience Fragment either into HTML or JSON form.  

Level 2
July 26, 2024

@gokul_agiwal - sorry, I assumed from the question it was already exported as an offer in Target. If it is built in a JavaScript framework such as react, it will need to be rendered to HTML and then exported via AEM to Target as an experience fragment.

Matthew Ravlich | ACG Digital | albertacg.com


@matthew_ravlich_acg  thanks for the response.