Using exported AEM Experience Fragment to Adobe Target not working | Community
Skip to main content
J
jainrupal2408
Level 3
February 22, 2024
Solved

Using exported AEM Experience Fragment to Adobe Target not working

  • February 22, 2024
  • 2 replies
  • 1433 views

Dear All, 
We are using AEM cloud and have been able to export the experience fragments from AEM to Adobe Target. They show under Offers inside Adobe Target. However, when I create an activity, and try to replace the content with Experience Fragment, it shows 0 results. 

 

Has anyone else facing the same issue? Is there anything I am missing ? Please find below the screenshots - 

 

Many thanks

Best,

Rupal

 

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 jainrupal2408

I found the root cause. While exporting the Experience Fragment, I need to make sure it is exported in "HTML" format. This can be done by selecting export format either "HTML" or "HTML&JSON" . 

Once HTML version of XF is exported and seen in Offers tab, then it can be used in VEC.

2 replies

alexbishop
Adobe Employee
alexbishopAdobe Employee
Adobe Employee
February 22, 2024

How are you creating your Target activity? If you're creating it via the Visual Editor then you would only see HTML Experience Fragments when using that "Replace Content > Experience Fragment" option

    J
    jainrupal2408Author
    Level 3
    February 22, 2024

    Dear @alexbishop ,
    Yes I am using VEC Editor. Do you mean any of my components which have clientlib or JS code wouldn't be visible?
    If not, then how can I utilize those?

    J
    jainrupal2408AuthorAccepted solution
    Level 3
    February 26, 2024

    I found the root cause. While exporting the Experience Fragment, I need to make sure it is exported in "HTML" format. This can be done by selecting export format either "HTML" or "HTML&JSON" . 

    Once HTML version of XF is exported and seen in Offers tab, then it can be used in VEC.

    Terms & ConditionsAccessibility statement

    Loading footer...