Wouldn’t it be odd/off-putting if you hired a personal trainer, showed up at the gym, and were immediately thrusted into a workout regime that didn’t support your goal of training for a half-marathon, losing 20 lbs, or simply strengthening your knee after recovering from an injury? It certainly would be. Then why are we as Salesforce consultants doing this with complex, sophisticated technology that spans multiple business functions and supports a large majority of employees? 

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.