@mattmuller Here is a documentation link for integrating AEM sites with Adobe Target which can get you started.https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/integration/target Here is a PDF document I found on Sensei in Targethttps://business.adobe.com/...

@ElmoPro Do you have any components associated with these pages? Do you see these issues happening on we.retail as well? 

@hrya Merge policies are rules used by Profile to determine how data will be prioritized and combined into a unified view under certain conditions. When data is ingested from various sources, it often contains information about the same customer but with potential conflicts or inconsistencies. Merge...

@ElmoPro It should be something to do with permissions.Is this happening on a particular page for a particular folder? Is this happening just for you or your entire team?

@hrya During segment creation, you have the option to explicitly select a merge policy to be used for that segment. This overrides the default merge policy and allows you to choose the appropriate merge policy based on your segmentation requirements.If no specific merge policy is selected during seg...

@Vignesh_K_S  I second what @EstebanBustamante responded. There is no out-of-the-box nested Multifield for Content Fragments, you would have to build your own. There is an earlier question answered about "Nested Multifield in Content Fragment". Check out the below link about it.https://experiencelea...

@ssin93 It might be what @aanchal-sikka suggested. It could be as simple as validation errors. Check if the data you are entering in the content fragment fields is valid compared to the CF model? Or it could be a permission issue. Is this happening for any CF on any path? Check your permissions once...

@Sandeep_k_Singh If you already tried @Keerthi0555 solution, try the below to debug the issue: 1. Check that the component policy is correctly configured in the _cq_design_dialog folder of your component. The _cq_design_dialog/.content.xml file should include the <styletab> entry to enable the Style...

Hi Community, Can you help me with different use cases where you are using AEM projects?https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/authoring/projects/projects I would like to know and understand different use cases from different orgs.

@Anilkumar9 The error indicates that the Java compiler is unable to find or resolve the "HelloWorldModel" class referenced in the component's Java code.Try checking your bundles are installed or not. Sometimes if the dependencies are not installed or active this error might happen.If the bundles are...