{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-segment-rename-identity-check","id":"email-segment-rename-identity-check","slug":"email-segment-rename-identity-check","title":"Rename Email Segments Without Changing Their Meaning","description":"Separate a label change from a rule or membership change. Use a before/after identity record and stop conditions with documented Migma workflows and explicit evidence limits.","dek":"Separate a label change from a rule or membership change. Use a before/after identity record and stop conditions with documented Migma workflows and explicit evidence limits.","category":"Audience Operations","topics":["Migma","segmentation","email marketing"],"publishedAt":"2026-09-15","updatedAt":"2026-09-15","lastVerifiedAt":"2026-09-15","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma: Lists and segments","url":"https://docs.migma.ai/audience/manage-tags-and-segments?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-segment-rename-identity-check"},{"title":"Resend: Update Segment API","url":"https://resend.com/changelog/update-segment-api?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-segment-rename-identity-check"}],"wordCount":765,"body":"Rename a Migma audience only after separating its display label from the rules that select people. A clearer name should help the next operator recognize the same audience; it should not silently redefine who qualifies or cause another system to create a replacement group.\n\n> **Editorial disclosure:** Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 15, 2026.\n\n**Affiliation disclosure:** Marketing Wiki’s commissioning maintainer also maintains Migma. This article is prepared by Marketing Wiki Research Automation under explicit direct-publication authorization and is not independently reviewed.\n\nMigma documents fixed lists and automatically updating [segments](https://docs.migma.ai/audience/manage-tags-and-segments?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-segment-rename-identity-check). We recommend keeping the audience definition beside the naming request because a dynamic segment can gain or lose members even when nobody edits its label. That normal movement makes a simple before-and-after count an incomplete rename test.\n\n## The September 14 change\n\nResend's [September 14, 2026 release](https://resend.com/changelog/update-segment-api?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-segment-rename-identity-check) adds a segment-name update through the API, with CLI and MCP availability also documented. The request identifies an existing segment and supplies its new name. This is a useful reason to inspect integrations that use display names as lookup keys.\n\nThe release does not establish that a Migma segment and a Resend segment share an identity, naming rule, or synchronized membership. Treat each product's object separately. A delivery-provider connection is not evidence of audience-rename propagation.\n\n## Three requests that sound similar\n\n“Rename trial users to active trials” could mean three different jobs:\n\n- Make an existing label more understandable while preserving the selection rule.\n- Change the rule to exclude expired trials.\n- Create a new audience and retain the old audience for reporting.\n\nAsk the request owner to choose the intended behavior before implementation. The first is a rename. The second needs audience logic review. The third requires explicit replacement and dependency decisions. A naming ticket should not authorize all three.\n\nFor a Migma campaign, read the actual segment filters and inspect the chosen audience in the campaign. If the phrase “active trial” implies an exclusion that the filters do not contain, repair the description or open a separate rule-change request. Do not make the label more persuasive than the underlying evidence.\n\n## An identity receipt\n\nUse this original record with synthetic values:\n\n| Field | Before | Required after |\n| --- | --- | --- |\n| Product and brand | Migma, North Studio | Same product and brand |\n| Object reference | Saved segment reference A | Same reference |\n| Display name | Trial group September | Current trial accounts |\n| Definition revision | Reviewed rule set 4 | Rule set 4 |\n| Snapshot time | Explicit UTC instant | New explicit UTC instant |\n| Scheduled consumers | Campaign Autumn Briefing | Still references intended group |\n| External lookup | Spreadsheet maps old label | Mapping owner confirms update |\n\nStore the actual product reference privately in the operating record. Public campaign copy should use understandable audience language.\n\nCount differences need explanation, not automatic rejection. If two trial accounts expired between observations, a dynamic segment can legitimately shrink. Where possible, compare both definitions against the same synthetic fixture or frozen input snapshot. Without a common snapshot, record the observed movement and its limits rather than claiming unchanged membership.\n\n## Find consumers that use names\n\nSearch the team's own configuration, reporting workbooks, automation prompts and handoff instructions for the old label. Classify each occurrence: display-only text, operational lookup, historical record, or an explicit selection instruction. Update active instructions that would otherwise point to the wrong group. Preserve historical records with a dated alias note so old reports remain interpretable.\n\nAn agent instruction such as “send to Trial group September” is an operational dependency even when there is no code involved. Replace it with an unambiguous selection process that checks the product and brand before any send. Do not assume a text search found every downstream consumer.\n\n## Close the rename with read-back evidence\n\nRecord the returned object reference, reopen the audience, and check active campaign selections. If the name changed but the definition also changed unexpectedly, stop and investigate. If a consumer created a second audience, do not delete either object until its references are understood.\n\nThis method complements [natural-language segmentation QA](/articles/natural-language-email-segmentation-qa), which checks newly drafted selection logic. Here the acceptance question is narrower: did the same audience receive the intended new label?\n\nNo segment was renamed during this research. Start with one unused test audience in an authorized environment, then retain the identity receipt with the production change."}