"Do not execute retroactively on newly known leads" checkbox in the qualification rules

One question to voters : should the checkbox be checked by default or unchecked by default.

It is not that simple : most of users will not understand the implications and will keep the default value, so let's have this default value set correctly...

The setting could also be managed instance-wide or workspace wide.

It could also be manageable through a role. Some people would have the right to change the setting, others will only have the right to use the default, instance wide default.

-Greg

Another, related, use case is about smart campaign that should run for anonymous leads only ?

See the Removal of "Is Anonymous" filters.  thread.

-Greg

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" trigger, going through data management, lead assignment, and a medley of other operational processing. The first step of Lifecycle Processing is to change "Lifecycle Status" from "[null]" to the appropriate Lifecycle Status value.

In the new world of no anonymous leads, all smart campaigns that will be triggered before a lead has been promoted (Marketo's lingo for going from Anonymous to Known) won't have run through these smart campaigns in Lifecycle Processing yet.

Let's take a look at the order of operations in the Activity Log of when a lead is created:

Using the above, we can add a filter to all smart campaigns that we want to keep from going through said smart campaign, explicitly.

Which filters to add to triggered smart campaigns

EXPLICIT EXCLUSION OF 'ANONYMOUS' LEADS:

This filter would equal "Don't apply this smart campaign retrospectively to leads upon their promotion to known:"

EXPLICIT EXCLUSION OF 'KNOWN' LEADS:

This filter would equal "Only apply this smart campaign retrospectively to leads upon their promotion to known, but exclude any leads who are already known:"

Don't have Lifecycle Processing and aren't ready for that project yet?

Create a new Marketo-only boolean field called "Is Promoted" and change the data value to "true" with a smart campaign triggered by "Lead is created." By default, the field will be unchecked (false) for new leads. Only your smart campaign, upon triggering, will check that box (become true). Use that as a filter in the smart campaigns you explicitly want to exclude from "upon promotion" smart campaigns.

Then your filter in your smart campaigns becomes "Is Promoted" with values of true or false, and you get (operationally) the same functionality (although inverse) of "Is Anonymous" was providing.

Best,

Edward Unthank | Founder, Etumos

Hi Guys,

I agree with Edward, this should work (ought to be tested though).

But still far too complex to set up and error prone. We really do not want Marketo users to all have IT architect background in order to understand how to set it up. It should stay manageable by MARKETING people...

One of the key advantages of Marketo over the competition (at least the other high end products) is that it is intended to be operated by marketing teams, and implemented in what I call "Low IT" projects. It would be, IMHO, a very dangerous path to forget about this. I am not saying that IT experts are not needed for the most complex things (integrations, webhooks, JS), but in the very case of simply setting up a series of smart campaigns that should trigger or not when the lead becomes "promoted", it should really not require a level of process logic that is more the apanage of a software engineer than of a Marketing executive.

-Greg

Edward has a nice solution to this with the "Is Promoted" filter.

I will have to be honest though, I think the use cases in general for excluding anonymous leads from processing through certain smart campaigns, whether for scoring or some other purpose are weak.

I know I will not be excluding any leads from interesting moment/list actions, and I think the scoring data is useful, even though we cannot do anything with it now until the record is known.  By not excluding records from scoring campaigns, at least you know the score of the record, how many interactions that record had with your org before filling out a form.

-Mike