Lead converting to Contact triggering old campaign activity

[Chris_Saporito]

Anyone else have the issue of a lead converting to a contact in SFDC falsely triggering activity from the original lead record? It looks like when these are converting it is adding the activity to the new Contact record, which is triggering tasks to our SDR team. Example, lead attended an event in Sept., their "attended" status triggers a task. Lead was converted to a Contact in SFDC on 2/24 which added "attended" to the new record and triggered the same task.

I'm thinking that I could use the "Lead is Converted" or "Not Lead was Converted" fields with date of activity to keep these from triggering.

Anyone else have this issue or insight on this issue?

[Grégoire_Miche2]

Hi Chris,

I am not sure I understand the case. Is the trigger fired because the lead tasks are attached to the contact in Salesforce ? Or is the trigger fired because the contact all of a sudden gets an "attended" status ?

Of this is the second what is is this status? a lead field or a program membership field ?

You know more, you need to review the triggers in the campaign setting the task. If you could paste a screen shot of the trigger, it would help us to help you

-Greg

[Chris_Saporito]

Thanks, Greg.

Below is a look at the triggered task smart campaign. The trigger is firing because the contact all of the sudden gets an "attended" status from an event they attended back when the record was a lead.

I think if I added a new filter below #1 as "Not Lead was Converted" with a date of Today, it would help keep that from happening.

[Josh_Hill13]

Are you sure Marketo does not have a dupe on this record? I've seen a behavior where Marketo retains the lead record and the Contact, while SFDC will show the Lead was Converted. This seems to occur under certain permission circumstances, but it might be a bug.

[Grégoire_Miche2]

Hi Chris,

Yes, I think the filter will work.

My guess is that the reason why this happening is because both the lead and the contact were a program member, as duplicates, and you merged them on lead conversion. I would bet that the lead and the contact had a different member status. The contact was likely with a "lower" status than the lead, so when the merge occurred, the contact member status was suddenly upgraded, which triggered the campaign.

So the long term solution is to limit duplicate creation

-Greg

[Anonymous]

Totally different scenario, but I had a rule that triggered based off of Rating and since this is a field I can't sync from lead automatically (good ol' standard fields) it was coming in as a new MQL upon every conversion. Pretty annoying to reps since they are already engaged with those people. I had to use a "Not Lead Was Converted" filter as well