There is room for improvement in Adobe Web Experience Management, particularly concerning single-page applications. It has certain aspects that need improvement regarding content exposure. While content as a service has been introduced, there are some difficulties when implementing it, as customizations are required, which are not out-of-the-box features or APIs provided. Additionally, the deployment strategy employed for Adobe Cloud Services has room for improvement, particularly in the time taken for deployment and debugging. Developers find it challenging to debug issues in the environment, as previous on-premises versions provided more visibility. This aspect definitely needs improvement. Normally, for the cloud, deployment takes around thirty to forty-five minutes, but I have seen situations where it takes more than one hour, sometimes even one and a half hours. For the production environment, at least half an hour may be acceptable, but one and a half hours is not acceptable. This contrasts with the on-premises version, which has a different architecture for deployment. This should be improved, and they need to look into it because one and a half hours for deployment is too much.
Regarding AI-driven analytics in Adobe Web Experience Management, AI analytics is not yet used; however, since recently there was a push at a global market level to move to AI part, Adobe also introduced certain things, but currently, I have not used it. From an integration point of view, as I said, for Adobe suite products, Adobe provided it. However, mainly for the cloud one, Adobe Web Experience Management on-premises has certain restrictions from a compliance point of view. Adobe has hosted it in their environment, and now I think most clients are moving to AMS as well. However, when it comes to third-party integrations, there are certain restrictions, especially in finance organizations. For the retail sector, support provided by Adobe is pretty good but clients are still restricting themselves from moving to the cloud due to compliance issues, which I believe is not because of Adobe Web Experience Management but rather because of the cloud structure itself. Improvement-wise, I think Adobe Web Experience Management site-wise is fine, but mainly for the cloud one, it is growing. However, I have observed that certain forms need improvement, and if Adobe has any offering for clients needing private cloud solutions, that would be great. I have seen clients restricting themselves from moving to the cloud, and it depends on Adobe's awareness of this issue through surveys they may have conducted. I don't think I would suggest any additional features for Adobe Web Experience Management because case by case, the requirements may vary. Adobe has tried to provide the vanilla features that are required.
This product is unable to handle very large video files and related elements. Adobe should focus on a media asset management solution, the solution currently lacks that.
Learn what your peers think about Adobe Web Experience Management. Get advice and tips from experienced pros sharing their opinions. Updated: June 2026.
Adobe Web Experience Management is a comprehensive platform designed for managing and delivering engaging web experiences. It provides tools for content management and digital asset management, making it ideal for businesses looking to enhance their digital presence. Adobe Web Experience Management empowers organizations to streamline processes with its intuitive interface. It offers robust content management features that enable users to create, manage, and optimize web content efficiently....
There is room for improvement in Adobe Web Experience Management, particularly concerning single-page applications. It has certain aspects that need improvement regarding content exposure. While content as a service has been introduced, there are some difficulties when implementing it, as customizations are required, which are not out-of-the-box features or APIs provided. Additionally, the deployment strategy employed for Adobe Cloud Services has room for improvement, particularly in the time taken for deployment and debugging. Developers find it challenging to debug issues in the environment, as previous on-premises versions provided more visibility. This aspect definitely needs improvement. Normally, for the cloud, deployment takes around thirty to forty-five minutes, but I have seen situations where it takes more than one hour, sometimes even one and a half hours. For the production environment, at least half an hour may be acceptable, but one and a half hours is not acceptable. This contrasts with the on-premises version, which has a different architecture for deployment. This should be improved, and they need to look into it because one and a half hours for deployment is too much.
Regarding AI-driven analytics in Adobe Web Experience Management, AI analytics is not yet used; however, since recently there was a push at a global market level to move to AI part, Adobe also introduced certain things, but currently, I have not used it. From an integration point of view, as I said, for Adobe suite products, Adobe provided it. However, mainly for the cloud one, Adobe Web Experience Management on-premises has certain restrictions from a compliance point of view. Adobe has hosted it in their environment, and now I think most clients are moving to AMS as well. However, when it comes to third-party integrations, there are certain restrictions, especially in finance organizations. For the retail sector, support provided by Adobe is pretty good but clients are still restricting themselves from moving to the cloud due to compliance issues, which I believe is not because of Adobe Web Experience Management but rather because of the cloud structure itself. Improvement-wise, I think Adobe Web Experience Management site-wise is fine, but mainly for the cloud one, it is growing. However, I have observed that certain forms need improvement, and if Adobe has any offering for clients needing private cloud solutions, that would be great. I have seen clients restricting themselves from moving to the cloud, and it depends on Adobe's awareness of this issue through surveys they may have conducted. I don't think I would suggest any additional features for Adobe Web Experience Management because case by case, the requirements may vary. Adobe has tried to provide the vanilla features that are required.
This product is unable to handle very large video files and related elements. Adobe should focus on a media asset management solution, the solution currently lacks that.