Managing Spam/CANSPAM/GDPR Accounts

Amanda Lee

Good morning! I searched the community for an answer but didn't see anything that really answered my question so if you all have a link to forward me to for this information, please let me know.

I'm wondering how you all manage spam accounts? We are adding captcha to our surveys, but there still seem to be quite a few stragglers getting through. I've about figured out that it's people who want a PDF download, but don't want us to email them or have their real information. I realize queries can lack a bit of detail, but I'd be interested to know if anyone has a good query they use to help suppress these spam accounts from being targeted.

My initial thought was something like the following:

• Email Status = Bad (Hard Bounce) and/or
• First or last name contains any of the following: !@#$%,~Ìó■ and/or
• Domain = mail.ru, web.de, 007game.ru, 1.aaple.ru, 10g.pl, 123.com, 123hummer.com, 126.com, 163.com, .eu, .uk, .au, .ca, etc.

I'd also be interested in knowing how you see fit to suppress CANSPAM and GDPR addresses from your email list.

Thanks in advance for any replies! - Amanda

Lacey Kruger

Hi Amanda,

Good question here. Rather than trying to pinpoint specific formats of your “bad” constituent records, we typically recommend creating a suppression group of disengaged constituents. It's a broader audience but we find that the “bad” records naturally fall into this group. To set this up, we use a combination of Engagement Factors and Query in Luminate. My typical approach is to create a group of constituents who:

• have not donated in the past 365 days
• have not clicked on an email in the past 365 days (note: we don't recommend using “Opens” anymore for this)
• have not taken any action on your Luminate site in the past 365 days
• are not Sustaining Donors
• have been a constituent for longer than 6 months