Using the Reason constraint on the Data Value Changed filter | Community
Skip to main content
Jamie-Carey
Level 4
December 30, 2014

Using the Reason constraint on the Data Value Changed filter

  • December 30, 2014
  • 7 replies
  • 3001 views

I'm trying to find out who had a lead score change from a specific smart campaign - would I use data value changed with a reason or some other filter?

The Data Value Changed filter with the Reason constraint is appropriate for finding leads that had their Lead Score changed by a campaign.


This screen shot shows an example of how you might set this up.

The list below show a few of the values you may see in the Reason field. If you know the exact phrase you are looking for, use the "is" operator. For example, "Changed by Smart Campaign Contact Us." If you don't know the exact value, try using the operator "starts with." 

  • Synched from salesforce.com
  • Changed by Smart Campaign
  • System flow action
  • System action reset
  • Form fill-out
  • SOAP API
  • Manual lead edit
  • Munchkin API
  • Import/merge into list

The Reason filter constraint is available in these filters:

  • Data Value Changed
  • Lead Partition Changed
  • Progression Status was Changed
  • Revenue Stage was Changed
  • Not Data Value Changed
  • Not Lead Partition Changed
  • Not Progression Status was Changed
  • Not Revenue Stage was Changed
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

7 replies

Adam_Benitez1
Level 3
February 17, 2016

Any idea what the reason would be for an "Activity Type" of "Merge Leads"? Thanks.

Adobe Employee
February 17, 2016

Hi Adam,

This can happen if leads are merged. For example, let's say you merged two leads because they have the same email address but one has the first name Fred and the other has the first name Frederick. One of those two values would be chosen as the winner so there would be an Data Value Change for First Name logged in the activity log. The reason for this change would be "Merge Leads" because it happened as the result of a merge.

Adam_Benitez1
Level 3
February 23, 2016

Sorry, Mel. I wasn't very clear. I meant what is the "Data Value Change" Add Constraint" Reason" I would fill in if I'm trying to exclude or include Merged Leads.

July 29, 2016

Why might I not see this constraint (REASON) on the Data Value Changed filter? It appears to be missing for me. Thanks.

Jamie-Carey
Level 4
July 29, 2016

hey Rob, can you add a screenshot of what you do see?

Level 2
October 4, 2016

I'm also trying to create a smart list that excludes those leads who were merged, like @Adam Benitez​. Does anyone have any idea how to exclude records that may have been merged? Thanks!

Tim_Alexander1
Level 2
December 8, 2017

I have no clue why no reasons are showing up, but I'd like to see if constraints would be the right way to trigger a smart campaign based on anything other than a change that occurred based on an update from the API.

If a change happens because of an update from the API, fire one set of campaigns. If not, use different ones. Is this possible?