# Creating Segments and Workflows based on Campaign-Level actions

**URL:** <https://community.hubspot.com/t/creating-segments-and-workflows-based-on-campaign-level-actions/155144>\
**Category:** HubSpot Ideas\
**Tags:** workflows, marketing-email\
**Created:** [August 3, 2026, 8:51pm UTC](https://community.hubspot.com/t/creating-segments-and-workflows-based-on-campaign-level-actions/155144 "2026-08-03T20:51:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dcroatt](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@dcroatt](https://community.hubspot.com/u/dcroatt)\
**Post date:** [August 3, 2026, 8:51pm UTC](https://community.hubspot.com/t/creating-segments-and-workflows-based-on-campaign-level-actions/155144/1 "2026-08-03T20:51:22Z")

</div>

**Allow campaign-level email-open segments**  
We need to build a contact segment of anyone who opened **any marketing email associated with a specific campaign**.

Today, the marketing-email activity filter requires selecting individual emails one at a time. For campaigns with 50+ sends, this is not practical and it does not automatically include future campaign emails.

Please add either:

1. a campaign-level email activity filter: “Opened any email associated with campaign,” or
2. an option to filter email activity by campaign association or email-name pattern.

This would let marketers create accurate, dynamic follow-up audiences without maintaining dozens of individual email conditions.

---

<div class="post-metadata">

**Author:** ![EgeTheCEO](https://avatars.discourse-cdn.com/v4/letter/e/ccd318/32.png) [@EgeTheCEO](https://community.hubspot.com/u/EgeTheCEO)\
**Post date:** [August 4, 2026, 10:12pm UTC](https://community.hubspot.com/t/creating-segments-and-workflows-based-on-campaign-level-actions/155144/2 "2026-08-04T22:12:51Z")

</div>

Campaign is the right durable unit here. I’d make the filter semantics association-based rather than name-based: contact had marketing-email event X, where X’s asset is associated with Campaign Y, within a defined time window. That would automatically include future sends while preserving the exact email event as drill-down evidence. The same campaign-scoped event primitive should be usable by segments, workflow enrollment, and reporting; otherwise teams will still rebuild three slightly different definitions. One important control is association history—if an email is added to or removed from a campaign later, HubSpot should make clear whether past events are reclassified or evaluated using the association that existed when the event occurred. I’m Ege in SF; happy to compare segment-governance edge cases if useful.