Adobe Target Activity | Load Dynamic Content from Akamai in Experience Fragments | Community
Skip to main content
ambikaTewari_ATCI
Community Advisor
ambikaTewari_ATCICommunity Advisor
Community Advisor
May 30, 2023
Solved

Adobe Target Activity | Load Dynamic Content from Akamai in Experience Fragments

  • May 30, 2023
  • 1 reply
  • 1317 views

Hi Team,

 

We are using AEM fragments in Adobe Target Personalization activity. We are facing issue with the content rendering.

 

We have experience fragment with Product Hero component which is getting successfully exported except the Price Info to Adobe Target. The price info on the Hero component is inside the ESI tags. These ESI Tags within the fragments call the akamai to render the price
When we use this fragment in an activity, we see the content but not the price info.

So, we are looking for help how to populate the ESI tags (price) within experience fragment. 

 

Can anyone advise something on this ?

 

 

    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 nnakirikanti

    Hello @ambikatewari_atci Exporting the experience fragments from AEM to Adobe target will have only context of selector ".atoffer.nocloudconfigs.html" not the page context (like product you are dealing with) so export request for a fragment "xyz" looks analogous to /content/experience-segments/<<xyz>>.atoffer.nocloudconfigs.html, this would not be process by Akamai as it is missing product/page context...

     

    Recommendation to solve this use case:

    AEM Approach: 

    Add another component presentation(slightly) with atoffer.nocloudconfigs.html as the file name and replace the ESI price markup with "${mbox.productPrice}" and verify this markup get exported when activated or by accessing with ".atoffer.nocloudconfigs" selectors.

     

    Passing the Price info from Web to Adobe Target:

    Provide price info from clientside to Adobe target via "targetPageParams" or "targetPageParamsAll" to replace the price info and send back computed markup to end user.

     

     Approaches for making price info available for targetPageParams

     1) build REST API around pricing and make a immediate call (first top most call) to this API with context to get and set the target params.

     

    Let me know if you have any concerns or issues with this approach. 

     

     

     

     

    1 reply

    nnakirikanti
    Community Advisor
    nnakirikantiCommunity AdvisorAccepted solution
    Community Advisor
    June 5, 2023

    Hello @ambikatewari_atci Exporting the experience fragments from AEM to Adobe target will have only context of selector ".atoffer.nocloudconfigs.html" not the page context (like product you are dealing with) so export request for a fragment "xyz" looks analogous to /content/experience-segments/<<xyz>>.atoffer.nocloudconfigs.html, this would not be process by Akamai as it is missing product/page context...

     

    Recommendation to solve this use case:

    AEM Approach: 

    Add another component presentation(slightly) with atoffer.nocloudconfigs.html as the file name and replace the ESI price markup with "${mbox.productPrice}" and verify this markup get exported when activated or by accessing with ".atoffer.nocloudconfigs" selectors.

     

    Passing the Price info from Web to Adobe Target:

    Provide price info from clientside to Adobe target via "targetPageParams" or "targetPageParamsAll" to replace the price info and send back computed markup to end user.

     

     Approaches for making price info available for targetPageParams

     1) build REST API around pricing and make a immediate call (first top most call) to this API with context to get and set the target params.

     

    Let me know if you have any concerns or issues with this approach. 

     

     

     

     

      Abhishek-Lal
      Abhishek-Lal
      November 17, 2023

      Hi @nnakirikanti ,

      We have a similar issue

       

      We have experience fragment with a MFE component which has ESI tags. These ESI Tags within that MFE (Micro front end) component call the Varnish to render the MFE as a whole. 

       

      When the XF is exported to target, and target is trying to inject that XF on the page, the ESI tag is still visible in the markup and is not getting resolved. 

       

      Code from the sightly of that MFE component. mfeESIUrl is the URL of the MFE

      <esi:include src="${mfeESIUrl @2941342='unsafe'}" />

       

      So this same markup which is in the sightly of this MFE component, gets rendered by target without it getting resolved. I have attached the screenshot from the author, but a similar markup gets rendered when target injects it. I saw your response at https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/adobe-target-activity-load-dynamic-content-from-akamai-in/td-p/596069, but I couldn't process what you suggested.

      Could you please tell or explain in a bit more detail.

       

      Need your valuable suggestion. Thanks a lot

       

      Abhishek-Lal
      Abhishek-Lal
      November 21, 2023

      Hi @nnakirikanti  @ambikatewari_atci 

      Can you please help on what approach did you take to resolve this ?

      Terms & ConditionsAccessibility statement

      Loading footer...