AnsweredAssumed Answered

Why wasn't this lead added to a program after being known?

Question asked by 768fcb04caedb7d07293549eb38dae94791735d6 on Dec 21, 2016
Latest reply on Dec 21, 2016 by 31c49a9e92cfdfc36ec09f16a3d031bc05f44a62

I have a program that's synced to Salesforce set up with the following smart campaign:


Smart List: Visits Web Page

Flow: Change Program Status & Create Task


In the results tab, I see the following:


Change Program Status - Skipped Cannot add an anonymous lead to a program

Sync Lead to SFDC - Failed: {MktSyncLeadtoSfdcImpl::synLead} cannot push anonymous lead to SFDC

Create Task - Visited web page "Landing Page 01"


Those activity detail errors/warnings are expected since the lead is anonymous. However, my understanding is that when an anonymous lead becomes known, the triggers that would have affected the anonymous lead are executed once the lead becomes known. Therefore, I would expect the Change Program Status and Create Task flows to execute when the lead became known, but they didn't (the lead isn't a member of the program and an SFDC task wasn't created).


What am I missing?