When a lead is merged / associated how can I make previously anonymous activity send an email?

[Jon_Wu]

Let's say I have a smart campaign that sends an email and is triggered by some activity such as Visits Web Page is example.com/promotion-confirmation. Then, let's say you hit that page anonymously, then we collect your email at a later time by calling associateLead to associate the previously anonymous activity with an email address.

At this point, I'd want my Smart Campaign to process all the events from when the lead was anonymous, and then send the email once the email is known, even though the web page visit happened in the past.

Instead, what seems to be happening is nothing. Next Generation Munchkin Tracking FAQ - Marketo Docs - Product Docs  seems to imply that my desired behavior (replay of anonymous events after merge) should be happening.

At the point of conversion (when the person becomes known in Marketo), all activities that occurred when the person was anonymous are appended to the person activity log and at this time they flow through the campaigns they qualify for.

To test, I visit the page in incognito, call associate lead and see if the campaign sent an email from the previous web page visit. Although the visit is added to history, the campaign isn't triggered. If I refresh the web page to add history now that the lead is associated, I do get an email.

This seems to be related to posts from Grégoire Michel​ (Removal of "Is Anonymous" filters. ), Mike Reynolds​, and Peter Szabo​ (Is Anonymous change >> will they get emails at merge? ).

Is what I want possible? Am I making wrong assumptions?

[Grégoire_Miche2]

Thx Mike.

-Greg

[SanfordWhiteman]

FWIW, I've also noticed that secondary campaigns do seem to run - they just don't send email. For a web page visit on my anonymous lead, I had a SC that changed a field, added the lead to a list, and added an interesting moment. Then I set up 3 separate SCs that were triggered off those 3 separate types of changes to send an email and log distinct interesting moments, and those all ran. It kind of seems like they process it all in real time, then just merge what happened anonymously, into the promoted lead when the promotion happens.

Of course this isn't in sync with the original description of Munchkin 2.0 (and who knows if you're on 2.0, so may be subject to change) but does a Call Webhook fire, even if a Send Mail ​doesn't?

[Jon_Wu]

Yes, which I knew if I was on 2.0. Scary to think that these little details could change after I get something working.

I did a brief test with a webhook on the primary and secondary campaigns and they seem to fire even when emails don't send - both in my initial SC and in secondary ones. I recently stopped firing webhooks for leads without an email because it was causing them to be treated as known and also breaking deduplication. They said this issue would go away later when I was migrated to some newer stuff, so maybe they were referring to Munchkin 2.0.

My previous case for firing webhooks was for scoring so I was writing back to the lead, so maybe if I don't write any fields back, it wouldn't be a problem. I feel like I don't want to get too far in the weeds until I know I'm on 2.0, otherwise things might fall apart if I get really creative.

[SanfordWhiteman]

Agree with everything you've said. It's frustrating to know there are upgrades this significant that are invisible to us.

On a positive note, this kind of stuff has made me hypersensitive to forced upgrades in my own projects!  So with FB gold versions are immutable, aren't aliased to new versions, and won't be sunsetted for a couple of years. That means we have to keep /v12, /v13, etc. all published even if we don't want anyone to use them.

[SanfordWhiteman]

2. If I want to trigger something every time once merge, could I add an Interesting Moment instead of initially sending an email, then have a separate campaign that fires every time the Interesting Moment is seen? That seems like it'd work just like #1, but without deduplication since all moments would theoretically be processed.

Nope, 'cuz nested triggers won't be fired for the backfilled events (supposedly).