Merging of leads is triggering smart campaign twice | Community
Skip to main content
A
Anonymous
January 23, 2013
Solved

Merging of leads is triggering smart campaign twice

  • January 23, 2013
  • 2 replies
  • 1390 views
We are coming across the following issue:
  1. A new lead, lets call him John, is created as a result of completing a form.
  2. When that form is completed a new known lead, John, is created if the lead does not exists yet.
  3. A field on the form, Requirements, is updated everytime the form is completed (no blocking updates)
  4. A smart campaign is then triggered to create a SF task, based on the creation of a new lead, the filling out of the form, or the changing of the field Requirements.
  5. A second duplicate lead for John is then created, we do not know how though because the Merge Lead activity record does not specify (or does it?).
  6. The leads are then merged, which then triggers the smart campaign, because a new lead has been created and the Requirements field has been changed from NULL to having a value, even though it is the exact same value as before.
How can the smart campaign be avoided from triggering twice for the same Requirements value?

Keep in mind the smart campaign must run every time a lead qualifies as the Requirements field can realistically change for a single lead.  Changing the qualification rules to only run once here will not satisfy the required logic.  The goal is to create a new SF task that includes the Requirements value in the task description, everytime it changes.
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by
You can exclude merged leads by adding a Not Lead was Created filter with the "Min. Number of Times: 2" constraint.

2 replies

A
Anonymous
Accepted solution
January 23, 2013
You can exclude merged leads by adding a Not Lead was Created filter with the "Min. Number of Times: 2" constraint.
A
Anonymous
January 23, 2013
Great simple solution Elliott, thanks for sharing.  

This does solve the above problem, where the field value is populated on the initial lead creation.  However if the field is null after initial lead creation, then populated on the second lead creation, the campaign would not trigger.

I'll modify this solution then with a "Not Data Value Was Changed" with the "Min. Number of Times: 2" constraint.
Terms & ConditionsAccessibility statement

Loading footer...