However on a different note I'm facing some delivery issue with my transactional email. Below is a screenshot of the overall email delivery associated with my Real Time event.But on checking the sending logs, below is what I see and I've not received any emails in my inbox as well. 

Thank you @SatheeskannaK I have been using Adobe I/O for the API interaction. After some exploration, I managed to uncover the root of the issue. Specifically, when dealing with sandbox instances, it's important to utilize the complete URL, such as acsXXXus.campaign-sandbox.adobe.com, as the organiz...

Thank you. However the ACS URL I use to access campaign is https://acsXXXus.campaign-sandbox.adobe.com/

Trying to send a POST request to the Campaign API, I'm getting the following error,"No match in backends for the given tenant id."The campaign instance I'm using is a sandbox instance whose URL is https://acsXXXus.campaign-sandbox.adobe.com/ and the URL I'm trying to send the POST is https://mc.adob...

I was going through the Adobe Documentation for A/B testing on AEM Forms it surprisingly caught me that they have discontinued the feature.https://experienceleague.adobe.com/docs/experience-manager-65/forms/integrate-aem-forms-with-experience-cloud-solutions/ab-testing-adaptive-forms.html?lang=en  A...

I've an update here:In our particular scenario, we have noticed that when the form HTML is added directly from the target, no issues arise. However, when it is added via the Experience fragment, console errors are observed and is hindering form submission. Several console errors are generated, indic...

I've two XFs in AEM which has been exported to Adobe Target and is being used in the AB activities. The XFs are basically formstack(third party) forms where the content is form HTML(not embed code). The form is getting loaded correctly in the pages. When previewing the QA URL couple of uncaught erro...

I've two XFs in AEM which has been exported to Adobe Target and is being used in the AB activities. The XFs are basically formstack(third party) forms where the content is form HTML(not embed code). The form is getting loaded correctly in the pages. When previewing the QA URL couple of uncaught erro...

@Sachin_Arora_ I'm on AEM 6.5.16 and the cq:name is getting stored at jcr:content/cq:name

Recently I have observed that there is a number of assets in my AEM DAM which doesn't have a cq:name while the majority of the assets does have.My understanding is that the cq:name value is generated by AEM by default, and I would like to understand why it doesn't get added for certain assets.