This content has been marked as final. Show 5 replies
I would suggest scoring off the trigger "Added to List." This will isolate the records in question, as opposed to records that are created via forms and/or in your CRM (if you're integrated), which means better performance on the system.
This will also allow you more flexibility around the scoring rules, as well as be able to troubleshoot more efficiently should you need to do so.
I recommend using the trigger "data value changes" and selecting the specific field that you want to score on. This will capture leads that come in via form completions, CRM sync, and list uploads.
I caution against using "added to list" trigger. If you have a list in a program and then clone the list, that trigger will activate and re score all those leads.
Jessica, that's really interesting - I would have never thought of that, but your reasoning is sound; if the same leads are on two different lists it the scoring will run for each of them, separately is what you're saying, right?
Ah! I didn't even think of the cloning issue. Good catch - always better safe than sorry!
If the flow rules are set to allow the leads to run through every time, cloning the list will activate the scoring campaign again.
But if the flow rules are set to run leads through only once, then cloning the list will not cause the problem.
I still recommend using the trigger "data value changes" and selecting the specific field.