Segmentation queries make it possible to manage dynamic lists of users.
Complicated segmentation queries may cause various segmentation-related elements of Iterable's user interface—for example, campaign recipient count—to load slowly (or not at all). This document provides tips to help prevent this from happening.
Limit Regular Expression Usage #
Regular expressions are a powerful segmentation tool, but use them only where necessary—to express a complex segmentation query, or to condense and optimize a group of related queries.
Otherwise, try to express the query without regular expressions. For example, a segmentation query such as email Matches Regex .*example.com
can be represented without a regular expression as email Contains example.com
.
Avoid Repetitive Expressions #
Simplify segmentation queries that contain multiple repetitions of a single rule.
For example, instead of segmenting on email Contains example.com
OR email Contains example2.com
OR email Contains example3.com
, use a regular expression query such as: email Matches Regex .*example.com|.*example2.com|.*example3.com
.
Be Aware of Joined Lists #
A campaign's recipient list may comprise multiple segmentation and suppression lists.
If the above suggestions don't help, make sure to optimize all lists associated with your campaign. Although the segmentation query associated with any particular list may look simple, combining them can increase the overall complexity.
Conclusion #
If you've tried these suggestions but still see slow-loading segmentation indicators in Iterable's user interface, please reach out to your customer success manager for help.
Comments
0 comments
Article is closed for comments.