Data Cloud (Formerly Salesforce CDP)

Salesforce Data Cloud is a Customer Data Platform (CDP) that collects, connects, and unifies customer information from multiple sources such as CRM, websites, mobile apps, marketing systems, and third-party applications. It creates a single, unified customer profile that Marketing Cloud can use for advanced segmentation, personalization, analytics, and AI-driven customer journeys.

For a QA/QC Tester or Auditor, Data Cloud is important because the quality of customer data directly affects audience segmentation, personalization, and campaign accuracy. Incorrect or incomplete customer data can result in customers receiving the wrong communication or missing important marketing campaigns.

Key Features

• Unifies customer data from multiple business systems.
• Creates a Single Customer View (360° Customer Profile).
• Performs Identity Resolution to merge duplicate customer records.
• Builds audience segments for personalized marketing campaigns.
• Provides real-time customer insights for Journey Builder.
• Supports AI-driven personalization and recommendations.
• Integrates with Salesforce CRM, Marketing Cloud, Commerce Cloud and external data sources.

QA Responsibilities

• Verify customer data is synchronized correctly from source systems.
• Validate audience segmentation before campaign execution.
• Confirm customer attributes are populated correctly for personalization.
• Ensure duplicate customer records are resolved appropriately.
• Verify suppression and exclusion rules.
• Confirm only eligible customers are included in campaign audiences.

Contact Builder

Contact Builder is the central customer data management component within Salesforce Marketing Cloud. It organizes contacts, relationships, Data Extensions, and customer attributes so marketers can build personalized customer journeys and targeted campaigns.

Think of Contact Builder as the location where Salesforce Marketing Cloud stores, organizes, and relates customer information before it is used by Email Studio, Journey Builder, Automation Studio, and other Marketing Cloud applications.

Key Components

• Contacts – Stores individual customer records using a unique Contact Key.
• Data Extensions – Custom tables that store marketing and customer data.
• Attribute Groups – Connect related Data Extensions together.
• Relationships – Define how customer data tables are linked.
• Population – Groups contacts into logical audiences.

Why Contact Builder Matters

• Supports personalized email marketing.
• Provides customer attributes for AMPscript and Dynamic Content.
• Supplies audiences for Journey Builder.
• Maintains customer relationships across multiple Data Extensions.
• Ensures a single Contact Key identifies each customer.

QA Responsibilities

• Verify Data Extensions contain accurate customer data.
• Validate Contact Keys are unique and prevent duplicate customer records.
• Confirm Attribute Groups and relationships are configured correctly.
• Validate merge fields used for personalization.
• Verify customer records appear in the correct audience segments.
• Ensure suppression lists and exclusion criteria are working correctly.
• Compare Data Extension record counts against business requirements.

Data Cloud vs Contact Builder

What is AMPscript?

AMPscript (Advanced Marketing Personalization Script) is Salesforce Marketing Cloud's proprietary scripting language used to personalize email content, SMS messages, landing pages, and customer journeys. It allows marketers to retrieve customer data from Data Extensions, apply business rules, display dynamic content, and personalize communications for every recipient.

Unlike standard merge fields, AMPscript can perform conditional logic, retrieve records from Data Extensions, format dates, perform calculations, and display different content based on customer attributes such as location, advisor, loyalty status, portfolio value, or language preference.

Common Uses of AMPscript

• Personalize greetings using customer names.
• Display different offers based on customer segments.
• Retrieve customer information from Data Extensions.
• Display dynamic content based on business rules.
• Show advisor information for Private Wealth clients.
• Create personalized links and landing pages.
• Handle missing customer information with fallback values.

Example 1 – Personalized Greeting

This AMPscript displays the customer's first name. If the value is missing, it displays "Valued Customer".

%%[
SET @FirstName = AttributeValue("FirstName")

IF EMPTY(@FirstName) THEN
    SET @FirstName = "Valued Customer"
ENDIF
]%%

Hello %%=v(@FirstName)=%%,
Welcome to a Bank Private Wealth.

Output

• Hello Michael, Welcome to a Bank Private Wealth.
• Hello Valued Customer, Welcome to a Bank Private Wealth.

Example 2 – Dynamic Content Based on Customer Tier

This example displays different messaging depending on the client's wealth segment.

%%[
SET @Tier = AttributeValue("ClientTier")

IF @Tier == "Platinum" THEN

]%%

Exclusive Wealth Management Benefits

%%[ ELSE ]%%

Explore Our Premium Banking Solutions

%%[ ENDIF ]%%

Example 3 – Lookup Customer Advisor

This example retrieves the customer's assigned advisor from a Data Extension.

%%[
SET @Advisor =
Lookup(
    "AdvisorDE",
    "AdvisorName",
    "ClientID",
    AttributeValue("ClientID")
)
]%%

Your dedicated advisor is:
%%=v(@Advisor)=%%

Common AMPscript Functions

• AttributeValue() – Retrieves a customer attribute safely.
• Lookup() – Retrieves a single value from a Data Extension.
• LookupRows() – Returns multiple records.
• EMPTY() – Checks whether a value exists.
• IIF() – Inline IF statement.
• FormatDate() – Formats dates.
• ProperCase() – Converts text to Proper Case.
• Concat() – Combines text values.

QA Responsibilities

• Validate all merge fields before production.
• Verify AMPscript executes without errors.
• Test every conditional business rule.
• Confirm fallback values display correctly.
• Ensure no raw AMPscript appears in production emails.
• Validate dynamic content for every audience segment.
• Verify Data Extension lookups return the correct customer information.
• Test personalization using multiple customer profiles.

What is Journey Builder?

Journey Builder is Salesforce Marketing Cloud's automation engine that creates personalized, multi-step customer journeys across multiple communication channels such as Email, SMS, Push Notifications, Mobile, Advertising, and CloudPages. It automatically delivers the right message to the right customer at the right time based on customer behavior, business rules, and real-time data.

Instead of sending a single email blast, Journey Builder allows organizations to guide customers through a complete marketing experience using automated workflows. Each customer follows a personalized path depending on their actions, profile, preferences, or business conditions.

Why Organizations Use Journey Builder

• Automate customer communications.
• Create personalized customer experiences.
• Send emails based on customer behaviour.
• Deliver multi-step onboarding campaigns.
• Send reminders, follow-ups and notifications.
• Reduce manual marketing effort.
• Increase customer engagement and conversion rates.

Example: Private Wealth Welcome Journey

Suppose a new client opens a Private Wealth investment account at a Bank. Journey Builder can automatically guide that client through a personalized welcome experience without manual intervention.

Key Components of Journey Builder

• Entry Source – Defines how customers enter the journey (Data Extension, API, Salesforce Event, etc.).
• Activities – Actions performed during the journey such as sending an email or SMS.
• Decision Split – Routes customers down different paths based on business rules.
• Wait Activity – Delays the next communication for a specified period.
• Goals – Measures whether customers achieve the intended outcome.
• Exit Criteria – Determines when customers leave the journey.

Typical Journey Builder Activities

• Email Send
• SMS Send
• Push Notification
• Decision Split
• Wait Activity
• Update Contact
• Salesforce Activity
• CloudPage

QA Responsibilities

• Validate the Entry Source contains the correct audience.
• Verify customer segmentation before activation.
• Test Decision Split business rules.
• Validate Wait Activities.
• Ensure customers follow the correct journey path.
• Verify dynamic content and AMPscript personalization.
• Validate suppression lists and exclusion rules.
• Ensure customers do not enter the journey multiple times unless intended.
• Verify Exit Criteria.
• Perform end-to-end regression testing before production.

Common Journey Builder Defects

• Incorrect audience entering the journey.
• Broken Decision Split logic.
• Incorrect wait duration.
• Duplicate customer entries.
• Personalization failures.
• Dynamic content displaying incorrectly.
• Broken links or images.
• Emails sent in the wrong sequence.

Journey Builder Workflow Example

The example below illustrates a typical Salesforce Marketing Cloud Journey Builder workflow. Customers enter the journey through a Data Extension, receive personalized email communications, wait for defined periods, pass through decision and engagement splits, and may receive additional messages such as Email, SMS, or Push Notifications before exiting the journey.

Figure: Example of a Salesforce Marketing Cloud Journey Builder workflow showing Entry Sources, Email Activities, Wait Activities, Engagement Splits, Decision Splits, SMS, Push Notifications, and Exit Criteria.

What is Automation Studio?

Automation Studio is Salesforce Marketing Cloud's backend automation tool used to automate repetitive marketing processes such as importing files, running SQL queries, refreshing Data Extensions, segmenting audiences, and preparing customer data before marketing campaigns are sent.

Unlike Journey Builder, which focuses on customer communications, Automation Studio works behind the scenes to ensure customer data is accurate, up to date, and ready for Email Studio and Journey Builder.

Why Organizations Use Automation Studio

• Import customer data automatically.
• Refresh Data Extensions on a schedule.
• Run SQL queries for audience segmentation.
• Clean and transform customer data.
• Create suppression and exclusion lists.
• Schedule recurring marketing processes.
• Reduce manual effort and improve data accuracy.

Typical Automation Workflow

Automation Studio Activities

• Import File Activity – Imports customer data into Marketing Cloud.
• SQL Query Activity – Creates or refreshes audience Data Extensions.
• Filter Activity – Builds audiences without writing SQL.
• Data Extract Activity – Exports Marketing Cloud data.
• File Transfer Activity – Encrypts, decrypts, or transfers files using FTP.
• Script Activity – Executes server-side scripts for advanced automation.
• Verification Activity – Confirms a file exists before continuing the automation.

Real Banking Example

Every night at 2:00 AM, a Bank receives an updated customer file from its core banking system containing new investment clients, account updates, and customer preferences. Automation Studio automatically processes this data before the next day's marketing campaigns begin.

QA Responsibilities

• Verify automation schedules.
• Confirm files import successfully.
• Validate SQL query execution.
• Verify Data Extension record counts.
• Confirm audience segmentation is correct.
• Validate suppression lists.
• Review automation logs for failures.
• Verify notifications are configured for errors.
• Test recovery after failed automation runs.
• Ensure downstream Journey Builder receives the correct audience.

Common Automation Studio Defects

• Import file failed.
• SQL query returned incorrect audience.
• Duplicate customer records.
• Automation executed at the wrong time.
• Data Extension not refreshed.
• Suppression list missing customers.
• Incorrect file mapping.
• Journey Builder started before data was ready.

Automation Studio vs Journey Builder

CASL & Privacy Compliance

CASL (Canada's Anti-Spam Legislation) is Canada's law that regulates the sending of Commercial Electronic Messages (CEMs), including marketing emails, SMS messages, and other electronic communications. Organizations must obtain appropriate customer consent before sending marketing communications and must provide recipients with an easy way to unsubscribe.

For organizations such as a Bank, complying with CASL is essential to protect customer trust, avoid regulatory penalties, and ensure marketing campaigns are sent only to customers who have granted the appropriate permissions.

CASL Requirements

• Obtain customer consent before sending commercial emails.
• Include a clear unsubscribe link in every marketing email.
• Display accurate sender information.
• Include company contact information.
• Respect customer opt-out requests promptly.
• Maintain records of customer consent where required.

Privacy Best Practices

• Protect customer personal information.
• Limit access to sensitive customer data.
• Use customer data only for authorized business purposes.
• Validate audience eligibility before every campaign.
• Prevent unauthorized customer communications.
• Follow corporate privacy and security policies.

How Salesforce Marketing Cloud Supports Compliance

• Publication Lists – Allow customers to unsubscribe from specific types of communications.
• Suppression Lists – Prevent certain customers from receiving marketing emails.
• Data Extensions – Store customer consent status and marketing preferences.
• Send Classifications – Differentiate Commercial and Transactional email communications.
• Journey Builder – Can automatically remove customers who withdraw consent.
• Automation Studio – Refreshes suppression and exclusion lists before campaigns are sent.

QA Responsibilities

• Verify customer consent before production sends.
• Validate suppression and exclusion lists.
• Confirm unsubscribe links function correctly.
• Ensure opt-out customers do not receive marketing emails.
• Verify sender name and sender email address.
• Confirm company contact information appears in every email.
• Validate the correct Send Classification is used.
• Verify privacy-related customer attributes are accurate.
• Review audience segmentation to ensure only eligible customers receive communications.
• Perform compliance validation before production approval.

Common Compliance Defects

• Email sent to customers without valid consent.
• Suppression list not applied.
• Broken unsubscribe link.
• Incorrect sender information.
• Missing company contact information.
• Commercial email sent using the wrong Send Classification.
• Opted-out customers still receiving marketing communications.

Accessibility & WCAG 2.1 AA

Web Content Accessibility Guidelines (WCAG) are internationally recognized standards developed by the World Wide Web Consortium (W3C) to make digital content accessible to people with disabilities. Although WCAG was originally developed for websites, many organizations—including banks such as a Bank—apply these same accessibility principles to marketing emails, landing pages, and other customer communications.

Accessible emails ensure that customers who use assistive technologies such as screen readers, keyboard navigation, or high-contrast displays can successfully read and interact with marketing communications. Accessibility is an important part of delivering an inclusive customer experience while meeting legal and organizational accessibility standards.

The Four WCAG Principles (POUR)

• Perceivable – Information must be presented in ways users can perceive, such as providing alternative text for images.
• Operable – Users must be able to navigate and interact with content using a keyboard or assistive technology.
• Understandable – Content should be clear, readable, and predictable.
• Robust – Content should work reliably across browsers, email clients, and assistive technologies.

Accessibility Best Practices for Email Marketing

• Provide meaningful ALT text for informative images.
• Maintain a minimum colour contrast ratio of 4.5:1 for normal text.
• Use a logical heading hierarchy (H1, H2, H3).
• Use descriptive link text instead of generic phrases like "Click Here."
• Use readable font sizes (16px or larger is commonly recommended).
• Design responsive emails that adapt to different screen sizes.
• Avoid placing important information inside images.
• Ensure buttons are large enough to be easily selected on mobile devices.
• Keep layouts simple and easy to navigate.
• Use sufficient spacing between clickable elements.

Accessibility Testing Tools

• axe DevTools – Automated accessibility testing.
• WAVE – Evaluates web accessibility and highlights issues.
• NVDA – Free Windows screen reader used for accessibility testing.
• JAWS – Commercial screen reader commonly used by organizations.
• Email on Acid – Validates email accessibility and rendering.
• Litmus – Tests accessibility and rendering across email clients.

QA Responsibilities

• Verify meaningful ALT text is provided for all informative images.
• Validate colour contrast meets WCAG 2.1 AA requirements.
• Ensure heading structure follows a logical hierarchy.
• Verify descriptive hyperlinks and CTA buttons.
• Confirm responsive layouts on desktop and mobile devices.
• Ensure emails remain readable when images are disabled.
• Validate screen reader compatibility where applicable.
• Review keyboard accessibility for landing pages and CloudPages.
• Perform accessibility testing using approved tools.
• Document and report accessibility defects before production.

Common Accessibility Defects

• Missing ALT text on images.
• Poor colour contrast.
• Incorrect heading hierarchy.
• Images containing important text with no text alternative.
• Very small font sizes.
• Generic hyperlinks such as "Click Here."
• Buttons too small for mobile devices.
• Email unreadable when images are blocked.
• Screen readers reading content incorrectly.

Example Accessibility Checklist

• ✔ ALT text verified.
• ✔ Colour contrast validated.
• ✔ Headings structured correctly.
• ✔ Links are descriptive.
• ✔ Responsive layout tested.
• ✔ Screen reader compatibility reviewed.
• ✔ Images disabled test completed.
• ✔ CTA buttons accessible on desktop and mobile.
• ✔ Email passes accessibility validation tools.

Email Testing Tools

Before any email campaign is released to production, it should undergo thorough testing to ensure it renders correctly, functions as expected, meets accessibility standards, and provides a consistent customer experience across email clients and devices. Salesforce Marketing Cloud supports built-in testing capabilities, while third-party tools provide additional validation for rendering, accessibility, and cross-platform compatibility.

As a QA/QC Auditor, using the appropriate testing tools helps identify defects before production, reducing the risk of broken emails, incorrect personalization, or accessibility issues reaching customers.

Common Email Testing Tools

1. Preview & Test (Salesforce Marketing Cloud)

Preview & Test is Salesforce Marketing Cloud's built-in testing feature. It allows QA teams to preview emails using actual subscriber data before sending them to customers.

• Validate merge fields.
• Test AMPscript personalization.
• Preview Dynamic Content.
• Verify customer-specific messaging.
• Send test emails to reviewers.

2. Email on Acid

Email on Acid is a specialized email testing platform that validates how emails render across dozens of email clients, browsers, and mobile devices. It also provides accessibility testing, link validation, image verification, and spam analysis.

• Cross-client rendering.
• Accessibility validation.
• Broken link detection.
• Image verification.
• Dark mode preview.
• Spam filter testing.

3. Litmus

Litmus provides many of the same rendering capabilities as Email on Acid but also includes collaboration features that allow marketing, design, and QA teams to review, comment on, and approve emails before production.

• Email rendering across clients.
• Accessibility testing.
• Team collaboration and approvals.
• Email proofing.
• Post-send engagement analytics.

4. BrowserStack

BrowserStack is primarily used for testing web pages rather than email rendering. Within Salesforce Marketing Cloud, it is commonly used to validate CloudPages, landing pages, preference centers, and forms across multiple browsers and devices.

• Responsive layout testing.
• Cross-browser compatibility.
• Mobile device testing.
• CloudPages validation.
• Landing page QA.

QA Responsibilities

• Validate merge fields and personalization.
• Verify AMPscript executes correctly.
• Confirm Dynamic Content displays correctly.
• Validate links and CTA buttons.
• Verify images render correctly.
• Review HTML and CSS rendering.
• Test mobile responsiveness.
• Validate accessibility (WCAG 2.1 AA).
• Test dark mode rendering where applicable.
• Confirm compatibility across major email clients.
• Document and resolve defects before production.

Common Defects Found Using Testing Tools

• Broken personalization.
• AMPscript errors.
• Incorrect Dynamic Content.
• Broken hyperlinks.
• Missing images.
• Poor Outlook rendering.
• Accessibility violations.
• Dark mode display issues.
• Responsive layout problems.
• Spam trigger warnings.

SQL Queries in Salesforce Marketing Cloud

Structured Query Language (SQL) is one of the most commonly used tools within Salesforce Marketing Cloud. SQL Query Activities in Automation Studio retrieve, filter, join, and transform data stored in Data Extensions. As a QA/QC Auditor, you should understand how SQL is used to validate customer data, build audiences, remove duplicates, and verify campaign readiness.

1. Select All Records

Retrieve every record from a Data Extension.

SELECT *
FROM Customers

2. Select Specific Columns

SELECT
    FirstName,
    LastName,
    EmailAddress
FROM Customers

3. Filter Records

SELECT *
FROM Customers
WHERE Province = 'Ontario'

4. Multiple Conditions

SELECT *
FROM Customers
WHERE Province = 'Ontario'
AND Status = 'Active'

5. OR Condition

SELECT *
FROM Customers
WHERE Province = 'Ontario'
OR Province = 'Quebec'

6. Sort Records

SELECT *
FROM Customers
ORDER BY LastName ASC

7. Remove Duplicate Records

SELECT DISTINCT EmailAddress
FROM Customers

8. Count Records

SELECT COUNT(*) AS TotalCustomers
FROM Customers

9. Count Records by Group

SELECT
    Province,
    COUNT(*) AS CustomerCount
FROM Customers
GROUP BY Province

10. Find Duplicate Email Addresses

SELECT
    EmailAddress,
    COUNT(*) AS DuplicateCount
FROM Customers
GROUP BY EmailAddress
HAVING COUNT(*) > 1

11. INNER JOIN

Return matching records from two Data Extensions.

SELECT
    c.FirstName,
    c.EmailAddress,
    o.OrderNumber
FROM Customers c
INNER JOIN Orders o
ON c.CustomerID = o.CustomerID

12. LEFT JOIN

Return all customers, even if no matching order exists.

SELECT
    c.FirstName,
    o.OrderNumber
FROM Customers c
LEFT JOIN Orders o
ON c.CustomerID = o.CustomerID

13. Find Customers Without Orders

SELECT
    c.CustomerID,
    c.FirstName
FROM Customers c
LEFT JOIN Orders o
ON c.CustomerID = o.CustomerID
WHERE o.CustomerID IS NULL

14. Exclude Suppression List

SELECT
    c.*
FROM Customers c
LEFT JOIN SuppressionList s
ON c.EmailAddress = s.EmailAddress
WHERE s.EmailAddress IS NULL

15. Filter by Date

SELECT *
FROM Customers
WHERE CreatedDate >= '2026-01-01'

16. Last 30 Days

SELECT *
FROM Customers
WHERE CreatedDate >= DATEADD(day,-30,GETDATE())

17. Top Records

SELECT TOP 100 *
FROM Customers

18. Active Subscribers

SELECT *
FROM Customers
WHERE Status = 'Active'

19. Customers with Marketing Consent

SELECT *
FROM Customers
WHERE MarketingConsent = 'Yes'

20. Audience Segmentation

SELECT
    FirstName,
    EmailAddress,
    LoyaltyLevel
FROM Customers
WHERE LoyaltyLevel = 'Gold'

Common SQL Functions

QA Responsibilities

• Validate SQL syntax before execution.
• Verify the correct Data Extensions are referenced.
• Confirm record counts match business expectations.
• Validate JOIN conditions return the correct audience.
• Verify duplicate Contact Keys and Email Addresses are removed.
• Confirm suppression and exclusion lists are applied.
• Validate customer consent filters (CASL/GDPR).
• Review SQL Query Activity execution logs.
• Verify output Data Extensions contain the expected records.
• Perform regression testing before production deployment.

Quality Assurance (QA) Checklist

A Quality Assurance (QA) Checklist is a structured list of validation activities performed before an email campaign is approved for production. The goal is to identify defects early, ensure customer communications are accurate, compliant, accessible, and deliver a consistent experience across all email clients and devices.

As an SFMC QA/QC Auditor, the checklist helps verify every aspect of a campaign, from audience selection and personalization to rendering, accessibility, and compliance, reducing the risk of production issues.

1. Audience & Data Validation

• Verify the correct audience is selected.
• Confirm Data Extensions contain accurate customer data.
• Validate audience segmentation.
• Verify Contact Keys are unique.
• Confirm customer consent (CASL/GDPR).
• Validate suppression and exclusion lists.
• Review SQL query results and audience counts.

2. Personalization & AMPscript

• Verify merge fields display correctly.
• Validate AMPscript executes without errors.
• Confirm fallback values are displayed when data is missing.
• Test Dynamic Content for every audience scenario.
• Ensure no raw AMPscript or merge tags appear in the email.

3. Email Content Validation

• Verify subject line accuracy.
• Validate preheader text.
• Review email copy for grammar and spelling.
• Confirm branding and corporate design standards.
• Validate images and logos.
• Verify CTA buttons and hyperlinks.
• Ensure legal disclaimer and company contact information are present.

4. HTML & Rendering Validation

• Validate HTML structure.
• Verify CSS renders correctly.
• Confirm responsive behaviour on desktop and mobile.
• Test Outlook rendering.
• Validate Gmail, Apple Mail, Yahoo Mail, and mobile clients.
• Review dark mode rendering where supported.

5. Accessibility Validation (WCAG 2.1 AA)

• Verify meaningful ALT text for images.
• Validate colour contrast.
• Confirm logical heading hierarchy.
• Review descriptive hyperlinks.
• Ensure readable font sizes.
• Confirm screen reader compatibility.
• Verify responsive layouts.

6. Journey Builder Validation

• Validate Entry Source.
• Verify Decision Splits.
• Confirm Wait Activities.
• Validate Exit Criteria.
• Test complete customer journey.
• Ensure customers follow the correct journey path.

7. Automation Studio Validation

• Verify automation schedules.
• Confirm successful data imports.
• Validate SQL Query Activities.
• Refresh Data Extensions.
• Review automation logs.
• Verify failure notifications.

8. Compliance Validation

• Verify unsubscribe link.
• Confirm Privacy Policy link.
• Validate sender information.
• Review Send Classification.
• Confirm customer consent.
• Verify suppression lists.

9. Testing Tools Validation

• Preview & Test completed.
• Email on Acid validation passed.
• Litmus rendering review completed.
• BrowserStack validation completed (CloudPages/Landing Pages).

10. Production Readiness

• Business approval received.
• QA defects resolved.
• Regression testing completed.
• Production deployment approved.
• Campaign scheduled.
• Post-deployment monitoring planned.

Complete Production QA Checklist

• ☐ Audience validated
• ☐ Data Extensions verified
• ☐ SQL queries validated
• ☐ Contact Keys reviewed
• ☐ Customer consent confirmed
• ☐ Suppression lists applied
• ☐ Subject line approved
• ☐ Preheader verified
• ☐ Merge fields tested
• ☐ AMPscript validated
• ☐ Dynamic Content tested
• ☐ Images verified
• ☐ Links tested
• ☐ CTA buttons verified
• ☐ HTML validated
• ☐ CSS rendering verified
• ☐ Mobile responsiveness tested
• ☐ Accessibility passed
• ☐ Outlook rendering verified
• ☐ Gmail rendering verified
• ☐ Email on Acid completed
• ☐ Litmus review completed
• ☐ Journey Builder validated
• ☐ Automation Studio validated
• ☐ Unsubscribe link verified
• ☐ Business approval received
• ☐ QA/QC sign-off completed

What is Spam?

Spam refers to unsolicited or unwanted email messages sent to recipients without their permission. Internet Service Providers (ISPs) such as Gmail, Outlook, and Yahoo use sophisticated filtering systems to determine whether an email should be delivered to the inbox, sent to the junk folder, or blocked entirely.

Why Spam Matters

Even a professionally designed email campaign can fail if spam filters determine that the message is suspicious. High spam rates reduce email deliverability, damage sender reputation, and can result in emails being blocked from reaching customers.

Common Causes of Spam

Spam Prevention Best Practices

• Send emails only to customers who have provided consent.
• Maintain a healthy sender reputation.
• Authenticate domains using SPF, DKIM, and DMARC.
• Avoid excessive capitalization and punctuation.
• Balance text and images.
• Always include a working unsubscribe link.
• Validate all hyperlinks before deployment.
• Personalize content using AMPscript or Dynamic Content.
• Keep email HTML clean and standards compliant.
• Regularly remove inactive subscribers.

Spam Testing in Salesforce Marketing Cloud

Before deployment, QA teams perform spam testing to identify issues that may affect inbox placement. Spam testing tools evaluate content, HTML structure, authentication, links, and sender reputation.

QA Responsibilities

• Validate sender authentication (SPF, DKIM, DMARC).
• Verify unsubscribe and preference center links.
• Check HTML for rendering issues.
• Review email content for spam trigger words.
• Test all hyperlinks and images.
• Validate personalization and AMPscript.
• Run spam analysis before production deployment.
• Confirm email accessibility and mobile responsiveness.
• Monitor bounce and complaint rates after deployment.

Salesforce Marketing Cloud HTML Email Template

Below is a simplified production-style HTML email template similar to what is commonly developed and tested within Salesforce Marketing Cloud. This example demonstrates responsive email structure, AMPscript personalization, dynamic content, branded styling, and compliance links.

Email Flow

Key Components

• Responsive HTML Email
• Table-based Layout
• AMPscript Personalization
• Dynamic Merge Fields
• CTA Button
• Company Branding
• Footer with Compliance Links
• Unsubscribe Link
• Preference Center

Complete HTML Email

<!DOCTYPE html>
<html>

<head>

...

%%[
SET @FirstName = AttributeValue("FirstName")
SET @RenewalDate = AttributeValue("RenewalDate")
]%%

Hello

%%=IIF(
EMPTY(@FirstName),
"Valued Customer",
@FirstName
)=%%

Your mortgage renewal date is

%%=FormatDate(@RenewalDate,"MMMM d, yyyy")=%%

<a href="%%=RedirectTo('https://www.sfmcbank.com/mortgage')=%%">

Renew Now

</a>

%%profile_center_url%%

%%unsub_center_url%%

</html>

What This Template Demonstrates

QA Responsibilities

• Validate HTML renders correctly.
• Verify AMPscript executes successfully.
• Confirm personalization displays correctly.
• Validate merge fields.
• Test CTA button.
• Verify RedirectTo() tracking.
• Validate images.
• Test Outlook rendering.
• Verify Gmail rendering.
• Validate mobile responsiveness.
• Confirm accessibility.
• Validate unsubscribe functionality.
• Verify preference center link.
• Perform Email on Acid and Litmus testing.

Rendered Email Preview

The preview below shows how the customer would see the email after Salesforce Marketing Cloud processes the AMPscript and personalization.