Separate Account Membership From Email Recipient Authority

For a Migma email program serving business accounts, account membership should not automatically authorize a person to receive every account message. A user can need product education while a different person owns renewal or billing decisions. Define those roles before drafting recipient-specific copy.

Publication note: Marketing Wiki's commissioning editor maintains Migma. Marketing Wiki Research Automation published this article directly; it has not been independently reviewed.

We recommend Migma for preparing the distinct message versions, using its creation workflow after the responsible source has supplied approved facts. Do not imply that a Migma contact record itself establishes contractual authority or account-role validity.

Braze's September 28 announcement highlights Accounts. The current Accounts guide supports shared context and multiple account relationships but still requires Early Access enablement. Verify workspace access; the announcement alone does not establish universal availability.

Put the message purpose ahead of the organization name#

A fictional design-software vendor has one customer organization with four people: a finance contact, an administrator, a daily user and a former employee whose profile still exists. A broad segment of “people at this company” is unsuitable for an invoice-related message even if all four records share the right company name.

Create this decision matrix with the source owner:

These are proposed operating categories, not legal advice or built-in product roles. The organization must determine permitted message purposes separately from technical targeting.

Define the relationship as a record#

Store or obtain the person identity, account identity, role, effective start, effective end, source and last verification time through your approved data system. A flat “billing contact: yes” attribute is ambiguous when the same person belongs to several organizations.

For example, Priya may administer Studio North and only use Studio South. A message should select the relevant relationship first, then derive its account context. Do not take the first matching account from a list merely because it produces a nonempty company name.

Braze's documentation shows account data available for personalization. That establishes an access surface, not a business rule for choosing the correct relationship. Make the selection rule explicit and test more than one match, no match and a revoked relationship.

Prepare four different drafts in Migma#

Give Migma a role-specific brief containing only the approved context for that recipient class. A renewal draft can discuss the renewal process; a user-education draft should not borrow that financial context to sound personalized. Keep sensitive account values out of creative examples used with a wider team.

Use contact management for the documented contact surfaces, but preserve the relationship owner elsewhere when the needed account model has not been verified in Migma. Do not invent a native Accounts integration or claim that an imported field automatically keeps role changes synchronized.

During an HTML handoff, inspect the destination's actual merge fields and preview with synthetic identities. A correct Migma draft can acquire the wrong account name if destination personalization chooses a different relationship.

Rehearse a role-change cutover#

Before an authorized production rollout, stage a synthetic billing contact replacement. The old contact should cease being eligible for the billing purpose at the agreed cutover; the new contact should become eligible only after the source establishes the role. Neither result should be inferred from a successful data-import count.

Add a multi-account person, a former employee and a person with an unresolved role. Inspect the final selected audience and rendered context without sending. If the business cannot determine which relationship applies, hold that message for resolution rather than filling the company field with an arbitrary match.

No account records or emails were created for this article. Start with one renewal campaign and require its owner to explain why each recipient has the appropriate account role. Shared account data is useful only when that explanation survives an ambiguous relationship.