Warning: Anonymous Leads and Lead Lifecycle Alerts

[Anonymous]

I just had a number of anonymous leads run through my lead lifecycle campaign and send alerts to my inside sales team - except those alerts appeared blank because we have no information on the anonymous lead (aside from their extreme interest in our website!).

I spoke with support who explained that anonymous leads can still run through scoring and revenue model campaigns (which is the opposite of what was stated in some of the discussion posts from earlier this year, which talked about the removal of the "is anonymous" filter).

For anyone else working on their lifecycle / revenue modeler - support advised that for certain programs (like MQL fast track), add "lead is created" as a filter to ensure that anonymous leads can't meet scoring thresholds.

[Mike_Reynolds2]

Using the "Lead was Created" filter set to true will stop anonymous leads from going through the campaign currently before V2.

After V2 rolls out, the "Lead was Created" filter will stop the campaign from being triggered during the replay process.

After V2 rolls out, the "Lead was Created" filter will NOT stop known leads from going through the campaign because they have the 'lead created' activity (because they're known leads). The replay of the campaign during lead promotion will not happen, but let's say the lead does whatever action triggers the campaign later on after they're known. In that case the campaign would trigger and they'd go through.

[Dan_Stevens_]

Makes sense - thanks for confirming, Mike.  The filter is only added to a handful of lead lifecycle campaigns - where a lead can only run through the campaign ONCE anyway.  So if they qualify - and they're KNOWN - then they will successfully run through the campaign before and after v2.

[Grégoire_Miche2]

Hi Mike,

Thx, I feel this what I have capture in the table above

-Greg

[Dan_Stevens_]

I think this is why we need further clarification from Marketo (Mike Reynolds​).  There seems to still be a lot of confusion on how this will play out once Munchkin v2 is fully rolled out to everyone (and when that will take place).  Ideally, this would have happened at the same time as the removal of the "is anonymous" filter and then we wouldn't have all of these questions.  But understand, this wasn't feasible from an operations perspective.

Maybe Marketo should consider having a live webcast around this for their customers.  And unlike their typical webcasts, keep the lines open so that we can ask questions in real time.  Let's have a real dialogue around this (vs. just one-way).

[Josh_Hill13]

Thanks Dan, I saw your discussion with Greg and also had a serious problem which took a week for Support to confirm with engineering:

1. Is Anonymous is removed from the UI. Once you remove it, it's gone.
2. Is Anonymous=F is now ignored in smart lists, BUT Marketo still allows Anonymous leads to go through many campaigns related to Visits Web Page, scoring, etc.
3. Is Anonymous=T we were told also no longer works, but it actually seems to break a smart list. You can no longer pull a list of Anonymous either.
4. The original docs said that Scoring on Visits would occur at the time of Known, and backfill scores in the past at the Known moment. This is NOT true. The reality is that Visits Web Page still triggers on Anonymous until the next update (or later) when the backend changes are completed.

Basically, the docs on the main site are wrong and you must use workarounds like Email Address IS NOT EMPTY and others to ensure Anonymous don't go through the wrong flows. The risk is that many leads aren't scored until after Known, if you do things like Email Address IS NOT EMPTY. And that part could be a big deal.

[Aubrey_Morgan]

I just noticed this as well! So weird and frustrating. We changed all of our campaigns to accommodate this change, just for this to go back to how it was before the Feb release

[Danni_Holleran]

Thanks for this info Christina! That's good to know re: the filter lead is created.

[SanfordWhiteman]

Agree, Christina -- this was not supposed to happen per the pre-release discussions, and I'm still uncertain whether there's an upcoming release that is truly going to turn this off.