Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Ion Interactive
Score 8.0 out of 10
Enterprise companies (1,001+ employees)
Ion is an enterprise-grade content experience platform that empowers modern marketers and designers to create no-code interactive content experiences integrated with their CRM or marketing automation tools.
N/A
Pricing
Drupal
Ion Interactive
Editions & Modules
No answers on this topic
Managed Services + SaaS
Custom
per year
Offerings
Pricing Offerings
Drupal
Ion Interactive
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
$5,500 per customer
Additional Details
—
ion’s Build Anything SaaS platform provides organizations with an entirely new and agile interactive content marketing capability. It enables non-technical marketers and designers to create, test and measure an unlimited number of all types of interactive content marketing experiences. It includes unlimited seats, experiences, tests, customization, phone and email support, analytics and more.
More Pricing Information
Community Pulse
Drupal
Ion Interactive
Considered Both Products
Drupal
No answer on this topic
Ion Interactive
Verified User
Technician
Chose Ion Interactive
ion is a comparable product to WordPress in some aspects of user experience and versatility. We've integrated elements of ion with Salesforce, which has given certain groups more flexibility in their day-to-day tasks. There are pros and cons when comparing Ion to Drupal, and …
Both ion and Drupal are essential in our business but they're used in completely different methods. Our Drupal pages are live and searchable on Google. Our landing pages are not indexed because we [like] to pinpoint traffic sources to them. We can turn a traffic source on and …
Honestly these are different products. Other web platforms, are built to create a website. However this is meant for rapid content creation of landing pages. A user lands on the page, does a desired action (fills out a form, clicks a button, etc) and then they are done. Also …
The ion platform is easy to use and quick to create websites. Using ion allows us to not need developer resources to create the websites. It is cost effective. The decision to use ion was made prior to my arrival at the company.
Neither of the above are landing page tools, but they are all resources that we are using currently. We have dramatically increased the number of our email campaigns and it became difficult with our billing setup to continue using Bronto and ion for email/landing page …
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
If you want to choose a quick start template and fill in the fields with your content, Ion will be fantastic for you. We've done this with whitepapers and quizzes and it's been great and extremely easy to use. If you have an exact idea of what you want, and a background in web development, you may get frustrated. Ion has some quirks that make it tricky to fully customize - everyone once in a while I really just want to go into the HTML and make some changes, but can't. If you are looking to reuse a piece of content for specific targeting (industry or account-specific), Ion is great. The dynamic substitutions are great and very helpful.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
Ion University, while stacked with a wealth of information, is difficult to navigate from a troubleshooting perspective. The tutorial videos are all very helpful, but they are also very long. Sometimes I would want to search for how to address a particular issue I was struggling with and it would be a two-minute segment buried in a 45-minute video.
Again, getting back the self-guidance side of things. I think a lot of the tutorials are set up in a way that makes sense to Ion, but not as much to the end user.
I think the controls admins use when creating new users could be a bit more straightforward.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
We use it for every landing page and we plan on only doing more dynamic content creation. We dont see that option coming in-house any time ever in the future. ION has a very robust platform for us to work with that really allows us to do more for our customers in regards to having the one-to-one conversation.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Usability is straightforward, with extensive documentation and tutorials provided to ensure landing pages are built to specifications and can be optimized for performance. Built-in platform funnels give insight into customer dropoff, success/failures, and conversions (at a glance). Setting up a landing page can be done quickly and easily, with numerous integrations (CRMs like SalesForce, for instance) supported
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
The ION support team is amazing. There has not been a single issue they they could not solve for me. If there is a feature or request that they do not have, they have even, on occasion, created custom scripts for our team. *Update 6/5/17 - ION has continued to delight on multiple occasions. I appreciate their attention to detail and ability to solve whatever issue I have. After 3+ years of use and support, ION still has my full endorsement.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
They offer a great amount of online training, videos, articles, etc. There is usually an answer available if you run into an issue. I would recommend taking advantage of the online training they offer. I wish I would have done it sooner.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
There were a lot of things we learned about the tool once we really got in and got our hands dirty. Being hands-on was essential for our team to be able to utilize ION in the most effective manner.
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
I was not the decision maker to choose this over Uberflip, but the UI is much more appealing to me. It's incredibly easy to use, clean, and from a backend standpoint, it requires little to no tech savvy'ness. Our team has really enjoyed using it and has required no training what-so-ever.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Separate client portfolios enable scalability, however, some elements are still grouped for all accounts so it's difficult to scale for an ad agency with multiple clients. Would prefer totally separate sections of the platform for all clients with each element housed separately.
Though we have not had the service long enough to see any measurable outcomes, we've been able to create interactive web content faster than ever before
The speed with which we can build interactive pages and re-use assets has been critical as projects we've done with Ion have made their way around and more and more internal clients have said "me too" for their own projects
It is very pricey at $28K for the base annual subscription (dropping to $24k after the first year), so depending on your budgetary situation, that may make no sense for your team--but we had contract money set aside for a company to build us a microsite for around the amount, so we just used it for Ion instead and will now be building the microsite ourselves using it
