As one of the chief “Pardot API Geeks” here at Sercante (no, it’s not a real title, but I think it really should be) I’m really excited about two big changes to the Pardot API – one of which was confirmed on this week’s Pardot Product Roadmap webinar.
I’ll admit it. As a marketing professional, I was a bit nervous the first time that I heard the term “Marketing Automation”. My first thought was that somebody was trying to automate my role and that I would soon be looking for a job.
Pardot Grading is a great way to identify prospects who meet your ideal buyer persona, but I find a lot of Pardot users neglect to set up their Grading profiles and automations because they don’t know where to begin.
A Salesforce AE recently asked me if we had a best practices guide for migrating to Pardot from Eloqua, Hubspot, or Marketo. My team at Sercante does these frequently — but while we’ve talked about implementing Pardot for the first time here (see also: Real Talk: 5 Surprises When Implementing Pardot and Why Pardot Implementations “Fail”), I’ve never written on considerations specifically for switching platforms.
I tend to nerd out when it comes to advanced form styling in Pardot. I get personal satisfaction from taking a form beyond its default “out-of-the-box” capabilities to meet a specific requirement or use case.
Recently a client brought a unique challenge to me that required advanced form styling.
The client in question had a form on their website to collect additional data on Prospects. They had introduced a new field to the form and promptly saw an influx in Connector errors.