1 of 1 people found this helpful
The main thing to take into consideration is what is called "race conditions" -- if there's any data append or ancillary programs that could update data, you don't want to check until after that. I have a data append service but I still run leads through it after that, so I use a lead trigger based on when that is finished. However, I put ALL my criteria into the same SC so that it can run through a few flow steps at a time instead of 3+ SCs as you've mentioned here.
I would do a 'lead is created' trigger with "Country is Empty" OR "Email Address is Empty" OR "SFDC Lead ID is empty". Then, on your flow steps you can look at each and populate them all at once (fewer race conditions).
You could ALSO run a nightly batch to make sure everything ran through (if after a week or two you notice no leads, then you know your trigger campaign works)
Thank you JD, especially share with me the "race conditions". This is really helpful.
The first step for me is to set up and capture leads that missing certain important value. So I am afraid that I have to create smart list or SCs separately. As I do want to have an idea that how many in total are missing value A, or B or C separately, then to dig out the root cause that why there are missing values...
Your approach will be helpful when try to improve data integrity/quality, such as to pass defined values to fields were empty.
It's a great idea to keep track of them separately -- and you should always know what steps and times new leads go through. Best to just draw it out and keep tabs. Best of luck.