Intellimize vs. Magnolia

Intellimize has done a great job of targeting our highest trafficked pages. For a demand generation organization it helps provide a lot value for places like the homepage or various high value funnels. Where Intellimize falls short is where we have a specific technology stack that often causes issues for us being able to run tests at scale because some experiments break or fail to run. Please do yourself a favor and evaluate this tool with your development team before purchasing. Single Page Applications do have re-rendering issues given some experiments which lead to run-time issues that need to be heavily QA'd before launch. For teams that are ecommerce or have a typical technology stack (e.g. wordpress and static pages), then Intellimize will probably work without any issues.

Incentivized

If you need a business CMS that brings along a good amount of features and also give you the chance to develop features on your own, Magnolia would be a good choice. Even if you have not the fitting infrastructure around, Magnolia provides you different ways like SAAS oder PAAS. If you have to review your code our have any problems the team behind will helps in a short time. Without using the connectors it is not so easy to connect special functionalities like Marketing tools or optimization tools. The DAM is very slow if you have an huge amount of documents and pictures to store for your website - you have to add an external DAM.

Incentivized

• CSM and Engineering resources are available with Intellimize and allows us to spend more time thinking about new ideas to implement.
• AI/Machine Learning allows winning personalizations to continually run or switch between variants for users that may convert better based on firmographic data
• The CSM is a wonderful collaborator and acts as a liaison between Intellimize's engineering team. With their help, I am able to better refine my own testing roadmap.

Incentivized

• Use of YAML to define content models with code.
• Versatility of defining actions for custom handlers.
• Reloading classes when code is modified in a local dev environment is nice. While it doesn't seem to work when changes extend beyond the method body (i.e., adding methods), it remediates the pain of long startup times.

Incentivized

• No WYSIWIG Editor
• Limited to only 5 tests a week
• QA of larger tests that require heavier engineering effort can often run longer than a week and can block the already limited number of tests you can run

Incentivized

• As a developer the learning curve is long, you can start developing relatively quickly but getting to know the platform in depth takes time.
• Having a history of modifications not only at the page level but also at the Content Apps level would be very useful.

Incentivized

Magnolia is an innovative CMS, for example it is possible to use the ipad to manage the contents. Magnolia’s team works hard to improve the product; the community is small but active and the support for the enterprise version is good. Magnolia’s team asks the users what they think and what they need, and the new functionalities planned for Magnolia 5.3 are very exciting for example the content personalization.

There are a ton of small things that could make this CMS great Off the top of my head... 1) Better navigation between a component and its corresponding node in the jcr ( devs often have to flip between a page and a spot in the jcr even though there could be a button to take you from a page/component in the pages app to its location in the JCR) 2) Why does a content editor need to open the page to edit the page properties? They could just as easily edit the dialog from the tree view if they have many pages to touch, and it would save them time by not having to render the page.

Incentivized

It's a lean and performant platform. You don't need to put reverse proxy servers in front of it to speed it up (although that does make it go even quicker) as there are various layers of caching built in to the application. While it's a little cryptic, the internal caching system is actually quite configurable and can be tuned to the right sort of content.

Often what tends to surprise many an IT manager is that you can run it on relatively modest hardware. We've often been met with "are you sure ?" but the reality is that it doesn't need a whole lot of horsepower.

Incentivized

You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases

Intellimize is a league above products like VWO and Google Optimize. Simply having the support from an external engineering team gives your web team the freedom and bandwidth to do more. The level of support for Google Optimize is entirely limited, especially if you're using the free version of that product, and I am skeptical of paying Google for the paid version of it since the largest value of the paid version of Optimize, is to simply run more tests. VWO has amazing heatmap and reporting, but severely lacks any Machine Learning or firmographic data. While their support is exceptional, it's not the same as having a dedicated CSM to help plan a roadmap. It's also helpful to note that VWO, Google Optimize, and Intellimize have issues with single page applications. Static websites are likely to run entirely fine without issue.

Incentivized

Magnolia DXP offers similar or more capability compared to the other platform, while much easier to implement. For example, Adobe Experience Manager tend to be more monolithic in nature, heavier footprint compared to Magnolia. Hence when implementing a DXP, it is much faster to build using Magnolia, at a much lower TCO. The other platform like Kontent.ai and Strapi are pure headless platform and offer lesser features. What really make Magnolia different is the APAC team, who are all out to support their client in the implementation, ensuring their client maximize their platform and the project implementation is successful. This is some thing that is not experienced when using other platform(s)

• Increased revenue
• Helped us build out many tests that had the impact of many years of learnings
• Contributed to more MQLs influenced

Incentivized

• We have placed web content management in the hands of the organisation than retained it within the technology team.
• We were able to quickly move to MVP and release and we are now focussed on moving the platform forward at some pace whilst not being burdened with BAU work inside the technology team as so much as self-service to trained organisational users
• The use of the SAAS/PASS has inbuilt business resiliency as specialist work and aspects such as underlying security is done by Magnolia and we are able to focus internal effort on building out the platform.