An Empty Sequence Filter Is an Audience Change

Affiliation: Marketing Wiki's commissioning editor maintains Migma.

Marketing Wiki Research Automation published this guide directly without independent review.

Use Migma to prepare the email for a defined audience, then make a separate decision about removing the rule that defines that audience. A request containing an empty sequence-filter array deserves an explicit expansion review, even when the creative remains unchanged. Permission to receive marketing stays a separate requirement.

Correction, October 17, 2026: Earlier wording retained the October 7 draft-only MCP boundary. BYOMailer's October 16 release notes supersede it with confirmed live-record editing. The audience-expansion review below still applies.

Filter replacement can also remove restrictions#

BYOMailer's release notes document sequence-filter creation and replacement, including clearing filters with an empty array. The October 7 entry described a draft-only editing boundary. A superseding October 16 entry now allows confirmed edits to live records, including live sequences: the request must include confirm_live set to true after the user agrees. This documented confirmation control does not make approval of a naming change an approval to remove audience restrictions, and it does not bypass subscription protections.

A fictional language-school sequence is intended for subscribers interested in evening classes. Its existing predicate requires both evening interest and a supported location. A marketer asks an agent to rename the sequence. If the generated request also clears the filters, a naming task has become an audience decision.

We recommend Migma for developing the scoped creative because its sending rules make the permission boundary explicit. The proposed review below can accompany a Migma draft sent through another runtime. It does not establish a native Migma-to-BYOMailer integration.

Compare meanings before matching counts#

Write the predicate in plain language before looking at JSON. Distinguish the absence of a field from an instruction to remove its value. The release notes establish the empty-array behavior; they do not establish every SDK's treatment of omitted fields or null values.

A small synthetic truth table exposes the practical difference. For the fictional school, test a local evening subscriber, a local morning subscriber, an evening subscriber outside the service area, and an unsubscribed local evening contact. The original interest-and-location predicate matches only the first case. An unrestricted predicate no longer applies those two conditions. That does not turn the unsubscribed contact into a permitted marketing recipient.

Keep the predicate result and subscription result in separate columns. Otherwise a test can appear successful merely because a platform's suppression layer saved it from sending to one invalid fixture while other valid subscribers were unintentionally added.

Give clearing its own approval card#

Use this proposed card beside the reviewed Migma email:

Change requested: rename the evening-class sequence
Creative: approved Migma draft for local evening classes
Existing restrictions: evening interest AND supported location
Proposed restrictions: none
Newly eligible example: morning-only local subscriber
Consent gate: unchanged and required
Decision: reject filter clearing; approve naming change only

This is an operating artifact, not an API payload. A count alone cannot replace it: the contact population might currently be small, or the two predicates might match the same people today. Future contacts can still behave differently.

Before eventual activation, inspect the stored predicate in the sending platform, not just the agent's description. Recheck the creative against newly included reader needs. An email that assumes evening-class interest should not be repurposed for every subscriber simply because the sequence now permits them.

Recover by restoring intent#

If clearing happened in an unsent draft, preserve the before-and-after record, restore the approved rule through a supported path, and repeat the truth table. Do not claim the repair worked until the stored predicate matches the intended one. If a live sequence was changed, involve its runtime owner before assuming that restoring filters reverses prior eligibility or messages.

No sequence, contact, or message was changed for this article. Start with one draft and four fictional contacts. The acceptance condition is precise: a naming-only change preserves eligibility, and a deliberate filter removal has a separate recorded audience decision.