Edward_Unthank_

Interesting! Must be a new improvement in Marketo, change of phrasing. It's the same thing, but "person" seems less misleading than "lead."

So long as you add the leads to be excluded to the program as "Exclusion" status, that piece of content will be skipped in the cast, so you won't waste a week of nurture!

The "Delete Lead" flow step in the smart campaign Justin describes will do the actual work of deleting the leads, after you've exported the leads.Edward

Exactly right. Because the Pre-Promotion smart campaigns are run first (before smart campaigns run upon promotion), the additional filters will keep any action from happening on the desired smart campaigns.

Also, I always export those leads first with all of their fields and save them on a work computer somewhere. No reason in having all that data go away irreparably. Export all lead data first, then do what Justin recommends. Edward

You can do this without a special feature request, if you're clever with order of operations.Lifecycle Processing, which starts out with a "lead is created" trigger and then runs through smart campaigns that are linked, can go through and change lead values. These happen upon the "lead is created" t...

Hey Rashida,I have a feeling that Brite Verify is the closest to what you're looking for. Depending on what you're wanting to do with "validation," you can accomplish some things by an operational program with smart campaigns that can clean data. I've heard some people coin this a "data washing mach...

Hey Racquel!I gave a presentation at Marketo Summit 2014 on how to do this!We use email cast programs for this, add people to the email cast program with an "Exclusion" progression status, and have the individual casts in the engagement program call the "Send Email" smart campaign within each email ...

Agreed. I suspect that a long time ago Marketo baked in the actual field names into the code of smart lists and flow steps, instead of the field unique IDs, and that's an enormous amount of reprogramming to change all of those references in all client instances to be the unique IDs of the fields ins...