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.

Show previous replies

Stepan_Egorov

Level 2

They're actually from the prior activity - I've tested multiple times and analyzed the log in detail.

I've contacted them, I'll reply here if I get some valuable answer (which is sometimes a desperate thing).

J

Jon_Wu

Level 4

I've been trying to architect around this for a while since many of my Smart Campaigns broke. After many back and forths with support, they told me that I was on Munchkin v2, but that the anonymous lead progression behavior did not apply to us yet and that it would be rolled out for us at an undetermined time in the future. They mentioned they would work to clarify this document as it was currently misleading. When I said that I was observing some of the behavior mentioned here, they said it's possible that engineering is rolling out pieces of this behavior little by little so any changes in behavior could be attributed to this slow rollout, but that I was definitely not on new lead progression behavior yet, despite already being on Munchkin v2.

I don't have much actionable from this other than to use some of the filters discussed in TROUBLESHOOTING Anonymous Lead Upgrades – Workaround, but hopefully just knowing this helps somebody else who's equally as confused as I am.

Dan_Stevens_

Level 10

Wow, thanks for sharing, Jon. Just last week, Support confirmed that we too were on Munchkin 2.0. Didn't realize that it doesn't mean that these replays would start working as expected. Troubling to hear this.

Ian_Suttie

Does anyone know if request campaigns will be executed if they are included as a step in a triggered campaign?

Let's say I have a smart campaign triggered by a web page visit. I understand that I can add the now-known user to a list (for example), but if that campaign also requests a second campaign what happens?

I can think of 3 possibilities:

1. the request campaign step is ignored

2. the requested campaign executes, but only the short list of supported actions in the 2nd campaign execute

3. the requested campaign executes and every step in that campaign execute

Anyone know what occurs?

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded