@AkshithaPo  There are several approaches available each offering unique advantages and catering to different needs. One primary approach involves leveraging the Out-of-the-Box (OOTB) schedule export option. This built-in functionality is designed for straightforward data extraction and can be parti...

@DN1191 Yes, this feature is available for email templates created with the AJO email designer. You can try using the HTML converter to enable the dynamic content option. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/channels/email/design-email/start-creating-content/existing-co...

@GigiCotruta It is not possible to post data into the profile level using a JSON structure with the update profile activity.

@Pradeep-Jaiswal STO is not available for campaigns.  https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/manage-journey/send-time-optimization

@RicardoALima Custom action can be used if the data lake offers a REST API. This allows for connecting to the API in a journey and generating a personalized token for emails, rather than storing it at the profile level.

@BrandonFa6 AJO will automatically exclude the profiles with email consent choice value = n. At the same time consider this call out "By default, the value for the consent field is empty and treated as consent to receive your communications. " https://experienceleague.adobe.com/en/docs/journey-optim...

@Michael_Soprano Although this is related to web in-app message. It has a manual trigger method mentioned on how to handle it through webSDK. https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/personalization/ajo/web-in-app-messaging

@HardikJa3I encountered the same error when attempting this. It appears that content experiments are not supported with Marketing triggered API campaigns. I recommend contacting Adobe support for clarification and, if necessary, submitting an enhancement request.  

@RicardoALima Unitary events can be used in this case to initiate a journey, enabling both the triggering of the journey and personalization. This personalization can be achieved using data from the event's context, including the ability to personalize URL parameters directly.   Given this, the seco...

@AkshithaPo Throttling works per host and per sandbox. It will not be at the journey level. "A capping limit of 300,000 calls over one minute is defined for all custom actions. In addition, the default capping is performed per host and per sandbox. For example, on a sandbox, if you have two endpoint...