First Name equals Last Name - Smart List possible?

[Anonymous]

We've recently been victims of some spam attacks, and I am trying to clean these names ouf of our system.

I am looking for a way to build a smart list that says "first name" = "last name," since that is one of the main patterns we're seeing in this attack. I've tried a bunch of things to no avail.

Is this even possible?

[Anonymous]

Is the inferred company Peg Tech? If so, I have had the same problem and can't figure out how to eliminate it. I have even added number validation to our forms.

[Anonymous]

No, most of these had no inferred company...it is close to 17K names, so kind of all over the place!

[Anonymous]

Wow! That is 17K more spam leads than we have had!

[Anonymous]

If you're using Saleforce, you maybe able to use a workflow rule to change one of the name to some unique value that you may be able to delete after the data is synced backed to Marketo.

[Itay_Billet4]

One solution is exporting all leads into an excel and filtering only the ones that "First Name = Last Name" , then create a custom field in Marketo. Create a column in the excel for this field (it could say "duplicate = yes") and import the excel back to Marketo (it will de-dupe based on the email).
Now you'll be able to use this field in smart lists and delete those leads.

SFDC workflow will help moving forward, as workflow applies only to record creation / updates (not to records that exist in the DB)

[Anonymous]

Thanks. It looks like there is no simple, list-building solution in Marketo? 

I'd rather not create custom fields, workflows, etc. We've already taken care of the spam attack on the front end -- we just need to get these folks out of our system.

Thanks for the suggestions!

[Anonymous]

Another solution maybe to Export a list to Excel as Itay suggested but to import the list which you want to delete into a Static List. Create a Smart List with "Member of List" pointing to the list that was created and Delete those Leads. But with over 17K records, this exporting to Excel may not be feasible.