Acquia Digital Experience Platform vs Hull CDP, from MessageBird

• The Acquia Cloud Hosting (enterprise) provides a three-server solution. You have a Development, Staging (or UAT), and Production servers with a clear path of deployment straight up the chain. You may use Acquia's own Cloud Hooks, or their web admin UI interface to deploy to any or all of the servers.
• Git is one of the foundation services built-in to the management of the website codebase. Allowing a developer, or well-trained end user (university employee) to easily deploy a tag or branch to any one of the servers, makes it very easy for us to offload the server / account management to the school, while we focus on improving their site.
• Not only does Acquia Cloud provide a multi-datacenter failover disaster recovery solution, but they also maintain a multi-region failover as well, which allows for a fully redundant enviroment to be maintained in two geographic regions. No fear of losing any database changes or form submissions from students.
• Lastly, the onboarding process is constantly being improved, and as I have been a third-party vendor involved in many of our hosting negotiations, I have seen it firsthand. Each enterprise client is assigned a small team of engineers, technical leads, and a pseudo-project-manager to explain the process in layman's terms to the client (university / college for my example), but they also perform a number of code reviews and best-practice analysis of a site prior to launch.

Read full review

• Slack integration - we revolve around slack as our central comm hub and having our customer information surfaceable is just gold.
• Making back-end data easy to read and digest - there is a lot of data that gets generated by our customers and it's impossible to sift through without Hull consolidating that information for us.
• Customer support - we have only had a couple issues in the many months using Hull and it's always been a quick resolution. They use Slack to support BTW which I love.

Read full review

• Responses from tickets aren't always from the same person, and can vary in effectiveness of solving your problem
• While documentation is robust, it can be difficult to find exactly what you need
• Provided forums are not monitored frequently, and are not as useful as they could be

Read full review

• Needs a deduplication engine
• Needs to be able to perform bulk and automated data cleansing (unified data is messy)
• Needs to integrate with more tools
• Needs to be able to be tailored to different use cases, such as a retail/ecommerce use case, with RFM metrics

Read full review

• Our website isn't a revenue generator, so we don't have specific ROI calculations.
• The new website is helping us move off of a legacy on-prem server environment. The reduction of cost in maintaining those will be beneficial.
• We have had to invest in some training for our developers to learn Drupal.

Read full review

• Positive: No longer asking engineering for customer activity data
• Positive: Allowing additional data integrations for where our customer activity data can be seen

Read full review