Hi @chrisyan , Pls check if the attributes that you are looking is properly configured/enabled in data source  or not ? Check the following link for more details :- https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configuration/configure-journeys/data-source-journeys/about-data-sou...

 

Pass the "From" address as a variable to String {%= extractEmailDomain(string) %}  to retrieve the domain name. Thanks, Somen

Hi @Ajo_WisdomChase ,You can utilize OOTB Helper function {%= extractEmailDomain(string) %} to achieve the same . In Email body personalize the same using the above mentioned function. Hope this will help you in achieving the objective. Thanks,Somen

Hi @AkramH , What part/section of AJO are you planning to customize with stylesheets  ? Could you elaborate more on the use case ?   Thanks, Somen

Hi Mikael, The calculation of how many times an offer is proposed happens when the email is being prepared, not when it is sent. This means that the system evaluates and counts the offers during the preparation phase.     The offer capping is calculated based on the chosen audience for the campaign ...

HI @Michael_Soprano , Yes, both Presets and Subdomains need to be configured in Adobe Journey Optimizer (AJO) to create and publish a landing page. Presets :- Presets in AJO are templates or predefined settings that streamline the creation and management of landing pages, ensuring consistency and ef...

Hi @Havilah , Yes, a profile can be present across different journeys at the same time in Adobe Journey Optimizer (AJO). This flexibility allows you to engage with customers through multiple journeys based on different triggers, conditions, and business objectives simultaneously. The below article g...

Hi @kurtCleOH , Prod env content are always latest and that is the reason why content sets are always propagated to higher to lower envs.  "Exclude Path" option can be utilized while building the package in case some content on lower environment is not required.     https://experienceleague.adobe.co...

In this case the issue can be in the format of the lookup  file  that you are trying to attach  or  pipeline script might have some specific conditions that it checks.  As per current documentation every yaml file has a common syntax like  below .  kind: "LogForwarding" version: "1" metadata: ...