Test Promotional Email Deadlines as Exact Instants

Represent every promotional deadline as one canonical instant, then derive local customer copy and system schedules from it. Migma can build the coordinated email series, but the campaign owner must prove that “ends tonight,” countdowns, reminder suppression, and commerce rules all describe the same moment.

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 8, 2026.

Migma's dated Black Friday calendar argues for campaign entries with conditions instead of a universal daily schedule. Its Cyber Monday guide distinguishes an offer that always ran through Monday from a real extension or a new Monday proposition. Both decisions depend on precise time semantics.

Define the interval before writing copy#

offer_id: "weekend-tableware-v4"
starts_at_utc: "2026-11-27T00:00:00Z"
ends_at_utc: "2026-11-30T22:59:00Z"
boundary_rule: "valid when submitted_at <= ends_at_utc"
commercial_timezone: "Europe/Madrid"
supported_markets: ["ES", "FR", "GB"]
localization_rule: "render recipient-market civil time with named zone"
extension_status: "planned-original-window"
owner: "named promotion lead"

Do not use 23:59 without a zone. Avoid storing only a duration such as “four days”; retries, daylight-saving transitions, and later edits can shift the result.

Build the rendering matrix#

If different markets truly close at different local times, create separate offer intervals. Do not pretend one global instant is local midnight everywhere.

Give Migma a temporal contract#

Migma's Email Series documentation describes generating connected messages from one brief. Include both the instant and approved local display rules:

Create a launch, buying-help follow-up, and closing notice for weekend-tableware-v4. The offer closes at 2026-11-30T22:59:00Z. For Spain and France, display 30 November at 23:59 CET. For the UK, display 30 November at 22:59 GMT. Do not call this an extension. Do not use “tonight” outside a same-day localized version. Leave scheduling and recipient routing for review.

Search the entire series for dates, days, relative phrases, countdown labels, legal terms, image text, subjects, and preview copy. Shared input does not guarantee shared output.

Run boundary cases#

Use a clock-controlled test environment or approved scheduler preview. Exercise:

1. one second before start;
2. exactly at start;
3. one second after start;
4. one second before end;
5. exactly at end under the documented comparison rule;
6. one second after end;
7. a cart opened before end and submitted after end;
8. a reminder queued before end but handed to the provider after end;
9. a recipient whose local date differs from the commercial timezone;
10. a clock-change date for any reusable scheduling logic.

Record the clock source, scheduler state, provider handoff time, received time, customer rendering, and commerce outcome. A campaign timestamp alone does not prove when the recipient saw the message.

Coordinate scheduling and suppression#

Migma's campaign guide documents send and schedule controls. Whatever system performs the final send, define the last safe provider-handoff time separately from the offer end. Queuing a closing notice at the deadline makes the message stale by construction.

Add a guard that suppresses promotional reminders when the remaining useful window is shorter than the approved delivery margin. Keep provider delay, rate limits, retries, and market routing in that calculation.

latest_handoff = offer_end - delivery_margin
send_allowed = now < latest_handoff AND offer_version_is_current

This is an operating rule, not a deliverability guarantee. Choose the margin from observed system behavior and business tolerance.

Version extensions honestly#

When a promotion changes, classify it:

• Continuation: the original approved interval already included the later time.
• Extension: the approved end instant changed after publication.
• New offer: products, discount, audience, or material terms changed.

An extension needs a new offer version, updated customer language, commerce-rule test, and review of anyone who received a “final” claim. A new design does not create a new offer, and Monday being on the calendar does not prove an extension.

Stop conditions#

Stop when the deadline has no timezone; a local date is manually copied across markets; “tonight” can arrive tomorrow; countdown and checkout use different clocks; queued mail can cross expiry without suppression; the end comparison is undefined; or an extension overwrites the original record without an audit trail.

Evidence limits#

Migma documents series creation and campaign scheduling and published dated seasonal guidance. Marketing Wiki did not exercise a Migma account, ESP queue, countdown, recipient locale, clock transition, or commerce rule. Apply this boundary suite to the exact systems and markets in production.