Email Campaign QA Checklist for Marketing Teams

Introduction

A marketing email can be visually perfect and still fail in production.

The wrong URL, missing image, incorrect personalization token, broken Outlook button, unreadable dark-mode footer or missing unsubscribe link can turn an otherwise successful campaign into a production problem.

This is why I treat campaign QA as a complete pre-production process, not simply as “checking the HTML.”

With more than 11 years of email development and campaign work, I have found that the most reliable QA process checks the campaign from several different perspectives: content, code, rendering, accessibility, tracking and final business requirements.

My Campaign QA Workflow

I normally break campaign QA into stages so that problems are found before the final approval step.

Campaign brief
      ↓
Content QA
      ↓
Subject + preheader
      ↓
Links + CTA
      ↓
Images + assets
      ↓
HTML + CSS
      ↓
Responsive testing
      ↓
Email-client rendering
      ↓
Outlook / Gmail / Apple Mail
      ↓
Dark mode
      ↓
Accessibility
      ↓
Tracking + personalization
      ↓
Footer / compliance
      ↓
Final proof
      ↓
Approval
      ↓
Production

Not every campaign needs exactly the same testing depth. The target audience, email platform, campaign type and client requirements determine the final testing matrix.

1. Campaign Brief and Requirements

Before checking the HTML, I make sure I understand what the campaign is supposed to do.

I verify:

• Campaign name
• Audience
• Language and locale
• Campaign objective
• Offer or promotion
• Send date
• Approved design
• Approved copy
• Required email clients
• Tracking requirements
• Personalization requirements

This gives the QA process a reference point. Without an approved source, it is difficult to determine whether the final email is actually correct.

2. Copy and Content QA

I compare the final email against the approved copy or copy deck.

I check:

• Headline
• Body copy
• CTA labels
• Product names
• Prices
• Discounts
• Dates
• Terms and conditions
• Legal copy
• Footer content

I also look for accidental placeholder text such as “Lorem ipsum,” “TEST,” old campaign copy or development URLs.

3. Subject Line and Preheader QA

The email body can be perfect, but the inbox presentation can still have an issue.

I check:

• Subject line
• Preheader text
• Spelling and punctuation
• Personalization variables
• Locale-specific copy
• Unexpected fallback text

I also check that hidden preheader content does not accidentally appear as visible content at the top of the email.

Inbox preview:

[ Subject Line ]
[ Preheader Text ]

        ↓

Email body

4. Link and CTA QA

Links are one of my highest-priority checks because a broken or incorrect CTA can directly affect campaign performance.

I verify:

• Primary CTA
• Secondary CTA
• Logo link
• Product links
• Image links
• Social links
• Privacy link
• Unsubscribe link

I check the actual destination rather than only checking that an href exists.

<a href="https://example.com/shop">
  Shop Now
</a>

5. Image and Asset QA

I verify every production image and graphic.

• Correct image
• Correct file path
• Image loads successfully
• Correct dimensions
• Correct crop
• Correct alt text
• Mobile behavior
• Dark-mode behavior
• Transparent background behavior

I also check that temporary development or staging image URLs have not been left in the production HTML.

<img
  src="https://example.com/images/hero.jpg"
  width="600"
  alt="September gift card offer"
  style="display:block;width:100%;max-width:600px;"
>

6. HTML and CSS QA

Once content and assets are confirmed, I review the email code.

I look for:

• Broken HTML
• Unclosed tags
• Incorrect table nesting
• Unexpected widths
• Unexpected fixed heights
• Duplicate CSS
• Missing responsive styles
• Outlook-specific requirements
• Dark-mode rules
• Accessibility markup

I also check that the production version contains the expected inline styles and that no development-only code remains.

7. Responsive QA

I test the desktop and mobile versions as two connected experiences.

For each major module, I check:

• Column stacking
• Image scaling
• Text wrapping
• Button size
• Padding
• Margins
• Typography
• Footer layout

Desktop:

[ IMAGE ] [ CONTENT ]

Mobile:

[ IMAGE ]
[ CONTENT ]

I pay particular attention to headlines and buttons because fallback fonts and mobile widths can change the visual balance of a section.

8. Email-Client Rendering QA

A browser preview is not enough for production email QA.

I validate the campaign against the email clients that matter for the target audience.

Depending on the campaign, this may include:

• Outlook
• Gmail
• Apple Mail
• Mobile email applications
• Other required client versions

9. Outlook QA

Outlook gets special attention in many enterprise email campaigns.

I check:

• Button rendering
• Background images
• Widths and heights
• Padding
• Line-height
• Vertical alignment
• Two-column modules
• Unexpected white lines
• VML fallbacks where required

I also compare Outlook rendering against the approved design and make sure a compatibility fix has not changed the experience in other clients.

10. Gmail QA

I test Gmail separately because the final email experience can differ by platform and environment.

My checks include:

• Desktop rendering
• Mobile rendering
• Responsive behavior
• Images
• Typography
• Links
• Dark mode
• Long content behavior

I do not assume that a single Gmail screenshot represents every Gmail environment.

11. Apple Mail QA

Apple Mail is another important part of my rendering checks.

I review:

• Typography
• Spacing
• Images
• Responsive behavior
• Buttons
• Dark mode
• Footer readability

I also consider how the email feels on a real mobile screen rather than judging only from a desktop preview.

12. Dark-Mode QA

Dark mode is a separate QA scenario in my workflow.

I check:

• Background colors
• Body text
• Secondary text
• Links
• Buttons
• Logos
• Transparent images
• Footer
• Contrast

A design that works perfectly in light mode can become difficult to read after client-side color transformations or dark-mode CSS.

13. Accessibility QA

I include accessibility in campaign QA rather than treating it as a separate project.

I check:

• Alt text
• Decorative images
• Meaningful link text
• Heading structure
• Reading order
• Color contrast
• Dark-mode contrast
• Table semantics
• Mobile readability

I have used NVDA for screen-reader testing and browser accessibility tools as part of my QA workflow.

14. Tracking and Analytics QA

Tracking should be checked separately from the visual email.

Depending on the campaign platform, I verify:

• UTM parameters
• Campaign identifiers
• Link tracking
• Click tracking
• Required analytics parameters
• Tracking redirects

I check that tracking parameters have not changed the destination URL or introduced malformed links.

Final CTA URL
      ↓
Tracking parameters
      ↓
Redirect / tracking layer
      ↓
Final landing page

15. Personalization QA

Personalization can introduce problems that are invisible in a normal static preview.

I check:

• First-name variables
• Dynamic product content
• Conditional content
• Fallback values
• Locale-specific content
• Audience-specific variations

For example, a campaign should have a sensible fallback if a first name is missing.

Personalized:

Hi Sachin,

Fallback:

Hi there,

The exact syntax depends on the marketing platform, but the QA principle is the same: test both the populated and fallback versions.

16. Footer and Compliance QA

The footer often contains important operational and compliance-related information, so I do not treat it as an afterthought.

I check:

• Company information
• Physical address where required
• Privacy link
• Preference-center link
• Unsubscribe link
• Legal copy
• Social links

I also make sure footer text remains readable on mobile and in dark mode.

17. Deliverability Preflight

Email QA is not the same as deliverability testing, but a campaign preflight can still identify obvious issues before launch.

Depending on the email platform and campaign requirements, I review:

• Sender information
• Reply-to address
• Subject line
• Unsubscribe mechanism
• Required compliance elements
• Broken links
• Broken images
• Unexpected placeholder content

I do not treat a visual QA checklist as a replacement for the organization's dedicated deliverability process. These are separate areas that should work together.

18. Final Proof and Approval

The final proof is where I stop making assumptions and review the campaign as a recipient would see it.

I check:

• Correct campaign version
• Correct audience
• Correct subject line
• Correct preheader
• Correct content
• Correct images
• Correct links
• Correct tracking
• Correct personalization
• Correct rendering
• Accessibility reviewed
• Footer reviewed

QA complete
    ↓
Reviewer approval
    ↓
Campaign setup
    ↓
Final proof
    ↓
Production send

My Master Email Campaign QA Checklist

I recommend turning this into a team checklist or QA sign-off document so that campaign quality does not depend entirely on one person's memory.

Common Email Campaign QA Mistakes

1. Only checking the HTML. Campaign QA also includes content, links, tracking, personalization and production setup.
2. Testing only in a browser. Browser previews do not represent every email-client environment.
3. Checking links only by looking at the code. The destination itself should be verified.
4. Ignoring mobile. A desktop-perfect campaign can still fail on a phone.
5. Skipping dark mode. Text, logos and buttons can become difficult to see.
6. Skipping accessibility. Visual correctness does not guarantee a usable email.
7. Testing only the happy-path personalization. Fallback values and alternate audience conditions also need review.
8. Changing HTML after approval without regression testing. A small change can affect another client or component.
9. Using outdated copy or assets. QA should always use the production-approved version.
10. Assuming QA is complete because someone else checked it. A documented checklist makes responsibilities clearer.

FAQ

Conclusion

A good email campaign QA process protects more than the visual design. It protects the campaign's content, links, customer experience, accessibility, tracking and business objective.

My approach is to break QA into clear stages: understand the campaign, verify the content, validate links and assets, inspect the HTML, test responsive behavior, check the important email clients, review dark mode and accessibility, validate tracking and personalization, and then complete a final proof before production.

The biggest advantage of a checklist is consistency. Instead of relying on memory, the team has a repeatable process that can be improved whenever a new production issue is discovered.

For marketing teams, that is the real value of email QA: not simply finding mistakes, but building a repeatable process that makes every future campaign safer and more predictable.