End-to-End SFMC Workflow
Customer Data
↓
Contact Builder / Data Extensions
↓
Audience Segmentation
↓
Content Builder
↓
Email Studio
↓
Journey Builder / Automation Studio
↓
Preview & Test
↓
Email on Acid / Litmus
↓
QA Sign-off
↓
Production Release
Data Management
- Data Cloud
- Contact Builder
- Data Extensions
- SQL Query Activities
- Segmentation
- Suppression Lists
Content Creation
- Content Builder
- Email Studio
- Email Templates
- Content Blocks
- Dynamic Content
- AMPscript
AMPscript Example
%%=IIF(EMPTY(first_name),'Valued Customer',first_name)=%%
This displays the customer's first name when available, otherwise a friendly fallback greeting.
Journey Builder
Entry → Email → Wait → Decision → Follow-up → Exit
Automation Studio
Schedule → Import → SQL → Update Data Extension → Refresh Audience → Ready for Campaign
QA/QC Validation Checklist
- Audience & Data Extensions
- Merge Fields
- AMPscript
- Dynamic Content
- Subject Line & Preheader
- Images & Branding
- Links & CTA
- HTML & CSS
- Responsive Design
- Accessibility (WCAG)
- Email on Acid Validation
- Litmus Validation
- Production Sign-off
Accessibility Requirements
- Meaningful ALT text
- Minimum 4.5:1 colour contrast
- Semantic heading order
- Readable font sizes
- Descriptive links
- Responsive layout
- Screen reader compatibility (NVDA/JAWS)
Best Practice: While WCAG was written for web content, organizations such as banks apply WCAG 2.1 AA principles to customer-facing emails to support accessibility and regulatory expectations.
Email on Acid
Purpose: Enterprise email QA platform used to validate Salesforce Marketing Cloud email templates before production.
Why use it?
- Validate rendering across Outlook, Gmail, Apple Mail and mobile clients
- Check HTML & CSS compatibility
- Verify images and broken links
- Validate accessibility and dark mode
- Identify spam and deliverability risks
Typical QA Workflow
SFMC Preview & Test
↓
Send Test Email
↓
Email on Acid
↓
Rendering + Accessibility + Links + Spam
↓
Developer Fixes
↓
Regression Test
↓
QA Approval
Common Defects
| Issue | Example |
|---|
| Broken Image | Banner missing |
| CSS Issue | Padding ignored in Outlook |
| Missing ALT Text | Accessibility failure |
| Broken CTA | 404 page |
| Merge Field Error | %%FirstName%% displayed |
Litmus
Purpose: Enterprise email rendering and collaboration platform used by QA teams to validate email quality before release.
- Cross-client previews
- Accessibility validation
- Link checking
- Responsive design verification
- HTML/CSS rendering
- Team review and approval workflows
BrowserStack
Purpose: BrowserStack is used to test the landing pages and CloudPages linked from emails across real browsers and devices.
Customer clicks CTA
↓
Landing Page Opens
↓
BrowserStack
↓
Chrome • Edge • Firefox • Safari
↓
Desktop • Tablet • Mobile
↓
QA Approval
- Browser compatibility
- Responsive layout
- Form validation
- Accessibility
- Performance
Testing Tools Comparison
| Tool | Primary Use |
|---|
| Preview & Test | Validate merge fields, AMPscript, personalization and dynamic content. |
| Email on Acid | Email rendering, accessibility, spam, HTML/CSS validation. |
| Litmus | Cross-client rendering, collaboration and previews. |
| BrowserStack | Landing pages, CloudPages and browser compatibility. |
As a QA/QC Tester and Auditor, you validate audience segmentation, Data Extensions, HTML/CSS rendering, AMPscript personalization, dynamic content, accessibility, customer journeys, automation workflows, A/B testing and cross-client compatibility before approving Salesforce Marketing Cloud campaigns for production.