Everything Salesforce Pardot

When we have Prospects in Pardot, we have nurtured them and they have become Marketing Qualified, we push them to Salesforce Sales Cloud (SC) for the Salespersons to work on. We can automate this by setting up Automation rules or Completion Action to assign them to Salesforce Users or Queues in Pardot. Once these Prospects sync with CRM, they are created as Leads (unless otherwise set by you) in SC. It is the Pardot Integration User that creates these Leads in SC. You may have multiple Lead Record Types in SC according to your organization's requirements. By default, Pardot will create a Lead in SC of the Lead Record Type that is set as default for the Pardot Integration User in its Profile. Here, in the above example, we can see that thought 3 Lead Record Types have been assigned or are visible to the Pardot Integration User, only the Campaign Lead Lead Record Type has been set as the Default Lead Record Type. Thus, all the Leads that are created by the Pardot Integration User w

While implementing Pardot, we have all configured Domain Management settings. While setting up the Email Sending Domains, we add a basic few domains, whereas, we might be using a few more while making regular email sends.  One such incident happened with one of my clients. They decided to set up an organizational level domain in the Email Sending Domains while they also used a regional sub-domain for sending emails. Image: Domain Management Setting The problem arose when, in one of their Email Templates, instead of using the organizational level domain, they set a regional sub-domain as the sender. Hence, when they sent an email, it bounced back from the recipient’s system as it did not recognize Pardot as an authorized sender for that sub-domain. The reason for these hard bounces was listed as a DMARC authentication error with the text, DMARC policy; 'sub-domain' domain; Unauthenticated email', etc,. So the option was to either change the Sender email or to get the sub-dom

Have you tried creating an Engagement Program (EP) in Pardot and discovered strange ways in which it works? I have had my share of confusion while running an EP and then analyzing its reports. Last week I made a send using an EP. Due to some incident, the send got delayed. Once the incident was solved, I was informed by Pardot Support that it would take a while to clear the backlog for the Engagement Studio and for it to get back on track. But, by that time a day had lapsed and the EP had skipped about 8000 prospects and gone to the next step. Hence, here are some of the learnings that I got from using Pardot EPs: 1. Using a particular date for email send only when required: Had I not set a date on sending the 1st email in my EP, EP would not have marked the Prospects as "Email not sent. Past scheduled date." Setting the email send to 'Immediately' would have been a better option since there were no Triggers or Rules before that node. Image: Engagement Studio Email R

Enabling and using the Resubscribe Functionality in Pardot can turn out to be a tricky one.  To explain briefly, if a Prospect Unsubscribes from any of your Newsletters or clicks Unsubscribe from all on the Preference Center, they do not receive any communication from us. If they want to opt-in again for a Newsletter or Sign up for an event, they can now choose to resubscribe to start receiving reminders or invitations by email in the future from us. To enable this feature in Pardot a few steps need to be taken: The feature needs to be enabled from Pardot Settings Texts to be displayed on the Form, in the email and on the Resubscribe Confirmation page need to be provided. Email template needs to be created for the email that will be sent out with more information and the Confirmation Link when the prospects click the link on the form Form Layout template needs to be tweaked for this feature to work Let us start with step 1 here to enable the feature in Pardot. Image: Pardot Settings Se