Using the Reason constraint on the Data Value Changed filter

Document created by Jamie Carey on Dec 30, 2014Last modified by 7c0530b8c4efdd5734ac0e37c02a18c0a98056cf on Jun 25, 2015
Version 3Show Document
  • View in full screen mode

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
  • Changed by Smart Campaign
  • System flow action
  • System action reset
  • Form fill-out
  • 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