How do suppressions work with triggers?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

Here's a situation that trips people up all the time. A contact unsubscribes from your welcome flow, but then they sign up for a webinar and your webinar reminder sequence fires anyway. Was that supposed to happen? Should it have?

That's the suppression question in a nutshell. Suppressions tell your automation what not to do, even when a trigger condition is technically met.

The key thing most ESP docs gloss over is when the suppression check runs. Ideally it happens at the moment of enrollment, not just at send time. If someone is on a global suppression list and a trigger fires, the automation shouldn't even start for that contact. Some platforms check suppressions only right before the email goes out, which means a suppressed contact can sit inside a flow for days before being filtered out. That's a gap worth understanding in whatever tool you're using.

There are a few different suppression scopes you'll typically encounter:

  • Global suppressions cover unsubscribes, hard bounces, and spam complaint records. These contacts should never receive any marketing automation, full stop. Klaviyo, ActiveCampaign, and most serious platforms apply these globally by default so you don't have to think about it.
  • Flow-specific suppressions are rules you set yourself. Recent purchasers, VIP contacts on a different track, or people already mid-way through a competing sequence. You're saying "skip this person for this particular flow" without removing them from everything.
  • Temporary suppressions create a cooldown. After a contact gets one email, you might suppress them from other triggers for 48 hours to avoid pile-on messaging.
  • Segment-based suppressions exclude entire groups, like employees or test accounts, from automations that were built for real customers.

The practical question is usually about scope. If someone unsubscribes from one flow, should that suppress them everywhere? For marketing triggers, yes, a global unsubscribe should block all of them. But transactional triggers (password resets, order confirmations) are a different story. Those can still fire even for unsubscribed contacts because they're not marketing messages.

Worth double-checking in your ESP: does an unsubscribe from one list or flow set a global flag, or does it only suppress that specific sequence? The answer varies by platform and by how your account is configured. Getting this wrong means either emailing people who opted out (a compliance problem) or silencing people who only wanted off one list (a missed opportunity).

If you're setting up automation and want a second pair of eyes, our SOS hotline is free and we won't pitch you anything.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Map out my suppression logic

I'm setting up automation in your ESP and want to get suppressions right. For each type of suppression below, tell me: (1) whether it should block enrollment or just the send, (2) whether it should be global or flow-specific, and (3) the risk of getting it wrong. My suppression types: [list them, e.g. unsubscribes, recent purchasers, cooling-off contacts, test accounts].

Edit the yellow boxes, then send to the AI of your choice.