Target recommendations in AJO email template | Community
Skip to main content
Best answer by Pulkit_Jain_

@michael_soprano 

Ok, yes, you can use a Custom Action in AJO to call an external API (i.e., Target Recommendations API) during the journey flow. The response from that API can then be mapped to journey attributes and used for personalization in email templates later in the journey, BUT here are the caveats:

  • The journey’s timeline now includes the external API’s response time. For high volumes, this may impact throughput.
  • You need to make sure the email template references the correct path to the recommendations; the path must be created each time. 

2 replies

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
August 11, 2025

@michael_soprano Have a look at this documentation.

https://experienceleague.adobe.com/en/docs/target/using/recommendations/recommendations-faq/integrating-recs-email

Thanks, Sathees
    Pulkit_Jain_
    Adobe Employee
    Pulkit_Jain_Adobe Employee
    Adobe Employee
    August 14, 2025

    @michael_soprano 

    Don't think that Target recommendations are directly embeddable in AJO email templates.
    Target recommendations are intended for real-time web personalization, not static or batch email. AJO email templates are rendered server-side at send time, not at open time, so dynamic JS calls (like Target offers) mightn't work. I haven't tested it, though.

    Any particular use case that you're trying to implement?

      Michael_Soprano
      Michael_SopranoAuthor
      Level 10
      August 14, 2025

      in AJO you have Custom Actions. During journey you can request Target Recommendations API and then put the response into AJO email template.

      What do you think?

      Pulkit_Jain_
      Adobe Employee
      Pulkit_Jain_Adobe EmployeeAccepted solution
      Adobe Employee
      August 14, 2025

      @michael_soprano 

      Ok, yes, you can use a Custom Action in AJO to call an external API (i.e., Target Recommendations API) during the journey flow. The response from that API can then be mapped to journey attributes and used for personalization in email templates later in the journey, BUT here are the caveats:

      • The journey’s timeline now includes the external API’s response time. For high volumes, this may impact throughput.
      • You need to make sure the email template references the correct path to the recommendations; the path must be created each time. 
        Terms & ConditionsAccessibility statement

        Loading footer...