Email Campaigns | IMI Life Science

Email Campaign Recovery

Purpose: Compose, schedule and review email campaigns while preserving failed drafts.

  • Save Draft: Save the current content without activating its selected schedule. Scheduling an existing campaign requires Schedule Campaign.
  • Schedule Campaign: Supply complete content, recipients and a future UTC time. Send Now requires complete content and recipients.
  • Recipients: Manual addresses may be separated by lines, commas or semicolons. Segment audiences use actual segment identifiers, not illustrative names.
  • A/B testing: Save two to five uniquely named variants with positive splits totaling 100 percent. The test pool receives variant content; the remainder waits for winner evaluation.
  • Failed delivery request: A saved draft is retained. Dismiss a covering error notification, inspect campaign status and retry the same campaign rather than creating a duplicate.
  • Delivery evidence: Scheduled, Sending and an accepted request are not proof of provider delivery. Bulk delivery recovery is not yet certified; use approved test audiences until its retry and reconciliation gates pass.

Durable Campaign Delivery

Purpose: Review durable delivery evidence without accidentally repeating an uncertain provider operation. This section supersedes earlier provisional bulk-delivery guidance.

  • Audience: Select real segments using the segment checkboxes, up to fifty. Failed catalog loading offers Retry segments. Missing or archived selections require explicit correction; invalid saved selections are never silently discarded. Manual addresses accept lines, commas or semicolons. Invalid addresses and combined audiences above 100,000 are rejected before any send is admitted.
  • Durable admission: An accepted send queues one saved audience and its publication intents. Broker retries reuse the saved recipient identities rather than creating another audience.
  • Read evidence: Completed means campaign processing finished, not that every recipient received mail. Provider accepted is distinct from confirmed delivery. Engagement rates use confirmed deliveries when available, otherwise provider acceptance.
  • Unknown outcomes: Delivery review lists uncertain recipient operations. Review remains unavailable until the original provider lease expires. Reload delivery status to obtain a fresh observation.
  • Review deliberately: Choose Provider accepted this attempt only with positive acceptance evidence. Choose Provider confirms this attempt was not sent only with evidence of zero provider effect. Supply a ten-to-five-hundred-character evidence statement and verify the evidence checkbox. The decision is bound to the observed attempt and journaled atomically.
  • Understand recovery: Confirmed not sent queues a new safe attempt of the same operation; it does not confirm delivery. Suppression and current consent still apply. An accepted review does not bypass them for any later action.
  • Uncertain review response: Use Check review receipt. Do not repeat the POST or create another campaign. Receipt metadata survives a page reload; evidence and email content are not retained in browser storage. A missing receipt is not proof that an uncertain write rolled back.
  • Version readiness: The matching Admin, Analytics and Notifications versions, migrations and versioned broker topics must be deployed together. An unavailable review queue is not an empty successful queue. Legacy in-flight work must be reconciled explicitly, never reset to Draft for a blind resend.