Creating a Pardot Spam Identification Process with Prospect Updater
Spam and junk data is the bane of my Pardot Admin existence. Nothing irks me more than seeing sales was notified of a form fill from [email protected], or that [email protected] was added to an engagement program. However, spam is an inevitable part of any marketing automation platform and there is only so much we can do to prevent it from entering, or remaining within, the system.
Kick Out the Spams
Song references aside, there are a number of things we can do to give junk data the boot from Pardot. I typically recommend creating dynamic lists that look for spam keywords in the most common Pardot Prospect fields (more info here). Then, use these lists to review and delete junk data on a regular basis. This process works great for small and mid-sized Pardot instances. But dynamic lists alone leave something to be desired for Pardot instances that intake thousands of new prospects a day.
When using Pardot native functionalities to identify junk, I found myself wanting to know why a prospect matched my junk lists:
- Which field on the prospect’s record was raising the spam flag?
- Is this legit junk or do my junk lists need to be tweaked?
Unable to solve this issue with native Pardot functionality alone, I turned to our Prospect Updater tool to see if I could turn this into a spam identification tool. With some tweaking and a lot of input from the Sercante Labs team, I was able to create a process that not only tells me why a prospect matched my spam criteria, but also allows me to easily manage spam clean up through the use of tags and automations rules.
Prospect Updater to the Rescue
With Prospect Updater, we moved the criteria from our junk catcher dynamic lists over to Google Sheets and created two new Pardot fields for the updater to use; “Spam Status” and “Spam Rules Matched.” Prospect Updater then compares all prospects in Pardot to the rules in the Google Sheet and updates their “Spam Status” field with one of the following values:
- Suspected Spam: Prospect Updater has determined this prospect matches one of the spam rules.
- Confirmed Spam: The Prospect has been reviewed and deemed to be spam
- Not Spam: The Prospect matches one or more of the spam rules but has been reviewed and is deemed not to be spam. The Prospect will be excluded from future Prospect Updater spam reviews.
- Reset: The Prospect’s junk data has been corrected. Prospect Updater will include this Prospect in future spam reviews.
The “Spam Rule Matched” field is also stamped with which spam criteria the Prospect matched.
Once the Prospect Updater Spam Identification process was up and running, I created new dynamic lists that collected Prospects marked as “Suspected Spam” and grouped them by the field that was spammy. This allows me to easily review and clean up these prospects on a regular basis.
Automate All the Things
To make the spam review process even easier, I put automation rules in place that would allow me to update prospects by tagging them or changing their “Spam Status” value. That way, I could use whichever update method was easiest at the moment.
- If a Prospect is indeed spam
- If a Prospect will always match spam but is not actually spam (i.e. Pamela Smith with email SPam[email protected])
- If a Prospect has been edited to no longer match spam rules
Having the “Spam Status” fields also allows me to create a suppression or “holding” dynamic list where new prospects will not be emailed until their “Spam Status” field is updated.
This process now runs like a well-oiled machine. It allows us to easily identify and kick out junk data and prevent said data from causing any damage in the short time it exists in Pardot.
Implementing the Prospect Updater Spam Identification Process
Set up and implementation of Prospect Updater is pretty painless. The first thing we need to do is set up a connected app:
- Complete the form on this page to get the package from us
- Install our Salesforce Package
- Set up a user and pre-authorize them to use the Connected App
The team will give you all the details and support you need to get this set up properly.
While the cogs are starting to move on that process, you can schedule a meeting with the Sercante Labs team to talk through your spam use case and any other challenges you might have for Prospect Updater. It can do a lot, and your wish is its command. The Sercante Labs team will then go back and do what developers do, and push buttons and stuff.
Once your Prospect Updater configuration is complete, the only thing left is a final training session to make sure you and your team are equipped to create, modify and maintain your new Super Spam Spotting System plus any other cool things you want to do with it (data clean up and normalization, maybe?).
Interested? Give the Labs team a shout through the form on the bottom of the Prospect Updater for Pardot page.
Thanks to Mike Fazio & Adam Erstelle for contributing to this solution.
The post Creating a Pardot Spam Identification Process with Prospect Updater appeared first on The Spot For Pardot.