Pardot vs K6

I give Pardot a review of four out of five stars, and for more reviews, see below. Before my organization started using Pardot, we were on eTapestry's built-in mass email communication software system. It wasn't working for us because it was a technology of the past. It was very clunky. We had a very limited amount of mailable prospects we had, and it was very manual, and the resolution for videos, images wasn't the best. The first biggest selling point for Pardot was its native integration with Salesforce. So now whenever we have a contact in Salesforce, it's automatically synced to Pardot, which makes it a lot easier for my team to use and navigate. And the second reason why we chose Pardot is because of its really intelligent tools, such as Engagement Studio where we can automate a lot of our tasks and be a much more efficient organization. Pardot definitely is not the easiest tool to use. We have to hire consultants to help us build it and integrate it with Salesforce. It took us about a full year before we became confident with using Pardot, and every day my organization is still learning more things that the tool can do for us. If you're a small team and want to be super efficient, Pardot is a great tool for you because it takes a lot of the manual work out, especially with drip campaigns and a lot of its automation tools.

- Sabal A.

I would give Pardot a three out of five stars. And for more reviews, you can click below. Prior to using Pardot, we were using HubSpot Marketing Hub. It was a great marketing tool. I have really no quarrels with that. But the integration with Salesforce Sales Cloud was a little lackluster and hard to control, especially when it came to custom field syncing. We chose Pardot primarily based on the integration with Salesforce. It had a lot of overlapping capabilities with other marketing automation platforms, but we were most excited to leverage the connection between our Sales Cloud contacts and our Pardot prospects. Pardot was a little difficult up front, but it didn't last very long. So the implementation for properly set up work would probably be about two months. We used kind of an implementation partner, which I would recommend, through Salesforce actually, their jumpstart program. And that helped because we had a dedicated and knowledgeable person that would give us feedback and check-ins once a week. So that made it a little bit easier. But I would say the first two months are a little bit of a challenge and then the org works well. I think if you're considering using Pardot and going to use Pardot, of course there needs to be some integration with another Salesforce channel. That's really where you get the best leverage and Pardot separates itself from other marketing automation softwares like HubSpot or Mailchimp or something like that. I think it's also important to have a dedicated personnel to manage Pardot. It's commonly the same person that manages a Salesforce instance. So you can double up like that, but it's not something that's going to self-manage you really need a dedicated administrator for when configuration requests come up.

- Kelly Michael S.

Pardot has made it easy to understand how our marketing is working, know who is a hot lead versus a disengaged one, and to create content that is easy to share and delivers good ROI. It’s built in many safeguards to keep you from getting in trouble with spam rules and avoid sending emails multiple times.

- Kate B.

"Developer-Friendly Performance Testing Tool & Infrastructure" What do you like best about k6? -Excellent documentation and supportive blogs (and video content like the Office Hours series) content simplifies getting started with k6 -Developer-friendly -- Easy to install and get going in the CLI. Makes performance testing more accessible to not just a few, but all of those on an engineering team. This is so important as performance testing is no longer just an expectation of a single niche quality team because of limitations of licensing or knowledge of an antiquated tool. -k6 cloud -- So far, ensuring the ability to scale our tests beyond the resource of our machines has been reassuring. The analyses and comparison features between test executions is helpful so far. Looking forward to the continued work against this infrastructure platform. Review collected by and hosted on G2.com. What do you dislike about k6? -The user experience of using k6 with npm modules is not consistent with what you expect from typical development -xk6 extensions conceptually are great as a community is helping to build out a need. Just be cautious of utilization as they may not be supported long-term, though these extensions are featured in k6 documentation. Review collected by and hosted on G2.com. What problems is k6 solving and how is that benefiting you? k6 has made performance testing an accessible practice for engineering teams. It's a rather low barrier to entry (getting started with k6) , yet you can get as advanced as you with, customizing your scripts as you need to get the insights required. Because of this tool, I'm seeing engineering teams starting to take on the responsibility of knowing and testing the limitations of their APIs and tiers.

- Lindsay H.

"K6-Game changer for API Load and Performance test" What do you like best about k6? It is developer friendly and easy to write load tests and has excellent documentation. Most importantly it is a straightforward K6 report that can tell where the performance issues are. We did a thorough analysis where we compared several tools/frameworks and we can tell with full confidence that K6 is much superior compared to other tools. These are some of the benefits: It is easy to install and start writing the first L&P test, code review It is great community support and excellent documentation Excellent Report and Integrates with NewRelic, CloudWatch if we decide to retire later it is easy to do because we can still run locally without being locked to one tool. I would call the K6 a modern L&P framework that can beneficial for any company. Review collected by and hosted on G2.com. What do you dislike about k6? I wish it had better support for HTTP protocols. It is awesome with API test but not so great with UI load test. Review collected by and hosted on G2.com. What problems is k6 solving and how is that benefiting you? Ensuring that API we develop performance well at Production. It is not a guessing game anymore. It is a data-driven decision.

- Talgatbek K.

What do you like best about k6? It's ease of use, readability and its fantastic set of constantly evolving features, paired with a vibrant community - which together with its good performance makes, to me, the best option for performance testing. And its extensibility as well... Tests are code, as they should. And readable code! Review collected by and hosted on G2.com. What do you dislike about k6? There is an extensibility /plug-in system but some integrations are still not covered… To complain about something, its only issue is that apart from the excellent readability of the tests, they still need to be written, so you need to know what you are doing- thank god- I still have a job. But give it time… (summary: tests needs to be written, haha) And the fact that you have to write in JavaScript - it would be fantastic to write in your own language such as C# as in my case :) Review collected by and hosted on G2.com. Recommendations to others considering k6: Check other options, make your own decisions. My criteria might not match yours. My decision points were the performance vs. features, mainly its code readability, how easy it is to define a real test, its open model, and extensibility. Review collected by and hosted on G2.com. What problems is k6 solving and how is that benefiting you? excellent, readable performance tests that evolve with the application, as code. One test source code fits all, so its simplicity is key.

- Jose Luis L.