“Choose how often you hear from us” sounds helpful. But if the linked page only offers newsletter topics, the email promises a control the reader cannot use. Even a well-designed preference page can disappoint when its labels and sending rules mean different things.
Start in Migma by writing an invitation that matches the choices the destination actually supports. Review the email, preference page, saved state, and later sending behavior as one journey, with the platform owner responsible for the rules.
This guide is published by Migma. It offers copy examples and a review method for marketing teams, including those using Loops. It does not claim that Migma creates or changes a subscriber’s Loops preference settings.
Name the choice before writing the invitation
A preference page may offer topics, mailing lists, frequency settings, or a pause. Those are possible designs, not a standard set of controls available in every implementation.
Loops’ preference-center guide explains that each choice needs a corresponding sending rule. A frequency option needs scheduling behavior; a topic choice needs an audience rule. The copy should describe the implemented result rather than an imagined ideal page.
Ask the sending owner to list the currently supported choices in plain language. “Receive product-update emails” is a topic decision. “Receive a weekly digest” is a format and cadence promise. “Stop promotional emails for a month” is a time-based rule that needs its own implementation.
Do not treat fewer topics as a guaranteed frequency reduction. One topic may generate several messages, while another may rarely produce an update. Use wording that accurately describes the choice the reader can make.
Review four pieces of copy together
| Surface | What the reader needs to understand | Review question |
|---|---|---|
| Email invitation | Which choices the page offers | Does the button promise a supported action? |
| Preference label | What a selected topic or setting means | Would a subscriber understand the future messages? |
| Save confirmation | Whether the change was accepted | Does the wording match the actual saved result? |
| Later email | Why this message still qualifies | Did the current preference affect selection? |
The table is a creative review aid. It does not establish how a particular sending platform stores or enforces the state. Have the platform owner demonstrate that behavior before approving a broad promise.
Keep account actions distinct from marketing choices. Someone leaving a newsletter should not be told that their account is closed when that is not what happened. Equally, “unsubscribe from everything” may be unclear if account-critical messages follow separate rules. Use the wording approved for the actual supported scope.
Draft an invitation in Migma
Review brand context, then give Migma the real choice list and destination description. Include the words the draft must avoid until their behavior is verified.
A useful brief could say: “Create a short footer invitation to choose newsletter topics. The destination supports product news and practical guides. It does not support frequency selection or a temporary pause. Keep the unsubscribe route clear.”
Example when only topics are supported
Invitation: Want to choose your newsletter topics? Review the available options and save the ones you want to receive.
Action: Choose newsletter topics.
This wording does not promise a weekly schedule or fewer messages. It asks for a specific supported action. The destination still needs to use understandable labels and confirm the saved choice accurately.
Example when a weekly digest is actually implemented
Invitation: Prefer a weekly digest? Review the available email options and choose the format that suits you.
Action: Review email options.
Use this version only when the digest and its selection rule exist. A checkbox labelled “weekly” is not enough if the underlying system continues selecting the person for every individual campaign.
These examples are original suggestions, not descriptions of controls guaranteed in Loops or Migma. Adapt them to the actual destination rather than copying them into every footer.
Keep the unsubscribe route clear
Preferences can help someone narrow what they receive, but they should not become an obstacle to stopping the messages covered by an unsubscribe request. The Loops guide recommends an accessible unsubscribe option without requiring a survey or unrelated preference selection first.
Review the visual hierarchy with that in mind. A prominent preference invitation and a hard-to-find unsubscribe route can create confusion even if both links technically work. Clear wording and readable presentation are part of a useful email footer.
Do not claim a preference change is saved when the page returns an error or leaves the state uncertain. The responsible owner should provide accurate success and failure wording. Avoid a reassuring email statement that conceals an unresolved platform problem.
Test the journey after handoff
Run Email Preflight in Migma for relevant layout, links, writing, and delivery-risk checks. It cannot verify preference persistence, future audience rules, or inbox placement.
Inspect the final platform version and use the platform’s supported test workflow to review the contact-specific destination. Confirm that the intended choices appear and that an accepted change affects subsequent selection as the owner expects.
Include a subscriber who removes one topic, someone who stops the supported marketing messages, and a later scheduled campaign. Ask how current preferences are reconciled if an older import or queued audience still contains different values. These are acceptance questions for the platform owner, not a request to contact real recipients without authorization.
Approve the promise the reader will experience
Read the invitation and the saved confirmation as if you knew nothing about the implementation. Both should describe the same supported choice. Keep an owner for future changes so a new preference-page design does not leave old email copy making the wrong promise.
Use Migma to make that invitation clear and easy to find. Accurate preference copy gives readers useful control only when the destination and later sending behavior support what the email says.
Frequently Asked Questions
What should a preference-center link promise?
Describe the choices the destination actually supports. If the page offers topic selection, say so. Do not promise weekly delivery or a temporary pause unless the sending system implements that choice.
Are fewer topics and fewer emails the same promise?
No. A topic choice controls subject matter, while frequency depends on scheduling and audience rules. Review the actual result before claiming that selecting one topic guarantees a particular cadence.
Should preference selection be required before unsubscribing?
Keep the supported unsubscribe route accessible and clear. Offer preferences as useful options without making the reader complete an unrelated survey or selection before stopping the messages covered by their request.
Can Migma change a subscriber’s Loops preferences?
The workflow here uses Migma to prepare and review the email invitation. The Loops and application owners must verify the contact-specific destination, saved choices, and how those choices affect later sends.