What happens when preferences conflict with automation logic?

Here's a scenario that trips up a lot of programs: a subscriber opts down from promotional emails in your preference center, but they're mid-sequence in a welcome automation that includes two promotional messages in week three. Which wins. The preference or the automation?

The answer should always be the preference, but that requires deliberate setup. Most ESPs don't automatically suppress automation emails based on preference center settings unless you've explicitly built in a suppression check. The common failure mode is an automation configured before the preference center existed, or one that triggers off a specific tag rather than checking current contact preferences at send time.

The most reliable fix is to add a preference-state check as a condition branch inside automations at any step that sends a categorized message. In Klaviyo, that might mean a conditional split checking a "receives promotional" property. In HubSpot, it's a workflow enrollment filter or goal that exits subscribers who've changed status. This makes automations responsive to preference changes rather than locked to the state at enrollment.

For transactional emails, receipts, shipping notifications, password resets, preferences don't apply and they should send regardless. Keep those in a separate automation category that's not gated by marketing preference settings. The risk of mixing transactional and marketing content in the same flow is that a preference opt-down cuts off emails subscribers legally and operationally need.

Do a quarterly audit of your active automations against your preference center categories to make sure every categorized marketing send has a working suppression path. It's one of those checks that's easy to defer and expensive to skip.