Pardot First DonationAutomation From Salesforce Contact Record

We have defined an Engagement Studio program for first-time donors in Pardot. We want all contacts with emails to get on this program from Salesforce. 

Here is the plan:

  • Contact has a closed/won opportunity and so the Number of Household Gifts goes from zero to 1 at some point for all members of the household account. 
  • Pardot is configured to sync all new prospects that have donations more than zero. Note that preexisting contacts may not sync.
  • A Pardot automation rule watches for new prospects with 1 gift In the last 60 days who are not yet on the start list of the warming engagement plan program and adds them to the start list.
  • Engagement studio runs its course and adds the prospect to the completed list eventually.
  • Any older contacts who become donors are not in Pardot and may not be synced because they predate our Pardot Salesforce Connector. These flagged one a month in a Wall of Zero report and can be synced manually.

The Number of Household Donations ...  read more

Lightning Pages: Best Practices

These are the slides for Texas Dreamin. I did about 4 months of research for this presentation and will be publishing more of my findings including things that don’t work well. This presentation ...  read more

Neverbounce Email Check

  1. When a new contact is created, Zapier runs. If there is an email address, it is checked with NeverBounce. If the email returns invalid, a task is created to check it. The task contains key information about the contact as well as returned information from Neverbounce to make the resolution go quickly.
  1. When the email field of a contact is updated, Zapier runs. If there is an email address, it is checked with NeverBounce. If the email returns invalid, a task is created to check it.
    1. I added a check prior to calling Neverbounce to make sure we don’t already have an open task against this contact. This prevents double checking Quinn, for example, more than one of the conditions become true for bouncing emails.
    When the Email Bounced Reason of contact is updated, Zapier runs. If IsEmailBounced is true and there is an email, it is checked with NeverBounce. If the email returns invalid, a task is created to check it.
    1. I added a check prior to calling Neverbounce to make sure we don’t already have an open task against this contact. This prevents double checking Quinn, for example, more than one of the conditions become true for bouncing emails. Note that this might fail if there is a lead on the campaign. #Techdebt 
    1. When the Email Bounced flag of Campaign Member is set to true, Zapier runs. If the Links Clicked does not contain the work Neverbounce and there is an email, it is checked with NeverBounce. The results are appended to the campaign member Links Clicked field with the word Neverbounce. If the email returns invalid, a task is created to check it. The task is associated with both the contact and the campaign.
      1. I added a check prior to calling Neverbounce to make sure we don’t already have an open task against this contact. This prevents double checking Quinn, for example, more than one of the conditions become true for bouncing emails.

      Techdebt: The above only works when the number of elements is 170,000 or less. That is OK for all but Campaign Member. Campaign member might fail one day.

      All four of these processes are entirely outside ...  read more

Unpacking Winter 2021

Winter 2022 arrived! I can’t wait to check on the status of the “Top 10 Candy” list for organizations who have the Power ot Ten license grant like me. However, first I need to help avoid the buildup ...  read more