Stop Marketo Triggers From Firing When Records Are Merged

[Anonymous]

We are working on a tedious de-duping project and I noticed that when records are merged, it's causing some of the Marketo Triggers to fire. 

For example, we have one trigger that is if Lead is Added to SFDC Campaign, change a customer date field called Last Campaign Response Date to (today's date). When duplicate records are merged, the surviving record is "added" to the SFDC Campaign, causing the trigger to fire and the custom date field to change, even though it retains the original campaign response date. 

Is there any way to configure this trigger to not fire for records that have just been merged? 

[Tara_Petre]

You could add all the duplicate records to a list and suppress that list in your campaign.  

Once you've finished your dedupe project you could delete the list or remove the filter from your smart list to allow the leads to qualify for the campaign at a later date.

[Kenny_Elkington]

Hi Tracie,

A solution such as Tara's is probably the most feasible.  This behavior is an artifact of how Salesforce treats merges between records and there's nothing we can use on the Marketo side to determine whether membership is the result of an organic add or a merge.