Campaigner vs. Magnolia

If you are a small business who just wants a passable service, this tool will suit you. It does have WYSIWYG tools to create emails and test sends are easy. It does a decent job of reporting too. If, however you are a larger company, I suggest you look elsewhere. There are plenty of other solutions that do this better (I liked My Emma from a previous position where we were doing small to medium sends) for less money and will actually provide decent customer service if you contact them

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

• Email Customization
• Contact Management
• Form
• Workflow Processes

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

• Campaigner is just too bare-bones. When we first started using Campaigner close to a decade ago it was perfect for what it was. But nowadays Campaigner is missing several features that their competitors offer like exit intent and cart abandonment emails.
• Campaigner has an astonishingly bad unsubscribe option. We have had many customers complain to us over the years that when they try to unsubscribe through the emails Campaigner sends, their unsubscribe does not go through.
• Hard to change account settings such as changing our subscription plan. We had to call and were told to wait 24 hours just to make a small change to our account.

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

I can't see us not renewing unless we find something better. This is highly unlikely because there was a thorough research done for use to chose the best marketing client and it always came back to campaigner.

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.

Great features but awful tech support experiences over five years of use. Some releases broke our workflows and Campaigner could never explain why. Our initial plan provided a designed client support contact. This individual changed frequently without notice and at one point they decided our plan no longer included a designated contact. Of course this was never communicated to us until we tried to reach out to the person. If you are tech savy this system might be for you but you'll be on your own.

Incentivized

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

Over five years I rarely had an interaction I was satisfied with. General tech support staff did not seem to be trained on anything but the basics of the system. They would open tech support tickets, give me a case # and then we would hear nothing. We still have open tickets from years ago. Software releases were never communicated. New features never announced. For an email marketing company they did not use email to communicate to me well at all. Every email I received was trying to sell me what I had already bought

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

Aweber - used this pre 2015. It did not provide a single opt in option. it allowed us to download our contact list into Excel but we could not re-upload any changes we made to cleanup or add to data. Campaign monitor - we did not like the user interface as well and as I recall it did not have a similar workflow feature.

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)

• Campaigner has cost us valuable time in the times that customers had complained to us that their unsubscribe emails did not go through and we had to manually go into campaigners website and manually remove those emails.
• Campaigner has offered an easy way for us to send marketing emails for quick and effective usage.

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.