Run Campaign Preflight before scheduling
Use K2Mailer’s deterministic preflight gate to catch critical audience, sending, tracking, content-format, unsubscribe, and link problems before a campaign is scheduled.
What Campaign Preflight validates
- At least one selected Active sending server and the required K2Mailer sending-domain record.
- Stored SPF, DKIM, DMARC, tracking-domain, and sender-alignment information for the effective From identity, with advisory versus blocking behavior kept separate.
- An estimated sendable audience after current subscription, activity, suppression, duplicate, complaint, and hard-bounce rules used by the campaign pipeline.
- HTML and Text recipient formats independently, including a usable body and visible unsubscribe mechanism for the format that will actually be sent.
- Known merge tags, tracking configuration, malformed absolute URLs, unsafe javascript links, and the static structure of URLs that contain supported placeholders.
- Signed one-click unsubscribe infrastructure required by the selected campaign transport.
Hard blockers versus warnings
Deterministic blockers prevent the schedule from being created or updated. The same server-side gate runs on the final write path, so bypassing the browser modal does not bypass those rules.
Some readiness signals are warnings rather than hard blockers. For example, SPF, DKIM, or DMARC status uses the latest state persisted in K2Mailer rather than a fresh DNS lookup at scheduling time, so an external provider-managed configuration may be valid even if K2Mailer has stale verification state.
Content Analysis is a separate layer
Campaign Preflight is deliberately deterministic and network-independent. AI suggestions and content moderation belong to the separate Content Analysis workflow, where premium plans can receive contextual recommendations and moderation results.
An AI or network outage does not disable deterministic preflight. AI can help explain or improve content, but it does not override suppression, consent, bounce, complaint, or other send-safety rules.
What happens when the result is ready
If a blocker is present, K2Mailer stops and shows the issue so it can be corrected. In the current scheduling and Send Test flows, a no-blocker result shows the ready state briefly and then proceeds automatically without requiring a second confirmation click.
Campaign preparation and the final recipient guard remain authoritative after scheduling, so a recipient who becomes ineligible before delivery is still skipped.
Was this guide enough?
Contact support if your screen or result is different.