Optimize Custom Action using API in AJO | Community
Skip to main content
X
xliu
Level 3
February 13, 2024
Solved

Optimize Custom Action using API in AJO

  • February 13, 2024
  • 3 replies
  • 3138 views

Hi,

 

We have a custom action in AJO which will send API calls to an endpoint and get payload data for campaigns. However, I checked this document (https://experienceleague.adobe.com/docs/journey-optimizer/using/configuration/configure-journeys/action-journeys/action-response.html?lang=en) which says one API call per profile even if the response always the same. So if an audience is 50,000 large, it will send 50,000 API calls.

 

So my question is whether there is a way to optimize the number of API calls? Or cache the payload in AJO? Or start a journey at midnight? Any solutions to reduce the number of API calls?

 

Thanks

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 SatheeskannaK

@xliu, There are no ways to optimize the number of API calls when using custom actions. There will be one API call per profile. However, if the response from the payload is common across all profiles, and you want to optimize API calls, you may consider ingesting that data in AEP and enabling it for activation with profiles to use in the journey. It requires larger solutioning.

3 replies

SatheeskannaK
Community Advisor
SatheeskannaKCommunity AdvisorAccepted solution
Community Advisor
February 13, 2024

@xliu, There are no ways to optimize the number of API calls when using custom actions. There will be one API call per profile. However, if the response from the payload is common across all profiles, and you want to optimize API calls, you may consider ingesting that data in AEP and enabling it for activation with profiles to use in the journey. It requires larger solutioning.

Thanks, Sathees
X
xliuAuthor
Level 3
February 14, 2024

Thank you @satheeskannak , the reason we think custom action might be a better solution is that the external data always changing, so when we run a journey, the payload always returns the latest data.

 

In this case, any suggestions on how to store this dynamic data to AEP?

 

Thank you so mcuh.

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
February 15, 2024

Got it. If the data is always changing, you will have to use a custom action, and of course, that will eat up your engine calls. If you’ve to ingest dynamic data in AEP, use the data flow or flat file approach.

Thanks, Sathees
A
Adobe Employee
AnanthanJaAdobe Employee
Adobe Employee
February 14, 2024

Hi @xliu,

 

If batch operations / file-based destinations are fine to provide, then you can look at using RTCDP destinations to push the profile segment to the customer destination.

Mohan_Dugganab
Adobe Employee
Mohan_DugganabAdobe Employee
Adobe Employee
February 14, 2024

Custom actions should ideally be used with unitary journeys where the volumes are discrete.

This is basically to avoid overwhelming the REST API endpoints when an audience is used.

 

In your case, you should  explore HTTP API for destinations to see if that meets your requirement https://experienceleague.adobe.com/docs/experience-platform/destinations/catalog/streaming/http-destination.html?lang=en

Terms & ConditionsAccessibility statement

Loading footer...