@Michael_Soprano By default, the AJO will wait approximately 30 seconds for an API response before proceeding to the next node. This duration can be adjusted if needed. Have a look at this page, https://experienceleague.adobe.com/en/docs/journey-optimizer/using/connect-systems/external-systems/exter...

@MarzenaRa  Verify AJO licensing on the following: To access Campaign Orchestration, your license must include either the Journey Optimizer – Campaigns & Journeys or the Journey Optimizer - Campaigns package. Contact your Adobe representative to confirm your license and update if needed. Learn more ...

@Pradeep-Jaiswal You don't necessarily need to keep all the personalization data in the profile store.Take a look at this documentation, https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journey-building/dataset-lookup

@user61843  Assuming you've enabled the testProfile flag, have you tried the "simulate content variations" option? More details can be found here: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/test/preview-test/simulate-sample-input If you're using personalization functions to d...

@MarzenaRaDeduplication, a feature of Orchestrated campaigns in AJO, relies on a relational datastore for its capabilities and is not available for use in Journeys. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/campaigns/orchestrated-campaigns/orchestrated-campaigns-faq

@Michael_Soprano  Custom Actions within AJO are designed to operate asynchronously. When AJO initiates a Custom Action, it dispatches an HTTP POST/GET request to the specified external API endpoint. AJO's interaction with your API is limited to awaiting an immediate HTTP response, such as a "200 OK"...

@HardikJa3 The success metric relies on the Reporting and data configuration settings (under Configurations -> Reporting). Provided that the prerequisites outlined in the documentation are met, you will be able to select a success metric based on your event schema and dataset. Have a look at this pa...

@TapanSaikiaTo optimize the process and mitigate potential rendering issues, I recommend structuring the HTML within the AJO email builder. This way, you can ensure that only essential contextual personalization data is passed, thereby circumventing the complexities and errors that can arise from di...

@HardikJa3 You should have each treatment performance available in both AJO and CJA. Refer to the documentation: https://experienceleague.adobe.com/en/docs/analytics-platform/using/integrations/ajo CJA should have corresponding components and metrics related to experimentation.

@MarzenaRa AJO's journey capping and arbitration features, combined with a well-defined rule set, can effectively limit the number of messages a profile receives. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/conflict-prioritization/capping-rules/journey-capping