Warning: Anonymous Leads and Lead Lifecycle Alerts

[Mike_Reynolds2]

There are two different parts to this, the current behavior before Munchkin V2, and the behavior later on after Munchkin V2 rolls out.

Current behavior:

If the "Lead was Created" filter is in use, all anonymous leads will be excluded from the campaign. Without having been converted from anonymous to known, there is no known lead record being, so there is no "Lead was Created" activity logged in the anonymous record. Therefore, if the "Lead was Created" filter is in use and set to true, the leads without that "Lead Created" activity (the anonymous leads) would be excluded.

Behavior after Munchkin V2 rolls out:

If the "Lead was Created" filter is in use, it will stop the campaign from going through the replay activity at the time of lead promotion. So, at the time a lead goes from being an anonymous record to being promoted to a known lead, during that promotion activity, all campaigns that could have previously been triggered by the anonymous activity will be triggered and "replayed" (the campaign replay activity). This takes the campaigns that could have been triggered by the triggering activity (ex: visit web page) and evaluates whether the anonymous record could have qualified for that campaign at that time using the current configuration of the campaign.So, let's say the campaign has a "Visit Web Page" trigger in combination with the "Lead was Created" filter. At the time the anonymous record visited the web page, it had not yet been created as a known lead, so there would be no "Lead Created" activity logged yet in the activity log. So, the anonymous record would match the trigger because it visited the web page, but the "Lead was Created" filter in the smart list would rule the anonymous record out because that activity would not yet have been logged at the time of the campaign replay.

It's all about the order of operations for the logging of activities. Check out the specifics in the Triggered Campaigns part of Anonymous Lead Upgrades – Under The Hood  The post-Munchkin V2 order of activity logging is given there:

In order to be able to identify which campaigns were triggered as part of the replay activity, they are logged right before the "Lead was Created" activity (New Lead in screen shot). So, since the campaigns are going through the replay process before the "Lead Created" activity is logged, the "Lead was Created" filter set to true would exclude them from that campaign and the campaign wouldn't be replayed.

[Dan_Stevens_]

Mike, any update on when Munchkin v2 will be rolled out to customers' instances?

[Mike_Reynolds2]

There isn't any kind of firm timeline on that rollout. The Anonymous Lead Upgrades – Release Schedule doc talks about this, but unfortunately there's not a lot of details I can give because it can't be determined yet.

The first phase was removing access to the anonymous leads. That's already done. The next phase is back end upgrades. There are improvements being made to many processes to pave the way towards the final move to Munchkin V2. In order for Munchkin V2 to perform as well as it is supposed to, multiple other server processes need to come up to speed as well. The tricky part is that each server group has to be deployed one at a time in a staggered release. Engineering has to ensure that each server group is successfully deployed before the next one so that there aren't any problems. It's safer that way, but does have the trade off of making it harder to pin down when the upgrades will happen.

[Dan_Stevens_]

Once this is known, will Marketo be notifying its customers as to when their instance will be updated?

[Mike_Reynolds2]

I'm not 100% positive on the specifics for that part, but Arjun Nair​ may have more details. Let me check in and get back to you with the specifics.

[Dan_Stevens_]

Thanks.  Can you quickly confirm if Greg's matrix below will be the correct behavior once v2 is deployed?

[Dan_Stevens_]

Good to know.  I misunderstood this comment that you cautioned everyone about:

"After the new lead promotion behavior is rolled out with Munchkin v2, using the "Lead was Created" filter will stop the campaign from ever being triggered during the REPLAY activity at lead promotion.  This means that no anonymous leads being promoted to known leads will ever go through these campaigns."

The keyword being "REPLAY".  So as long as we're using the "Lead was Created" filter to prevent ANY anonymous lead from EVER triggering our lead lifecycle campaigns, we're safe to leave this filter intact, even after v2 has been deployed, correct?

[Mike_Reynolds2]

Depending on your particular definition of "safe" LoL.

If your goal is to prevent anonymous leads from going through the campaign right now (pre-Munchkin V2), AND to prevent the campaign from being triggered during the replay of the campaign (after Munchkin V2) at lead promotion, then yes, that's the safe way to go.

Other customers may want to still let the leads go through these campaigns at promotion to known lead after Munchkin V2 rolls out, so that's a different scenario.

[Dan_Stevens_]

I'm confused again.  I have no desire in any replay.  I just want to prevent anonymous leads from ever going through these campaigns - both now and after v2.  Yet, once they become known, then they will qualify.  Are you saying that this will still be an issue if we keep the filter in place?

[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.