Acquia Digital Experience Platform vs Pardot

• 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

• Pardot enables you to set up different environments via the Pardot Business Unit feature, this is helpful for when decentralization is still needed, but you want all business units working with the same tool.
• Pardot enables you to quickly and easily create automation rules that can clean the database retro-actively.
• Pardot has the ability to have multiple lead scoring models run at the same time.

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

• Email templates and drafts are really confusing. I trained various people to create their own templates, but they consistently got confused between publishing a template or just saving a draft, and where they needed to go back to find it.
• Their help process is broken, at least for our particular use case. Because we have an enterprise license for Salesforce (even though we had a separate license for Pardot) whenever I needed help with something, I'd get stuck down a rabbit hole and couldn't submit a ticket.

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

• We spent several months and lots of money working with a outside integration partner, only to find out the journey we were trying to automate couldn't really be done and was better suited for Marketing Cloud. We ended up cancelling and switching to Marketing Cloud.

Read full review