Salesforce and Pardot have a symbiotic relationship that can’t be beat when it comes to B2B marketing automation. At Kicksaw, I often find myself talking to a potential client about their sales operations and find that the conversation will naturally venture into the marketing operations territory. After all, the Marketing department's goal is to send the Sales team as many highly qualified leads as possible. And while Salesforce has put together documentation on how to implement Pardot with Salesforce, Kicksaw has a highly skilled Marketing Ops team that has executed more than a hundred implementations, and along the way, we've picked up some valuable tips and made note of some important “gotchas” that are often overlooked during the implementation process. 

As a Solutions Architect here at Kicksaw, whenever I am handed a new (to me) Salesforce org to work on, one of the first things I check is the health of the business processes made with Process Builder, as they seem to be a common spot for a lot of bugs and errors. In this article, I’m going to share some tips and tricks with you to ensure that your own Process Builder business processes don’t turn into a nightmare of timeouts, bugs, and unexpected data. 

One of the biggest challenges when testing is covering code that interacts with an external service. This is where the domain of unit tests ends and that of integration tests begins, but the latter is multitudes more complicated than the former. Once it’s time to test anything that makes a network call, the bar is raised.