Data Value Change trigger vs. net new lead

[JD_Nelson]

I have a trigger to run every time a field is changed, but I'm wondering if when the initial lead is created if that's not triggering because it didn't "change" it just "was".  If so, how do you recommend I set my triggers to capture both a 'data value change' as well as a data value set?

[Anonymous · Accepted solution]

Hi JD,

For the lead scoring campaigns I have set up as triggers, I normally listen for data value changes OR new lead is created.  When you have two triggers in the smart list of a campaign, they act as or statements.  This should capture net new leads and existing leads where data changes.

Thank you,

Courtney

[JD_Nelson]

if you do 'lead is created' how would you limit it to a certain field? I'm

trying to track UTMs and not every lead will have them, so it would be

overload if we ran it through the UTM track knowing there weren't any

values...

JD Nelson //

MindjetDemand Generation Manager // office 415.229.4236 <415.229.4228>

1160 Battery Street East, 4th Floor, San Francisco, CA 94111

LinkedIn <https://www.linkedin.com/pub/jeff-jd-nelson/10/379/823>

On Tue, Jul 21, 2015 at 3:12 PM, Courtney Marshall <

[Kenny_Elkington]

Hi JD,

You'll want to apply both triggers a Courtney noted, and then add the attribute filter for the field you're looking for to filter only to new leads which have the desired value for that field.

[JD_Nelson]

will this work?

[Elliott_Lowe1]

Those triggers/filters will work.

[Josh_Hill13]

Just remember that when a Lead is Created, the system does not register the new field data as a Change Data Value, so those two triggers are needed in this case.