Hi @_Manoj_Kumar_    Tried with selecting and unselecting the "Prefill form fields with profile information", but in both the condition, landing page is still not accessible over the web. I think, it's a current limitation of AJO's to expose this landing page over the web instead of only using as a ...

Hello AJO community members,   I have a use case where I created a landing page using AJO and published it. I'm able to preview this page but want to access this page over the web, simply putting the link of the landing page on a CTA on a AEM page to be accessible by the end user. The problem we are...

Hi @g12    Try with re installing the wcm core component package.

Hi @Kam-nyc    Few things to check here:-   1. Have you checked on the publisher whether this asset exists? 2. If asset exist, ideally it should be accessible. It might be the dispatcher is blocking it. You would need to add the dispatcher filter rule to allow /api/assets/*.

Hi @pallavi223    What's your scenario to use Adobe Forms as headless?    I don't think that there is an use case available to use Adobe forms as headless. You can always embed the Adobe form in any web page hosted outside AEM. The embedded adaptive form is fully functional and users can fill and su...

You would have to go to AEP profiles and search for your profile based on the namespace. For example, if the user is logged to the website and the email Id is getting ingested in the profile attributes, then in that case you can search based on the email ID namespace. In case, it's an anonymous user...

Hi @ben_mrm    I don't think the AEP segmentation details are available on the cloud debugger extension. You would have to go to AEP and check whether your profile is qualified for that segment or not which you are exporting as an audience in Adobe Target.   Hope this help.

Hi @deakin96    As per my understanding, for your use case Adobe Target stand alone would not be sufficient to generate audience based on cart content. Adobe Target provide a way to create the audience but mostly it's very basic and it's based on geolocation, OS, Page etc. You can try generating som...

Hi @ravir73578276    Unfortunately, I don't think there is any OOB mechanism available to index the graphQL queries. You can persist the queries and cache it at the dispatcher and CDN layer which will ultimately improve the performance of the requesting client application.   Kindly refer to the foll...

Hi @S__k__Agarwal    To hide and remove the unwanted columns, you can use the approach suggested by @Himanshu_Jain .   To add a custom column "Country", you would need to overlay the following path /libs/wcm/core/content/common/availablecolumns and add the node for the Country. Along with that you w...