Level 10

Anonymous Lead Promotion to Known Lead – Munchkin V2 Behavior

Mike_Reynolds2 · 2015-12-08T22:57:01+00:00

Included in this article Summary How Leads Become Known Anonymous Web Activity Logging Triggered Smart Campaigns Revised 9/15/2023 Clarified Qualification Rules Behavior with regard to the date of a triggering activity Summary When a person visits a web page with your Munchkin tracking code on it, that web activity is tracked for that anonymous lead. When a lead takes action to become known, a lead record is created in your Marketo lead database and the anonymous web activity that lead had prior to becoming known is included in that new lead record. Any smart campaigns that would have triggered off of that web activity will then fire in the order of when the web activity occurred. How Leads Become Known There are three main ways that an anonymous web activity record can be converted into a known lead in your Marketo lead database. 1. Fills out form. If the anonymous lead fills out a Marketo form, that will create a new known lead record. The anonymous web activity that lead had before becoming known will be associated to that new known lead record. 2. Clicks a link in an email. Hyperlinks in emails are automatically decorated with a tracking code that is used to associate an anonymous record back to a known lead record. If you have a lead in your database that hasn’t had any web activity yet (like a lead that was added from a list import), when the lead clicks the hyperlink in the email, that tracking code in the hyperlink will associate their Munchkin cookie to your known lead record and all of that anonymous web activity will be logged into that known lead record. 3. API call. You can use an API call to associate an anonymous web activity record to a known lead record. This can be done through a SOAP API syncLead call, or by a REST API Associate Lead call. Anonymous Web Activity Logging Anonymous lead activity is housed in a different database. This doesn’t create a lead record until the lead is promoted to a known lead. All activity a lead had prior to becoming known will be logged chronologically in the new lead record with the correct corresponding date/time stamps once the lead becomes known. Triggered Smart Campaigns Anonymous leads can’t trigger smart campaigns. However, when a lead becomes known, the active smart campaigns that would have triggered from the anonymous activity will be triggered. All trigger campaigns currently active at the time the lead becomes known will be triggered if the lead took the action being triggered on while anonymous. Only campaigns currently active at the time the lead becomes known will be triggered. The campaign definition at the time it is triggered is what will be executed. For example, if the campaign has a Score Change of +10 but is changed to +5 just before the lead becomes known, the new lead created will be given a score of 5, not 10. The campaigns that are triggered by the anonymous activity will be processed in order of the activities that occurred, oldest to newest. In the lead’s activity log, all campaign activities (with one exception below) will be logged with the time stamp of when the lead becomes known, right before the New Lead activity. Interesting Moment flow step activities will be backdated to the date and time when the corresponding anonymous activity occurred. Not all flow actions in the campaign will be executed. When leads flow through campaigns as a result of the promotion to known lead, only specific flow actions will be processed. All other flow actions will be ignored. The flow actions executed will be: 1. Change Score 2. Interesting Moment 3. Change Data Value 4. Add to List 5. Remove from List Secondary campaigns (campaigns triggered off of activities performed by the campaigns triggered by the lead promotion) will not be triggered. Pruned activities will not trigger campaigns. Anonymous web activity is not stored forever—it gets pruned over time, so any activity that has been pruned is no longer there to be triggered off of. When determining whether a person will qualify for a replayed trigger campaign, the time that the activity occurred is used. For example, if you have a campaign listening for Visits Web Page events, and qualification rules set to let leads run through once per hour, each event that is more than one hour apart will qualify the lead for the campaign. This may lead to several instances of the same campaign running for a person upon promotion to known.

Forum|Forum|10 years ago
December 8, 2015
14 replies
35958 views

Included in this article

Summary
How Leads Become Known
Anonymous Web Activity Logging
Triggered Smart Campaigns

Revised 9/15/2023

Clarified Qualification Rules Behavior with regard to the date of a triggering activity

Summary

When a person visits a web page with your Munchkin tracking code on it, that web activity is tracked for that anonymous lead. When a lead takes action to become known, a lead record is created in your Marketo lead database and the anonymous web activity that lead had prior to becoming known is included in that new lead record. Any smart campaigns that would have triggered off of that web activity will then fire in the order of when the web activity occurred.

How Leads Become Known

There are three main ways that an anonymous web activity record can be converted into a known lead in your Marketo lead database.

1. Fills out form. If the anonymous lead fills out a Marketo form, that will create a new known lead record. The anonymous web activity that lead had before becoming known will be associated to that new known lead record.

2. Clicks a link in an email. Hyperlinks in emails are automatically decorated with a tracking code that is used to associate an anonymous record back to a known lead record. If you have a lead in your database that hasn’t had any web activity yet (like a lead that was added from a list import), when the lead clicks the hyperlink in the email, that tracking code in the hyperlink will associate their Munchkin cookie to your known lead record and all of that anonymous web activity will be logged into that known lead record.

3. API call. You can use an API call to associate an anonymous web activity record to a known lead record. This can be done through a SOAP API syncLead call, or by a REST API Associate Lead call.

Anonymous Web Activity Logging

Anonymous lead activity is housed in a different database. This doesn’t create a lead record until the lead is promoted to a known lead.
All activity a lead had prior to becoming known will be logged chronologically in the new lead record with the correct corresponding date/time stamps once the lead becomes known.

Triggered Smart Campaigns

Anonymous leads can’t trigger smart campaigns. However, when a lead becomes known, the active smart campaigns that would have triggered from the anonymous activity will be triggered.
All trigger campaigns currently active at the time the lead becomes known will be triggered if the lead took the action being triggered on while anonymous.
Only campaigns currently active at the time the lead becomes known will be triggered.

The campaign definition at the time it is triggered is what will be executed. For example, if the campaign has a Score Change of +10 but is changed to +5 just before the lead becomes known, the new lead created will be given a score of 5, not 10.
The campaigns that are triggered by the anonymous activity will be processed in order of the activities that occurred, oldest to newest.
In the lead’s activity log, all campaign activities (with one exception below) will be logged with the time stamp of when the lead becomes known, right before the New Lead activity.
Interesting Moment flow step activities will be backdated to the date and time when the corresponding anonymous activity occurred.

Not all flow actions in the campaign will be executed. When leads flow through campaigns as a result of the promotion to known lead, only specific flow actions will be processed. All other flow actions will be ignored. The flow actions executed will be:

1. Change Score

2. Interesting Moment

3. Change Data Value

4. Add to List

5. Remove from List

Secondary campaigns (campaigns triggered off of activities performed by the campaigns triggered by the lead promotion) will not be triggered.

Pruned activities will not trigger campaigns. Anonymous web activity is not stored forever—it gets pruned over time, so any activity that has been pruned is no longer there to be triggered off of.
When determining whether a person will qualify for a replayed trigger campaign, the time that the activity occurred is used. For example, if you have a campaign listening for Visits Web Page events, and qualification rules set to let leads run through once per hour, each event that is more than one hour apart will qualify the lead for the campaign. This may lead to several instances of the same campaign running for a person upon promotion to known.

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

SanfordWhiteman

Level 10

Mike, what's the changelog from the last ver?

Mike_Reynolds2Author

Level 10

The change was to update the screen shots of the activity log. You had pointed out the error in Anonymous Lead Upgrades – Under The Hood and I realized this one showed the same old screen shots. Just swapped them out with the new ones

A

AutumnMa1

Level 3

You say that these will "retroactively" run upon known

1. Change Score

2. Interesting Moment

3. Change Data Value

4. Add to List

5. Remove from List

Trying to understand if I can also Change Status of SFDC Campaign or Programs in my flow for newly known leads.

So if I have a smart list

And the flow includes a change of status for a SFDC campaign or a program. You are saying that this won't be updated for the lead upon when it's known? or because I have added the lead is created step here, it will do all flow actions?

Mike_Reynolds2Author

Level 10

@Autumn Mahoney

Since your campaign pictured above has two triggers, those triggers will work independently of one another. So if a lead is created, the Lead is Created trigger will fire, and if the lead visits the "Request a Demo" landing page, the second trigger would fire, sending the lead through the campaign a second time.

The Lead is Created trigger would send the lead through the campaign and all flow steps (like your SFDC campaign status change flow step) would apply. The second time the lead goes through, from the Visits Web Page trigger, this would be from the replay activity, so only those five specified flow steps would apply, and the others would be skipped.

One thing to watch out for though. Let's say you also have a Change Score +5 flow step. Since the lead will be sent through the campaign twice, the score would be increased by 5 twice, resulting in a final lead score of 10.

Anthony_Pica

Level 4

Mike Reynolds wrote:
The Lead is Created trigger would send the lead through the campaign and all flow steps (like your SFDC campaign status change flow step) would apply.

Just to be clear, do newly known leads run through SFDC campaign status change flow steps? The above article states that only the following flow actions are activated when anonymous leads become known:

1. Change Score

2. Interesting Moment

3. Change Data Value

4. Add to List

5. Remove from List

SanfordWhiteman

Level 10

If the trigger for that flow step is Lead is Created, that's, let's say, the "real-time trigger" as opposed to the "time-delayed trigger" that is replayed.

The real-time trigger doesn't have the replay restrictions.

Stepan_Egorov

Level 2

Hi guys,

This passage seems obvious to me:

All activity a lead had prior to becoming known will be logged chronologically in the new lead record with the correct corresponding date/time stamps once the lead becomes known.

Other topics on the forum also suggest that the anonymous and known records should merge, but that sort of doesn't happen in our case.

In my instance, after the anonymous lead #1576950 becomes a known one, his scores are zeroed out (actually, a new known user #1576951 is created with his "aleternative" score): http://prntscr.com/it9h6e.

After zeroing out, the "original" #1576950 anonyomus score keeps being counted, and recorded in the log of the user #1576951, but independently: http://prntscr.com/it9jjs

Only after some time when these strange things happen I see "Merge People" in the log: http://prntscr.com/ita2zz But the resulting ALX Person Score is 20, while in fact it should be 25 (#1576950 + #1576951).

Why don't the records merge in terms of score? I've tested it with several test users, but the results are the same.

Any help is appreciated.

Dan_Stevens_

Level 10

I think you may confusing the activity - which does get merged when the person becomes known - and the REPLAY of the smart campaigns that are only applicable if you've been upgraded to Munchkin v2 (many have not been upgraded - including us). "Change score" is one of those replay campaigns that would trigger under v2.

Any update on when customers will be migrated to Munchkin v2?

Stepan_Egorov

Level 2

The campaigns are actually played, as can be seen on the screenshot, but the scores of the anonymous lead are not added to those of the known lead.

Is this addition what you mean by replaying the campaigns?

If so, and if we're not still on Munchkin v2, then that's incredibly sad.

Dan_Stevens_

Level 10

It’s hard to tell if these are replays from prior activity or played/triggered as a result of current activity. The only way to know if you’re on v2 is to file a Support ticket and ask them

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded