Campaign smoke tests: 7 quick pre‑launch checks small teams should run before any marketing send

Quick preflight checks (consent, segments, tokens)

• Consent & suppression — How to: pull your send list and filter any canonical consent/suppression fields (opt‑in, do‑not‑contact, unsubscribed, GDPR flags) from CRM or email tool (HubSpot, Mailchimp, Salesforce). Failure signal: people with unsubscribe/opt‑out flags still in the list. Remediation: remove them or apply the suppression list; pause the send until backfill is fixed.

• Segment size & overlap sanity — How to: check segment count and compare against recent sends; run an overlap query to spot duplicates across segments (a quick CSV compare or CRM list that shows contact IDs). Failure signal: segment unexpectedly large, tiny, or shares many IDs with another active campaign. Remediation: reduce scope, split sends, or remove overlapping segment; delay launch if counts are off.

• Personalisation/token validation — How to: preview 10–20 real records across lifecycle stages and languages; use the platform preview or export sample to check tokens (name, company, custom fields). Failure signal: blank tokens, weird fallbacks (null, {{error}}) or wrong salutations. Remediation: add safe fallbacks, correct field mapping in CRM, and re‑run a small preview.

Content and timing checks (links, UTMs, timezones)

• Link, UTM and landing page checks — How to: click every link in a test copy (include CTA, images, unsubscribe, privacy links) and verify UTM parameters land in your CRM/campaign reporting. Failure signal: 404s, redirects to staging, missing UTMs, or broken unsubscribe links. Remediation: fix URLs or swap to a hold page; cancel the send if unsubscribe or privacy links fail.

• Timing & timezone sanity — How to: confirm scheduled send timezone vs recipient timezone settings (platform scheduling, scheduler rules or CRM timezone fields) and check recurring automation timers don't retrigger at midnight. Failure signal: early/late sends to large subgroups or repeated sends across time boundaries. Remediation: adjust schedule to recipient local time, add a cooldown window, or reschedule the campaign to a known safe slot.

Canary test, kill‑switch and rollback plan

• Canary/test send with verification — How to: send a small canary to 10–50 internal or seeded test addresses (mix desktop/mobile and different email clients) and verify rendering, links, personalization and tracking. Failure signal: rendering issues, token errors, missing images or incorrect CTAs. Remediation: stop the full send and iterate—fix templates or tokens, then re‑canary.

• Lightweight kill‑switch + rollback — How to: have a three‑step rollback ready: 1) Pause scheduled send or campaign flow (platform UI or scheduler); 2) Apply a suppression tag or flip a single ‘suppress_sends’ flag on the segment/CRM so no further messages go out; 3) Restore a pre‑send snapshot of segment or content if you need to retry. Failure signal: inability to pause from the UI or unexpected queued recipients. Remediation: use suppression flag at CRM-level, notify team, and run a safe rollback drill.

• Need help? If your Fareham or South Coast team wants hands‑on support preparing these checks or building a simple kill‑switch, see our marketing automation support in Hampshire — Optira can help run the preflight and document a short rollback plan.