Choose a Holiday Audience Before Choosing a Language

In Migma, choose who a holiday email is relevant to before choosing the language of its creative. English does not select a country, a country does not prove personal observance, and a timezone does not establish that a seasonal promotion fits a subscriber. Treat those as separate decisions.

Disclosure: Marketing Wiki's commissioning editor maintains Migma. Marketing Wiki Research Automation prepared this article for direct publication without independent review. The routing cases are fictional and were checked offline; no subscriber data or live Migma segment was tested.

Migma's audience overview treats country, language, preferences, and suppression as audience concerns. Its October 1 Thanksgiving editorial is a timely planning lead. The editorial date is not evidence that one Thanksgiving date applies to the whole list. This guide addresses that audience decision before the existing translation-review workflow begins.

One holiday name, two calendar entries#

The Canada Revenue Agency's 2026 recognized-holiday page, with page details dated January 6, lists Thanksgiving on Monday, October 12. Its scope concerns CRA-recognized holidays and due-date treatment; do not generalize it to every provincial employment rule.

The US Office of Personnel Management's 2026 federal calendar lists Thanksgiving on Thursday, November 26. That calendar concerns federal employees. Neither government page establishes what an individual subscriber celebrates or when your store's promotion should run.

Use the official dates as calendar evidence, then have the campaign owner approve the commercial and audience relevance. A Canadian English-language campaign and a US English-language campaign can need different dates even though their language fields match. A French-language version does not automatically move the campaign to a different holiday calendar.

Make relevance an explicit input#

Decide what makes the message appropriate: a declared market for the campaign, an established customer relationship, and the subscriber's applicable preferences. Use data you are authorized to use and whose meaning is known. Do not infer personal observance from a name, email domain, or language. A timezone may reflect travel or a configured preference rather than the market the campaign serves.

Unknown country should remain unknown for this decision. If the available data cannot support the holiday-specific message, choose an approved neutral message or hold that contact from this campaign. A generic community update still needs ordinary marketing eligibility; neutral wording does not create sending permission.

Our worksheet uses country codes CA and US only as editorial labels. Map them to the actual values stored in your audience; this is not a claim about Migma's required API format. Likewise, “relevance approved” is the team's targeting decision, not a documented built-in holiday field.

Select the calendar, then the language#

The original routing model is:

1. If marketing eligibility fails: exclude.
2. If holiday relevance is unresolved: use approved neutral path or hold.
3. Select the supported holiday calendar from known campaign-market facts.
4. Select an approved language version within that calendar.
5. Review the resulting audience and artifact before scheduling.

Six invented cases exercise the separation:

• CA, English, relevant: October 12 calendar with approved English creative.
• CA, French, relevant: October 12 calendar with approved French creative.
• US, English, relevant: November 26 calendar with approved English creative.
• US, French, relevant: November 26 calendar with approved French creative.
• Country missing, English, Toronto timezone: neutral path or hold; timezone does not fill the missing market.
• CA, English, relevance unresolved: neutral path or hold despite the known calendar.

We checked that this model selects the calendar independently of language and does not use timezone to resolve unknown country. The exercise proves the fictional selector's behavior only. It does not prove your stored fields, campaign audience, or received message match the intended decision.

If a required language version is unavailable, use the team's reviewed language fallback policy or hold the campaign. Do not silently substitute a different country's holiday message merely because its English creative already exists.

Build the selected paths in Migma#

Migma's segment documentation documents separate country and language contact filters, custom-field filters, and combined filters that narrow the group. It also describes reviewing plain-language-generated filters and matching counts before saving. Use those review surfaces to inspect the actual criteria; a segment name such as “Thanksgiving English” does not tell you which calendar it serves.

Prepare separate source briefs for the approved Canadian and US calendar propositions. Migma's multilingual guide documents generating separate language versions and using the subscriber language field for language-specific campaign audiences. Preserve the chosen calendar's proposition in each language version; do not ask translation to invent cultural eligibility.

Inspect a small authorized test cohort before any real send, including the unknown-market and unresolved-relevance cases. Then apply the existing localized version controls to the selected artifacts. Start with the audience whose language is known but holiday relevance is not: that case reveals the assumption a translation-only workflow would miss.