Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
N/A
Optimizely Customized Commerce
Score 8.8 out of 10
N/A
Optimizely Customized Commerce is a headless PaaS commerce solution built to scale commerce results for enterprise brands.
So one of the primary focuses in the company has been SEO, and it does not seem well suited to SEO. For instance, how we set up the alt image tags. It's pretty tricky and there are multiple steps to do that. So I would like to see an Adobe Experience Manager that is more focused on out-of-the-box solutions for SEO, schema coding, alt image tags, and other sorts of SEO functionality to have that more built into the vanilla version of the product. Well suited? It's very good at scalability. And because we're managing such a large number of hotel properties, it works well for an enterprise.
Our experience may be unique because we opted for an Epi core team to implement our website/console set-up and connection to our PIM and ERP. The experience may have been different with a 3rd party or it may not have. That said, we have been live with our primary website for almost 2 years and I still do not consider it was ever "done". We have been going back and forth on functionality issues and bugs since launch. I have low confidence that changes made the previous day will 100% be online the next - so my team rechecks the work they did the previous day to ensure everything is online. The addition of a second channel and enhancement requests have compounded the issues. I feel this product would work fine with singular or less complex market SKU offerings.
It is able to support our incoming volume. We're one of the largest in what we do in the country, and we've not had any issues in terms of how it performs, or how it scales our customers coming in. It's a fairly stable platform. It is also a very intuitive platform in us being able to give our business users the ability to come make changes and request additions without going through a huge lift in getting those requests implemented. It has also been a very developer-friendly platform for my team to be able to develop, adapt, and build. We're also expanding on being able to use AEM both as a pure content management solution and also as a headless content solution. So that way we are trying to build a unified content platform that would allow us to create, publish, and manage content across channels from one place. So it's fairly intuitive that way. It's fairly scalable. Obviously, the modern tooling helps, but overall I think it's been a good experience.
Episerver has a robust discount engine. This engine, combined with "visitor groups" allow our marketing department to categorize customers and offer a variety of discounts to targeted customers at specific times.
Episerver has a full-featured, storefront experience that can handle everything you might want for an e-commerce website.
Episerver offers A/B testing that can be helpful for trying out new content ideas and tracking the results.
I think some of the key things that can be done better is today we have more point solutions for different things like personalization. We have Adobe Target and for email marketing, we have Adobe Campaign Marketer and all that kind of stuff. But truly I have worked both as an implementation partner for Adobe as well as now I'm a client of Adobe. Being in both those shoes, I can say that we can do a lot better in terms of beefing up the capabilities of AEM, bringing personalization and search and content search experience closer together. It would definitely put Adobe Experience Manager in a different league if we can bring all those personalization capabilities together. I think initially the content management systems, the market was mostly meant to serve static sites. It never matured into that full-scale content personalization being married together. I think that's one area where if those integrations rather than being point solutions, if those capabilities can be made more native to AEM, I think it would definitely be a big sell for a lot of customers.
Support. Episerver used to have direct support and access to the tech team to discuss and resolve issues. The new support portal is not enough for developer needs.
Quality Assurance. We find issues in the Episerver code that should have been resolved in QA before release.
Sales. Episervers sells the framework as a solution while showing Alloy. While it helps Episerver sell more, it puts the implementation partner into trouble as the client thinks they bought the solution. Episerver does not provide a solution. It provides a framework that you can build a solution on.
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
Really want to be able to spend more time and resources on rolling out new things with Episerver but at the moment we seem to be fixing alot of issues and pain points with the way our system was setup.
From our learning curve until we got better. I'd say as we're moving forward and we're making more customizations and we're getting used to it, I'd say it's about a seven or an eight. But as more innovations and more information comes out from Adobe as they make more changes and they make improvements, I'd say they're getting probably about an eight right now.
The administrative interface is largely intuitive and relatively easy to use. The complexity of business needs and ability to customize can affect this (i.e. you have to set up and develop with the user in mind), but the basic structure is largely solid. There are some areas of redundancy (such as Commerce Manager overlapping with other administrative areas) that can sometimes cause confusion or offer some functions in one place, whereas other related functions are managed on a completely different page.
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
We had an incredible team at Episerver Supporting us with the go live, reviewing our integration, and pushing our integration partner to deliver a quality product
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
Fully understand what is OOTB feature of the platform before proceeding to develop. Then implement a customization of key features once you can prove they are working as OOTB to make them more user friendly and productive for the business. Eg pre order and e gift card
At Canadian Tire Financial, in the time I've been there, we've always used AEM, but in past places I've used WordPress, I've used Squarespace. Things that are more general user-friendly where you're like building your own blog or you're creating a small business website where it's basically just text, you're not intaking information or something like that. I think the customization options in AEM are huge. My experiences with WordPress were pretty straightforward. Again, it was like, I don't know, like college newspaper website or something like that where you're just like putting content up for people to look at. You're not necessarily taking in any other information. Maybe you might allow people to log in or something and save articles or something pretty straightforward, but then even then I remember that stuff taking me forever to do, to figure out and scroll through tons and tons and tons of documentation. It's just not fun. No one enjoys doing that and then even then you might not have the answer available to you. And that's so frustrating. Hey, it's super user-friendly, figuring out the content editor is pretty straightforward. You're not clicking around and being, "what the heck am I looking at?" Or you're not looking at a bazillion menus to be like, "maybe the thing I want is in here." I can't stand that. I want to be able to look at a page, see what I'm going to be getting in production, and then publish it. I don't want to look around in menus to figure out how to add something to a page.
Optimizely Commerce Cloud offers a very wide range of features for admin users. There is less a need for an IT specialist or programmer to be involved when changes need to be made.
Instead of being directly involved in the tool purchase, I am involved in analysis or what we can use to maximize the tool. Small organizations may find it expensive. However, if the team or organization focuses more on your ROI or the features you will get, then it will definitely be worth it. Pricing is based on a number of factors, including team size or the use of the tool. The user can select the pricing option that best fits their needs based on the number of form submissions they make or the number of pages they wish to publish on their global/multisite sites.
The professional services team within adobe is one of the best in terms of technical and solutioning knowledge. However, considering the billing charges of adobe professional services team, it is always recommended to involve them during platform initial setup or when a complex solution is to be built with platform customizations.
This actually has been great for our websites. In the time that I've been with the company, we've seen at least the profitability of our websites because we are measuring that through analytics. We've seen it double since using it. We were using it when I first started with the company, but we've gotten better at how we're using it and really optimizing the use as well as the design. I think that that's made a huge difference. We've seen a huge jump in the performance of our websites with maintaining users and the e-commerce side of it.
