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

[Grégoire_Miche2]

With the disappearance of the "is anonymous" filter, trigger campaigns may run retroactively on leads at the moment they become known. See Re: Removal of "Is Anonymous" filters.   and Next Generation Munchkin Tracking FAQ - Marketo Docs - Product Docs

So the idea is to have a check box in the qualification rules for trigger campaigns that prevent the SC to run retroactively.

-Greg

[Michael_Langell]

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

[Grégoire_Miche2]

Hi Mike,

If I may, I would disagree with you on this :

• Edward's solution would work, but cannot be set up by mere mortals trying to use Marketo
• The use cases are many. For instance, we want to run scoring campaigns only on known leads. Read Removal of "Is Anonymous" filters.

Now, there is a very simple workaround: add a "lead was created" filter to trigger smart campaigns that are not supposed to trigger before lead creation.

-Greg

[Grégoire_Miche2]

Hi Edward,

Just add a "lead was created" filter to smart campaigns that are not supposed to fire retroactively.

-Greg

[SanfordWhiteman]

* The order of events in your v1 screenshot isn't the same as the order in the v2 prerelease docs. New Lead >> Fill Out Form (v1) vs. Fill Out Form >> New Lead (v2).  This may be a mere typo as v2 is referred to as "the same order it does currently."

FTR the public release of v2 changed the order from the prerelease notes.  It now matches the v1 order. 

[Grégoire_Miche2]

And a "Not lead was created" filter (no time constraint) for smart campaigns that should not run after lead creation.

-Greg

[Michael_Langell]

Guess my question is why would someone just want to run scoring campaigns on solely known leads or having them run through a campaign that assigns a lead source?.  What is that use case?    You are just losing data by doing that.  Like the Lead was Created filter, even easier.  

[Grégoire_Miche2]

Hi Mike,

Some of my customers want to restrict visit web page scores for certain high value pages to only known leads.

Others want to score differently behavior of known leads and behavior of anonymous leads for instance a web page visit valued +1 for an anonymous and +2 for a known lead.

On the opposite, some want to cap the behavior score that anonymous leads can get so that an anonymous lead does not reach MQL score before being known and will, to that intend, have smart campaigns that run for anonymous leads only.

-Greg

[Dan_Stevens_]

Just be aware, this is only a temporary solution.  According to this discussion here (TROUBLESHOOTING Anonymous Lead Upgrades – Workaround ) - specifically the last comment fromMike Reynolds​ - once Munchkin V2 has been rolled out to every customer, the "Lead Was Created" filter being used will stop the entire campaign from being able to be replayed at all--it won't even be called.  So we'll need to remember which campaigns we included that filter since it will need to be removed once again.

BTW, is there a reason why this specific idea does not show up in the search results - even when entering the title of the idea exactly?  Is it because of the quotes?  Scott Wilder​

[Grégoire_Miche2]

Tested the issue of the idea not showing and it does the same for me.

-Greg

[Mike_Reynolds2]

Hey guys, can you test the search option again when searching for the docs by the title? I believe we've gotten that fixed but just want to confirm. Thanks!