TROUBLESHOOTING Anonymous Lead Upgrades – Workaround | Community
Skip to main content
Mike_Reynolds2
Level 10
February 16, 2016

TROUBLESHOOTING Anonymous Lead Upgrades – Workaround

  • February 16, 2016
  • 11 replies
  • 1894 views

Included in this article

  1. Overview
  2. Stopping Send Alerts for Anonymous leads
  3. Excluding Anonymous Leads entirely (use with caution)
  4. Deleting Lead Partitions

Revised 2/19/2016

Added caution on "Lead Was Created" work around

Added "Stopping Send Alerts" work around

Added "Deleting Lead Partitions" Known issue

Revised 2/17/2016

Marked "Lead Was Created" work around as under review

1. Overview

The upgrade to anonymous leads is a two—step process. The first part removes the “Is Anonymous” filter and performs all other changes to the Marketo UI as outlined in the Changes Inside Marketo UI documentation here. The second part is the introduction of Munchkin V2. This piece is where the new lead promotion behavior is introduced as outlined in the Munchkin V2 Behavior documentation here. The changes to the Marketo UI removes access to anonymous leads, but they do still exist inside Marketo until the Munchkin V2 piece rolls out later this year.

In the meantime between now and then, your smart campaigns will include these anonymous leads even though you won’t be able to access those leads. This can result in things like blank Send Alert emails going out for leads that can’t be accessed. This document will show you how to exclude those anonymous leads pending the Munchkin V2 release.

2. Stopping Send Alerts for Anonymous Leads

The biggest problem Support has seen so far is with blank Send Alert emails being sent for anonymous leads that can’t be accessed. There is a very isolated use case when this occurs. The Send Alert flow step sends the email to the Lead Owner or the Account owner, but anonymous leads can’t be synced to SFDC, so the only time anonymous leads could have an Alert email sent is if the flow step is set to send “To Other Emails”.

To stop anonymous leads from having the Alert email sent, add a choice to the flow step with the condition that if the Email Address is empty, do nothing. Since anonymous leads won’t have an email address, they will skip the flow step and the problem is resolved.

This solution will not require any changes after the Munchkin V2 roll out later this year. Since the campaign replay process on lead promotion does not execute Send Alert flow steps (described in Anonymous Lead Promotion to Known Lead – Munchkin V2 Behavior and Anonymous Lead Upgrades – Under The Hood), that replay process will not be affected.

3. Excluding Anonymous Leads (use with caution)

When a lead becomes a known lead, a Lead Was Created activity is logged. If the lead is still anonymous, it will not have this activity in its activity log. Adding the “Lead Was Created” filter in your Smart Lists and Smart Campaigns will stop all anonymous leads from going through the campaign.

Adding the filter

Remove the Date of Activity constraint in the filter by clicking the X on the right side. This will make the filter look for the activity for all time.

With this filter added like this, all leads that qualify will be known leads, and all anonymous leads that still exist will be ruled out.

4. Deleting Lead Partitions

Until Munchkin V2 rolls out, anonymous leads still exist in the lead database even though they can’t be accessed. Lead partitions can’t be deleted if there are leads still in them and you’ll get this error:

If you receive this error, the first step is to make sure these aren’t known leads. To do this, navigate to Admin > Workspaces & Partitions > Lead Partitions and click the “Show # of Leads” button.

This will open up the column where you can view how many known leads are in the partition. Any leads showing up here will be known leads.

Use a “Lead Partition” filter in a smart list to identify these leads, then move the leads to a different partition.

Once this is done, if you have zero leads showing in the partition but still get the error saying you can’t delete the partition because it has leads, open a case with Marketo Support. The anonymous leads will need to be deleted on the back end by our Engineering team.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

11 replies

Grégoire_Miche2
Level 10
February 16, 2016

Similarly, the "Not Lead Was created" filter (no time constraint) enables to run smart campaign only on anonymous leads that have not yet been promoted to know leads.

-Greg

Mike_Reynolds2
Level 10
February 17, 2016

Greg,

You're correct, using the "Not Lead Was Created" filter will allow you to run campaigns on anonymous leads only, but I would advise against using this method. The reason I recommend against it is because it will only work between now and when the Munchkin V2 upgrade is rolled out later this year. The roll out of that piece is a staggered roll out over time and we don't have a firm schedule because it will vary depending on how each server group responds.

Yes, it will work right now to target anonymous leads, you're correct about that. However, as soon as anonymous leads are fully removed in that Munchkin V2 roll out, it will break it wherever used, the same way that using the "Is Anonymous" filter (set to true) would. You can use it right now, but ultimately it's just delaying the inevitable of having to change the process to stop targeting anonymous leads (which will no longer exist after Munchkin V2 rolls out), so putting it in place now only creates more work later since it will have to be removed again later. Sorry.

Grégoire_Miche2
Level 10
February 19, 2016

Hi Mike,

Basically, this is the intend when adding this filter : preventing any triggering of the event during the replay phase.

But would this also block the campaign to trigger if the triggering event occurs again AFTER the lead has been promoted ? If this is true, this is a real trouble.

Time to consider the urgent need for this idea:

-Greg

Grégoire_Miche2
Level 10
February 19, 2016

I like the idea of the email address filter. But it may happen that Known leads without an email address are created in Marketo from the CRM. These will be excluded from the flow step.

-Greg

Mike_Reynolds2
Level 10
February 20, 2016

Greg,

That's true, but having leads without email addresses syncing from CRM into Marketo is not a best practice. Without an email address, there's no way to de-duplicate against that known lead record (form fill, list import, etc.), or to email the lead to get them to click a link to associate the anonymous record to the known lead either. Yes, those leads would be excluded from the flow step, but a bigger issue in that case would be a data integrity issue of whether your lead acquisition practices are helping or hurting your marketing practices.

Mike_Reynolds2
Level 10
February 20, 2016

Greg,

If the lead is a known lead and then later after promotion takes the action that triggers the campaign, the "Lead Was Created" filter would not stop them from going through the campaign. So, no, after the lead has already been promoted, it would not be excluded from the campaign

Grégoire_Miche2
Level 10
February 20, 2016

Hi Mike,

I agree about not sync'ing the empty email addresses being a best practice, but users are not always observants of best practices.

-Greg

Dan_Stevens_
Level 10
February 20, 2016

This may be fine for preventing alerts from being sent out (assuming the lead has no email address yet - but as Greg mentioned, not everyone adheres to these best practices), but what about all of the other flow steps that will still trigger?  That's why I preferred the "lead was created" filter since it's contained within the smart list and stops the lead right then and there from qualifying. Until Munchkin v2 is rolled out, without the "lead was created" filter, these leads will still qualify for the other 20 or so flow steps we have in our lead lifecycle campaigns.

The issue now is the delay in having Munchkin v2 rolled out alongside the way Marketo treats anonymous leads - and having these temporary workarounds in place (which affects 20 or so smart campaigns in our instance). Is it just technically unrealistic to roll it out now for all customers?

Mike_Reynolds2
Level 10
February 22, 2016

@Dan Stevens​,

On lead promotion, only 5 flow actions will be executed during the reply process:

1. Change Score

2. Interesting Moment

3. Change Data Value

4. Add to List

5. Remove from List

More details in Anonymous Lead Upgrades – Under The Hood

That's on lead promotion post-Munchkin V2 though, and I think you're referring to the time between now and then when the anonymous lead still exist. Honestly, it's a tough call. You can block all anonymous leads from ever going through the campaigns by using the "Lead was Created" filter. In your use case, that would probably work best. However, for others who are only concerned with stopping the Send Alert emails from going out--people who still want to have the leads go through the scoring changes or data value changes--the choice in the flow step is a better way to go because it doesn't block the entire campaign, just that one flow step.

The trade offs here are what happens after Munchkin V2 rolls out. If you don't want to change anything later on, if you want to just make one change now and not have to worry about it, use the choice in the flow step. For folks who want the campaign to still trigger on the campaign replay at lead promotion, the campaign will still be replayed without needing to make any more changes.

However, if your use case is different and you want to block all anonymous leads from the campaign across the board, then the "Lead Was Created" filter is a better way to go. All flow steps are still executed now, pre-Munchkin V2, so this would stop all anonymous leads from having any of those actions taken. The trade off is that, after Munchkin V2, 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. Use cases differ, so ultimately it's a judgement call that everyone is going to have to make themselves depending on their particular scenarios.

As far as the time before Munchkin V2 rolls out, it would be nice if we could push all upgrades out at the same time. Sure would make everyone's lives easier. However, on the back end, there are a very large number of other upgrades going on right now (system upgrades, not customer-facing) and they need to be done in sequence. The UI changes to remove access to Anonymous leads was part one. The back end system upgrades are the next part needed to lay the foundation for the Munchkin V2 part that comes after that. The back end upgrades are already going on now and I've been hearing that they're going really well, so we're getting all good news so far, but it still takes time. These back end upgrades are actually much much larger than the UI changes done to remove visibility to anonymous leads, so they have to be staggered out and monitored to ensure they're 100% before moving on.

Grégoire_Miche2
Level 10
April 17, 2016

Hi @Mike Reynolds​,

So if the "lead was created filter" block all un-promoted leads from entering the campaign and allows all promoted ones to run it, then the filter plays it's role of preventing replays to happen. So could you please elaborate more on the issue you want to raise ?

-Greg