Campaign QA
The campaign pre-send checklist
A pre-send checklist for the whole campaign, not just the email.The expensive errors don’t live inside one asset. They live between channels: the offer that changed in the email but not the SMS, the landing page that still points at last month’s promo.
This is the multichannel hub. Each channel below has the checks that actually catch errors, and the email section links to the deep-dive guides. It sits under campaign production management, because QA belongs in production, not at the end.
Get the multichannel pre-send checklist
The full checklist for email, SMS, WhatsApp and landing pages, as a printable PDF with a named owner per line.
The checks, by channel
- 01Renders correctly across your real client mix: not 90 clients, the ones your open data says matter.
- 02Survives dark mode: logo visible, brand colors intact, buttons and text still legible.
- 03Every merge field has a template-level fallback, tested with rows that fake missing data.
- 04Links, UTMs and the reply-to address all resolve; the preheader isn't the last edit's leftover.
SMS
- 01Sender ID and opt-out language are correct for every destination country.
- 02The link is short, tracked and points at the live landing page, not a staging URL.
- 03Character count and encoding are checked so the message doesn't silently split or drop emoji.
- 01The template is approved and the variables map to the right data in order.
- 02Media and buttons render on both mobile apps, and the fallback copy reads on its own.
- 03The opt-in basis for each recipient is on the record before send.
Landing pages
- 01The offer, price and dates match the email and SMS that drive traffic to it: no drift between channels.
- 02The form works, fires its events, and the thank-you or redirect actually happens.
- 03It holds up on mobile and loads fast enough that the click survives.
For the email channel specifically, go deeper: what goes on an email pre-send checklist, which email clients you should actually test, why your email looks broken in dark mode, and how to set email personalization fallbacks.
FAQ
Common questions.
Why not one generic checklist for everything?
Generic QA lists fail because nobody reads item 23, and because a check that matters for email is noise for SMS. A campaign pre-send checklist is adapted by channel and by campaign type, and each item has one named owner, so the checks that apply actually get done, and the ones that don't aren't there to ignore.
When should these checks happen?
During production, not at the end. When QA is a gate on send day, it either gets rushed or it slips the launch. Attaching each check to the asset while it's still being built is the whole idea behind campaign production management. The campaign can't be marked ready until the checks and approvals exist.
Does LaunchSign send the campaign?
No. LaunchSign runs the production and pre-send QA, then hands a finished, checked, signed-off campaign to the platform you already use to build and send. The send itself still happens there.
Catch it in production, not on send day
LaunchSign attaches these checks to each asset while it’s still being produced, so most of the list is done long before the campaign is marked ready.