Ensuring all smart list operators function properly without limitations

[Anonymous]

We've used "Contains" operator to query smart list instead of using the stragiht forward "is" operator and have begun to see problematic performance. We were advised by Marketo that using "contains" opens up the query and lengthens Marketo system process time and is more prone to error. Can we ensure all operators will work properly otherwise there is no use in offering "contains" if we have to use "Is" as a work-around.

[Josh_Hill13]

Cynthia,

using a more open ended operator like CONTAINS does take longer to process than an exact match IS.

The reason you probably have more errors is because CONTAINS often brings up possibilities that the user had not considered, such as "intern" vs "international". The only other issue is more of a trigger problem than an operator - too many of these tend to create race conditions, so you need to be careful with them.