Target the right subscribers

A B2B supplier of industrial fasteners sends the same monthly price list to every contact it has ever collected — hardware retailers who order every month, a one-time enquiry from years ago, a distributor who switched to a rival. Most of that list has no reason to open a fastener price list this month, and every uninterested recipient who ignores enough emails drags down how the domain looks to mailbox providers over time.

List segmentation lets the supplier build an audience from what it actually knows about each contact — order frequency, product category, last engagement date — combining conditions with AND/OR logic rather than sending to everyone by default. A segment built on active buyers in the fastener category recalculates on its own as new orders come in, so the price list reaches people it is actually relevant to, not a static list frozen at the moment it was first built.

A segment is only as good as the data behind it, and the biggest practical risk is a rule that is broader than intended — an unbounded condition, or an OR chained onto an AND without enough thought, that ends up matching the entire contact table instead of the intended subset. Because a send is irreversible once confirmed, the segment builder shows the actual matching count before saving, and that number is worth reading carefully rather than assuming the logic did what it looked like it should on the screen.

Segmentation on purchase behaviour or product category depends on a connected store, booking system or CRM actually reporting that data accurately — Patri reads what it is given, it does not infer buying intent from nowhere. A supplier without a connected order system can still segment on tags, engagement history and manually recorded attributes, but the richer, purchase-based segments described here need that underlying data source wired up first.

Segmentation also interacts directly with suppression: a dynamic segment recalculates from the live contact table, and anyone who has unsubscribed, hard-bounced or complained is excluded from that table by the suppression system before a segment ever sees them, not filtered out afterwards as an extra step. This means a well-built segment inherits clean list hygiene automatically, but it also means segmentation alone cannot rescue a list that was built on bought or scraped contacts in the first place — no filtering logic turns an unconsented address into a safe one to email.