This content has been marked as final. Show 5 replies
If you have a unique field that always indicates that the record in question is not a converted record but is a duplicate of a record that did convert, you could use that field as an exclusion in your smart list.
E.g., Duplicate of Converted Lead = False
I suppose Justin's idea would work, but I'm wondering if you meant something else by your question.
If you say "Show me a list of leads with X criteia that have Converted=True" then you should have the correct list. why would you need to do a separate exclusion of the non converted leads?
I assume you are leaving the SFDC Lead records alone because there is some sort of User record type related to your product? If so, you should consider a method of identifying those people separately via a record type or other flag.
Yes, looking at leads where converted = true would work! That would be also known as the simpler way :)
Sorry if I didn't present this as clearly as I could have. I have two lists to cross reference basically - both of these lists already exist:
List A = Converted status is "true"
List B = All lead records that have duplicate email field values (dupes). Converted status could be "true" or "false".
The additional logic I need will look at leads in list A to see if they have duplicate lead records in list B (using the email field to identify matches). This resulting list would be used as a negative list.
I think Justin's first response was on the right track. I just don't know how to look up dupes (email address) against an existing smart list.
e.g. "Do leads in this list have any additional lead records with matching email address?"