Skip to main content
Level 2
August 31, 2026

Improve Efficiency and Process for Unapproving Segmentations

  • August 31, 2026
  • 2 replies
  • 19 views

Managing and retiring segmentations in Marketo can be an unnecessarily time-consuming process.

Today, when a segmentation needs to be unapproved, archived, or deleted, administrators must manually remove every dependency listed in the Used By section. This often requires opening each individual asset and disconnecting the segmentation one at a time.

For email assets, the process can be even more complex. Administrators may need to remove dynamic content, create drafts, reapprove assets, and perform additional cleanup before the segmentation can be detached. In larger instances with many programs and emails, this can become a significant administrative burden.

My suggestion is to enhance the existing Used By functionality. Since Marketo can already identify every asset that references a segmentation, administrators should be able to select some or all dependencies and authorize Marketo to remove those references automatically.

A potential solution would allow administrators to:

  • View all segmentation dependencies in a single location.
  • Select some or all dependencies for removal.
  • Confirm the action through a warning and approval dialog.
  • Have Marketo automatically remove the segmentation references from the selected assets.
  • Proceed directly with unapproving, archiving, or deleting the segmentation.

The core idea is simple: if Marketo can identify every dependency through the Used By feature, administrators should have the option to remove those dependencies in bulk rather than manually updating each asset one by one.

Business Impact

  • Reduces administrative overhead and cleanup effort.
  • Simplifies segmentation governance and lifecycle management.
  • Makes it easier to retire outdated or unused segmentations.
  • Helps organizations stay below segmentation limits.
  • Reduces the risk of missing dependencies during manual cleanup.
  • Saves significant time in larger Marketo instances with many programs and emails.

Example

If a segmentation is referenced by 50 emails and 10 programs, administrators must currently locate and update those assets individually before the segmentation can be unapproved. Since Marketo already knows exactly where those references exist through the Used By view, providing a bulk removal option would greatly improve efficiency while still maintaining administrator oversight through confirmation prompts and permissions.

2 replies

sandy_logitech
User Group Leader
User Group Leader
September 1, 2026

You should be specific about what “removing a dependency” entails. Restoring default content in assets is pretty brute-force. What about segmentations used in Smart Lists - what happens to Any/All/Advanced Filters? Segmentations used in Velocity tokens? 

Level 2
September 1, 2026

In this thinking, none of that matters, making the process of easier is what matters. If you want to remove or archive/unapprove a segmentation only, it should be simpler to do.