MC Email Specialist Interview Questions
25 expert-curated questions covering email design, deliverability, SPF/DKIM/DMARC, A/B testing, and Journey Builder.
MC Email Specialist Interview Questions
Width: Use a max-width of 600px — most email clients, especially Outlook on Windows, render best at this width. Tables are still recommended for layout to handle Outlook's Word-based renderer.
CSS: Inline CSS is the most widely supported method. Embedded styles (<style> in <head>) are stripped by some clients (older Gmail, some mobile). External CSS is not supported in email.
Fonts: Use web-safe font stacks (Arial, Georgia, Times New Roman) with web font declarations (
Preheader text: Keep it 85–100 characters to display well across clients; hide any filler text using display:none or mso-hide:all.
Images: Always provide descriptive alt text. Many clients block images by default — the email must be readable without images.
Plain text: Always include a plain text version; some ESPs and spam filters penalise HTML-only emails.
CSS: Inline CSS is the most widely supported method. Embedded styles (<style> in <head>) are stripped by some clients (older Gmail, some mobile). External CSS is not supported in email.
Fonts: Use web-safe font stacks (Arial, Georgia, Times New Roman) with web font declarations (
@font-face or Google Fonts) first, falling back gracefully. Many Outlook versions do not support web fonts.Preheader text: Keep it 85–100 characters to display well across clients; hide any filler text using display:none or mso-hide:all.
Images: Always provide descriptive alt text. Many clients block images by default — the email must be readable without images.
Plain text: Always include a plain text version; some ESPs and spam filters penalise HTML-only emails.
Fluid (Liquid): Uses percentage-based widths so the email scales proportionally on any screen. No media queries required. Limitation: text can become too small or too wide without min/max-width constraints.
Hybrid (Spongy): Combines fluid percentage widths with max-width constraints using MSO conditional comments to fix Outlook rendering. The inner table uses
Responsive: Uses CSS media queries to change layout at breakpoints (e.g., stack columns below 600px). Works great in clients that support media queries (modern Gmail, Apple Mail, iOS Mail). Outlook desktop clients largely ignore media queries, so a hybrid fallback is still needed.
Outlook VML: Microsoft Outlook uses VML (Vector Markup Language) for background images and gradient fills — standard CSS background-image is ignored.
Hybrid (Spongy): Combines fluid percentage widths with max-width constraints using MSO conditional comments to fix Outlook rendering. The inner table uses
width:100% and max-width in CSS, while Outlook sees a fixed-pixel table via VML/conditional comments. This is the most widely compatible approach today.Responsive: Uses CSS media queries to change layout at breakpoints (e.g., stack columns below 600px). Works great in clients that support media queries (modern Gmail, Apple Mail, iOS Mail). Outlook desktop clients largely ignore media queries, so a hybrid fallback is still needed.
Outlook VML: Microsoft Outlook uses VML (Vector Markup Language) for background images and gradient fills — standard CSS background-image is ignored.
Content Builder uses a folder hierarchy for organisation (similar to a file system). Tags provide a cross-folder labelling system for quick filtering. Shared content lives in a parent Business Unit and is accessible to child BUs. Global content is locked content shared across BUs that child BUs cannot edit.
Content block types:
— HTML block: Raw HTML for complete custom control.
— Text block: Plain text or rich-text editor content.
— Image block: Hosted or external image with alt text and link.
— Button block: Styled CTA button with configurable colours and URL.
— Dynamic content block: Rule-based or AMPscript-powered content variation block.
— A/B test block: Two or more content variants for split testing within a single email slot.
Content block types:
— HTML block: Raw HTML for complete custom control.
— Text block: Plain text or rich-text editor content.
— Image block: Hosted or external image with alt text and link.
— Button block: Styled CTA button with configurable colours and URL.
— Dynamic content block: Rule-based or AMPscript-powered content variation block.
— A/B test block: Two or more content variants for split testing within a single email slot.
Template-based emails in Content Builder use a template that defines the structural layout — headers, footers, column arrangements. The template defines content slots (also called content areas or editable regions).
Locked regions: Areas defined in the template that child email creators cannot modify. Typically used for brand-mandated headers, footers, and legal disclaimers. Locked via the
Unlocked regions: Slots where email creators can drag-and-drop content blocks (images, text, buttons, dynamic blocks). Each slot has a defined content type restriction (e.g., image only, any block).
This structure ensures brand consistency while giving content creators flexibility. Super content blocks can be inserted into templates as globally locked brand elements editable only by admins.
Locked regions: Areas defined in the template that child email creators cannot modify. Typically used for brand-mandated headers, footers, and legal disclaimers. Locked via the
locking property in the template code.Unlocked regions: Slots where email creators can drag-and-drop content blocks (images, text, buttons, dynamic blocks). Each slot has a defined content type restriction (e.g., image only, any block).
This structure ensures brand consistency while giving content creators flexibility. Super content blocks can be inserted into templates as globally locked brand elements editable only by admins.
Rule-based dynamic content uses the Content Builder UI to define conditions (profile attributes or sendable DE field values) and map each condition to a specific content block variant. Rules are evaluated top-to-bottom; the first matching rule's content is rendered. A default block is shown when no rule matches. This approach requires no code and is ideal for marketers.
AMPscript-based dynamic content uses IF/ELSEIF/ELSE logic inside an HTML content block to conditionally render different HTML sections, call different ContentBlockByKey(), or output different personalisation tokens. This is more flexible and can reference multiple DE lookups, complex computed conditions, and nested logic. Use AMPscript when rule-based conditions are insufficient or when the number of variants is large.
AMPscript-based dynamic content uses IF/ELSEIF/ELSE logic inside an HTML content block to conditionally render different HTML sections, call different ContentBlockByKey(), or output different personalisation tokens. This is more flexible and can reference multiple DE lookups, complex computed conditions, and nested logic. Use AMPscript when rule-based conditions are insufficient or when the number of variants is large.
Deliverability is the ability of an email to reach the recipient's inbox (not spam folder). Key factors:
Sender reputation: Composite score based on IP reputation, domain reputation, engagement rates, spam complaints, and bounce rates.
IP reputation: The sending IP address's history of sending behaviour. New or unwarmed IPs have no reputation — they must be warmed up gradually.
Domain reputation: The From domain's sending history. Major MBPs (Gmail, Yahoo, Outlook.com) now weight domain reputation more heavily than IP reputation.
Authentication: Valid SPF, DKIM, and DMARC alignment are increasingly required by major MBPs. Gmail and Yahoo mandated these from February 2024 for bulk senders.
Content: Spam trigger words, image-to-text ratio, link quality, and HTML coding issues affect spam filter scoring.
Engagement: High open/click rates and low unsubscribe/complaint rates signal to MBPs that recipients want the mail.
Sender reputation: Composite score based on IP reputation, domain reputation, engagement rates, spam complaints, and bounce rates.
IP reputation: The sending IP address's history of sending behaviour. New or unwarmed IPs have no reputation — they must be warmed up gradually.
Domain reputation: The From domain's sending history. Major MBPs (Gmail, Yahoo, Outlook.com) now weight domain reputation more heavily than IP reputation.
Authentication: Valid SPF, DKIM, and DMARC alignment are increasingly required by major MBPs. Gmail and Yahoo mandated these from February 2024 for bulk senders.
Content: Spam trigger words, image-to-text ratio, link quality, and HTML coding issues affect spam filter scoring.
Engagement: High open/click rates and low unsubscribe/complaint rates signal to MBPs that recipients want the mail.
SPF (Sender Policy Framework) is a DNS TXT record on the sending domain that lists the IP addresses and mail servers authorised to send email on behalf of that domain. Receiving servers look up the sending domain's SPF record and verify that the sending IP is listed.
include mechanism: Delegates to another domain's SPF record. Marketing Cloud SAP requires adding
~all (softfail): IPs not listed should be treated with suspicion but still accepted. Most MBPs accept softfail mail but may apply a spam score penalty. Recommended for initial SPF rollout.
-all (hardfail): IPs not listed should be rejected outright. Use -all once you are confident all legitimate sending sources are enumerated. SPF lookup limit is 10 DNS lookups — exceeding this causes a PermError.
include mechanism: Delegates to another domain's SPF record. Marketing Cloud SAP requires adding
include:cust-spf.exacttarget.com to your SPF record.~all (softfail): IPs not listed should be treated with suspicion but still accepted. Most MBPs accept softfail mail but may apply a spam score penalty. Recommended for initial SPF rollout.
-all (hardfail): IPs not listed should be rejected outright. Use -all once you are confident all legitimate sending sources are enumerated. SPF lookup limit is 10 DNS lookups — exceeding this causes a PermError.
DKIM (DomainKeys Identified Mail) adds a cryptographic digital signature to the email header. The sending server signs outgoing mail with a private key; the public key is published as a DNS TXT record at
Alignment: DMARC requires DKIM alignment — the
Relaxed vs strict alignment: Relaxed allows subdomain matching; strict requires exact domain match.
selector._domainkey.domain.com. Receiving servers retrieve the public key and verify the signature — confirming the email has not been tampered with in transit and originated from an authorised sender.Alignment: DMARC requires DKIM alignment — the
d= domain in the DKIM signature must match (or be a subdomain of) the RFC5322 From header domain. When Marketing Cloud sends with its own DKIM key (@exacttarget.com), DKIM alignment with your From domain fails. The Sender Authentication Package (SAP) provides your own private domain and DKIM keys, enabling proper alignment.Relaxed vs strict alignment: Relaxed allows subdomain matching; strict requires exact domain match.
DMARC (Domain-based Message Authentication, Reporting, and Conformance) is a DNS TXT record at
p=none: Monitor mode — no action taken on failing messages; aggregate reports (rua) and forensic reports (ruf) are sent to the specified email. Used during initial deployment to identify legitimate sending sources.
p=quarantine: Failing messages are routed to the spam/junk folder. Intermediate enforcement step.
p=reject: Failing messages are outright rejected and not delivered. Full protection against domain spoofing.
BIMI requirement: Brand Indicators for Message Identification (BIMI) — which displays your brand logo in supporting inboxes — requires
pct: Percentage of failing mail to apply the policy to (default 100). Useful for gradual rollout.
_dmarc.domain.com that specifies what receiving mail servers should do when a message fails SPF and DKIM alignment checks.p=none: Monitor mode — no action taken on failing messages; aggregate reports (rua) and forensic reports (ruf) are sent to the specified email. Used during initial deployment to identify legitimate sending sources.
p=quarantine: Failing messages are routed to the spam/junk folder. Intermediate enforcement step.
p=reject: Failing messages are outright rejected and not delivered. Full protection against domain spoofing.
BIMI requirement: Brand Indicators for Message Identification (BIMI) — which displays your brand logo in supporting inboxes — requires
p=quarantine or p=reject DMARC enforcement and a Verified Mark Certificate (VMC) for Gmail.pct: Percentage of failing mail to apply the policy to (default 100). Useful for gradual rollout.
IP warming is the process of gradually increasing sending volume from a new or cold IP address to build a positive sending reputation with ISPs before sending full volume.
Typical ramp-up: Start with 500–1,000 emails/day to your most engaged subscribers (opened in last 30 days). Double volume roughly every 2–3 days, targeting engaged segments before the broader list.
Seed lists: Include internal seed addresses at major MBPs (Gmail, Yahoo, Outlook.com) to monitor inbox placement during warm-up.
Metrics to monitor:
— Bounce rate: should stay below 2% (hard bounces under 0.5%).
— Spam complaint rate: must stay below 0.08% (Gmail threshold); above 0.3% causes serious reputation damage.
— Open rate: target at least 20% from warmed segments.
— Spam trap hits: monitored via tools like Validity/Return Path.
— Inbox placement rate: percentage landing in inbox vs spam vs missing. Target above 90%.
Typical ramp-up: Start with 500–1,000 emails/day to your most engaged subscribers (opened in last 30 days). Double volume roughly every 2–3 days, targeting engaged segments before the broader list.
Seed lists: Include internal seed addresses at major MBPs (Gmail, Yahoo, Outlook.com) to monitor inbox placement during warm-up.
Metrics to monitor:
— Bounce rate: should stay below 2% (hard bounces under 0.5%).
— Spam complaint rate: must stay below 0.08% (Gmail threshold); above 0.3% causes serious reputation damage.
— Open rate: target at least 20% from warmed segments.
— Spam trap hits: monitored via tools like Validity/Return Path.
— Inbox placement rate: percentage landing in inbox vs spam vs missing. Target above 90%.
Shared IP: Multiple senders share the same sending IP address. Reputation is influenced by all senders on that IP. Marketing Cloud's shared IP pools are managed by Salesforce and are pre-warmed. Suitable for lower-volume senders (typically below 50,000 emails/month) who cannot maintain sufficient volume to keep a dedicated IP warm.
Dedicated IP: A single IP address reserved exclusively for your organisation's sends. Your reputation is entirely determined by your own sending practices. Requires deliberate warming from cold. Typically recommended for senders above 50,000–100,000 emails/month who send consistently (at least weekly). Multiple dedicated IPs can be grouped into an IP pool for load distribution.
Key consideration: If you stop sending on a dedicated IP for more than 30 days, the reputation fades and the IP effectively goes cold again, requiring re-warming.
Dedicated IP: A single IP address reserved exclusively for your organisation's sends. Your reputation is entirely determined by your own sending practices. Requires deliberate warming from cold. Typically recommended for senders above 50,000–100,000 emails/month who send consistently (at least weekly). Multiple dedicated IPs can be grouped into an IP pool for load distribution.
Key consideration: If you stop sending on a dedicated IP for more than 30 days, the reputation fades and the IP effectively goes cold again, requiring re-warming.
Hard bounce (permanent): The receiving server permanently rejects the email — the address does not exist or the domain is invalid. Marketing Cloud automatically sets the subscriber status to Undeliverable after 1 hard bounce. Threshold: keep hard bounce rate below 0.5%.
Soft bounce (temporary): A temporary delivery failure — mailbox full, server temporarily unavailable, message too large. Marketing Cloud retries soft bounces up to 4 times over 72 hours before marking as undeliverable. Threshold: keep below 4%.
Blocked bounce: The receiving server or ISP actively blocked delivery, often due to IP/domain blacklisting or content filtering. Indicates a reputation problem.
Technical bounce: Miscellaneous technical errors (DNS failures, connection timeouts). Should be monitored but don't necessarily indicate a list quality issue.
Soft bounce (temporary): A temporary delivery failure — mailbox full, server temporarily unavailable, message too large. Marketing Cloud retries soft bounces up to 4 times over 72 hours before marking as undeliverable. Threshold: keep below 4%.
Blocked bounce: The receiving server or ISP actively blocked delivery, often due to IP/domain blacklisting or content filtering. Indicates a reputation problem.
Technical bounce: Miscellaneous technical errors (DNS failures, connection timeouts). Should be monitored but don't necessarily indicate a list quality issue.
Global unsubscribe (All Subscribers list): The subscriber is marked as globally unsubscribed across all commercial sends from the entire Marketing Cloud account. They will not receive any commercial email regardless of which list or DE they appear in.
Publication list unsubscribe: The subscriber opts out of a specific publication list (email category/topic). They still receive emails from other publication lists. Enables a preference centre experience where subscribers manage their communication preferences.
One-click unsubscribe (RFC 8058 / List-Unsubscribe-Post): A machine-actionable unsubscribe mechanism required by Gmail and Yahoo since February 2024 for bulk senders (>5,000/day). The email header includes a
Publication list unsubscribe: The subscriber opts out of a specific publication list (email category/topic). They still receive emails from other publication lists. Enables a preference centre experience where subscribers manage their communication preferences.
One-click unsubscribe (RFC 8058 / List-Unsubscribe-Post): A machine-actionable unsubscribe mechanism required by Gmail and Yahoo since February 2024 for bulk senders (>5,000/day). The email header includes a
List-Unsubscribe-Post header; email clients expose a native unsubscribe button that POSTs directly to the unsubscribe endpoint without the subscriber needing to click a link in the email body. Marketing Cloud SAP enables this automatically.
CAN-SPAM (Controlling the Assault of Non-Solicited Pornography And Marketing Act) applies to commercial email sent to US recipients:
1. Honest From header: The From name and address must accurately identify the sender.
2. Honest subject line: Must not be deceptive or misleading about the email's contents.
3. Physical address: A valid postal address (or PO box) of the sending organisation must be included in the email body.
4. Opt-out mechanism: A clear and conspicuous way for recipients to unsubscribe must be present in every commercial email.
5. Honour opt-outs within 10 business days: Unsubscribe requests must be processed within 10 business days; you cannot require the subscriber to pay a fee or provide information beyond their email address.
6. Transactional exemption: Transactional emails (order confirmations, password resets) are largely exempt from CAN-SPAM requirements but must still not be deceptive.
1. Honest From header: The From name and address must accurately identify the sender.
2. Honest subject line: Must not be deceptive or misleading about the email's contents.
3. Physical address: A valid postal address (or PO box) of the sending organisation must be included in the email body.
4. Opt-out mechanism: A clear and conspicuous way for recipients to unsubscribe must be present in every commercial email.
5. Honour opt-outs within 10 business days: Unsubscribe requests must be processed within 10 business days; you cannot require the subscriber to pay a fee or provide information beyond their email address.
6. Transactional exemption: Transactional emails (order confirmations, password resets) are largely exempt from CAN-SPAM requirements but must still not be deceptive.
GDPR (General Data Protection Regulation) applies to email marketing to EU/EEA residents. Key impacts:
Lawful basis: You need a valid lawful basis to send marketing email. For most marketing, this is consent (freely given, specific, informed, unambiguous). Other bases (legitimate interest, contractual necessity) are less reliable for direct marketing.
Consent records: You must be able to demonstrate when, how, and what the subscriber consented to. Store consent timestamps and source in a DE. Marketing Cloud's preference centre can capture and store this.
Right to erasure (Right to be Forgotten): When a subscriber requests deletion, you must remove their personal data from Marketing Cloud — subscriber record, all DEs containing their data, and ensure they are suppressed from future sends. Marketing Cloud's contact deletion API (
Data minimisation: Only collect and store data necessary for the declared purpose.
Lawful basis: You need a valid lawful basis to send marketing email. For most marketing, this is consent (freely given, specific, informed, unambiguous). Other bases (legitimate interest, contractual necessity) are less reliable for direct marketing.
Consent records: You must be able to demonstrate when, how, and what the subscriber consented to. Store consent timestamps and source in a DE. Marketing Cloud's preference centre can capture and store this.
Right to erasure (Right to be Forgotten): When a subscriber requests deletion, you must remove their personal data from Marketing Cloud — subscriber record, all DEs containing their data, and ensure they are suppressed from future sends. Marketing Cloud's contact deletion API (
POST /contacts/v1/contacts/actions/delete) handles this.Data minimisation: Only collect and store data necessary for the declared purpose.
A/B testing in Content Builder allows splitting your send audience to test up to 10 variants before sending the winner to the remainder.
Test variables:
— Subject line (most commonly tested)
— From name
— Email content (different content block variants)
— Send time (with or without Einstein STO)
Test setup: Define the test percentage (e.g., 10% to each variant) and the winner determination period (e.g., 4 hours after send).
Winner criteria:
— Open rate (unique opens)
— Click rate (unique clicks)
— Revenue (if MC is integrated with Commerce Cloud or e-commerce tracking)
Automatic winner send: After the winner determination period, Marketing Cloud automatically sends the winning variant to the remaining audience. Results include statistical confidence metrics to validate significance.
Test variables:
— Subject line (most commonly tested)
— From name
— Email content (different content block variants)
— Send time (with or without Einstein STO)
Test setup: Define the test percentage (e.g., 10% to each variant) and the winner determination period (e.g., 4 hours after send).
Winner criteria:
— Open rate (unique opens)
— Click rate (unique clicks)
— Revenue (if MC is integrated with Commerce Cloud or e-commerce tracking)
Automatic winner send: After the winner determination period, Marketing Cloud automatically sends the winning variant to the remaining audience. Results include statistical confidence metrics to validate significance.
Automation Studio supports several schedule types for automations:
Scheduled: Run once, daily, weekly, or monthly at a specified time. Supports time zone selection.
File Drop (Triggered): The automation starts automatically when a specific file is uploaded to a designated SFTP folder. The file name can be an exact match or a wildcard pattern. Ideal for data-import-triggered workflows (e.g., import a new segment file and immediately send an email).
Wait Activity: Pauses the automation for a specified duration before the next step. Used to sequence activities (e.g., import, wait 15 minutes, query, then send).
Run Once: Manually triggered or scheduled for a one-time execution. Automation activities within a single run execute sequentially in defined order.
Scheduled: Run once, daily, weekly, or monthly at a specified time. Supports time zone selection.
File Drop (Triggered): The automation starts automatically when a specific file is uploaded to a designated SFTP folder. The file name can be an exact match or a wildcard pattern. Ideal for data-import-triggered workflows (e.g., import a new segment file and immediately send an email).
Wait Activity: Pauses the automation for a specified duration before the next step. Used to sequence activities (e.g., import, wait 15 minutes, query, then send).
Run Once: Manually triggered or scheduled for a one-time execution. Automation activities within a single run execute sequentially in defined order.
Journey Builder supports multiple entry source types:
Salesforce Data Entry: Contacts enter based on Salesforce CRM records (Contact, Lead, or custom object) meeting filter criteria, or when a record is created/updated.
API Event: External systems inject contacts via a REST API call to an EventDefinitionKey. Used for behavioural triggers (cart abandonment, form submission, purchase event).
Scheduled Audience: A data extension is evaluated at a scheduled time; all contacts in the DE (meeting filter criteria) enter the journey. Supports recurring schedules for re-entry.
Cloud Pages Form Capture: A Smart Capture form on a CloudPage can be an entry source — form submission directly injects the contact into a journey.
Inbound Chat/WhatsApp: For MC Personalisation or WhatsApp-enabled journeys (newer entry sources added with MC Growth/Advanced editions).
Salesforce Data Entry: Contacts enter based on Salesforce CRM records (Contact, Lead, or custom object) meeting filter criteria, or when a record is created/updated.
API Event: External systems inject contacts via a REST API call to an EventDefinitionKey. Used for behavioural triggers (cart abandonment, form submission, purchase event).
Scheduled Audience: A data extension is evaluated at a scheduled time; all contacts in the DE (meeting filter criteria) enter the journey. Supports recurring schedules for re-entry.
Cloud Pages Form Capture: A Smart Capture form on a CloudPage can be an entry source — form submission directly injects the contact into a journey.
Inbound Chat/WhatsApp: For MC Personalisation or WhatsApp-enabled journeys (newer entry sources added with MC Growth/Advanced editions).
Wait activities:
— Wait by Duration: Pauses for a fixed time period (hours/days/weeks).
— Wait Until Date: Pauses until a specific date/time field on the contact record.
Decision activities:
— Decision Split: Routes contacts down different paths based on data attribute conditions (up to 10 paths + default).
— Engagement Split: Routes based on whether a contact opened or clicked a previous email in the journey.
Einstein activities:
— Einstein Send Time Optimisation (STO): Delays each contact's email send to their individually predicted optimal send time within a window.
— Einstein Engagement Frequency: Suppresses contacts who are predicted to be over-messaged.
Other activities: Email send, SMS, Push Notification, Update Contact, Sales/Service Cloud Activity, Advertising Audience, Custom Split (via API activity).
— Wait by Duration: Pauses for a fixed time period (hours/days/weeks).
— Wait Until Date: Pauses until a specific date/time field on the contact record.
Decision activities:
— Decision Split: Routes contacts down different paths based on data attribute conditions (up to 10 paths + default).
— Engagement Split: Routes based on whether a contact opened or clicked a previous email in the journey.
Einstein activities:
— Einstein Send Time Optimisation (STO): Delays each contact's email send to their individually predicted optimal send time within a window.
— Einstein Engagement Frequency: Suppresses contacts who are predicted to be over-messaged.
Other activities: Email send, SMS, Push Notification, Update Contact, Sales/Service Cloud Activity, Advertising Audience, Custom Split (via API activity).
Delivery rate (delivered ÷ sent): Target >98%. Below 95% indicates list quality or deliverability issues.
Open rate (unique opens ÷ delivered): Industry average ~20–30% but heavily distorted by Apple Mail Privacy Protection (MPP) since 2021, which pre-loads tracking pixels. Use CTOR as a more reliable engagement signal.
CTOR (Click-to-Open Rate) (unique clicks ÷ unique opens): More meaningful than raw click rate post-MPP. Target >10–15%.
Bounce rate: Hard bounces <0.5%; soft bounces <4%.
Unsubscribe rate: Below 0.2% per send; above 0.5% signals content/frequency issues.
Complaint rate: Below 0.08% (Gmail FBL threshold from Feb 2024). Above 0.3% causes significant deliverability damage.
Spam placement rate: Monitored via inbox placement tools (Validity, GlockApps). Target <5% to spam.
Open rate (unique opens ÷ delivered): Industry average ~20–30% but heavily distorted by Apple Mail Privacy Protection (MPP) since 2021, which pre-loads tracking pixels. Use CTOR as a more reliable engagement signal.
CTOR (Click-to-Open Rate) (unique clicks ÷ unique opens): More meaningful than raw click rate post-MPP. Target >10–15%.
Bounce rate: Hard bounces <0.5%; soft bounces <4%.
Unsubscribe rate: Below 0.2% per send; above 0.5% signals content/frequency issues.
Complaint rate: Below 0.08% (Gmail FBL threshold from Feb 2024). Above 0.3% causes significant deliverability damage.
Spam placement rate: Monitored via inbox placement tools (Validity, GlockApps). Target <5% to spam.
Signals of subscriber fatigue:
— Steadily decreasing open rates over time for a segment
— Increasing unsubscribe and complaint rates
— Declining CTOR despite stable open rates
— Engagement Recency data showing subscribers who haven't opened in 60+ days
— Email client caching: Apple MPP pre-loads pixels, inflating open rates and masking true engagement decline
Mitigation strategies:
— Implement Einstein Engagement Frequency to auto-suppress over-messaged contacts
— Build a re-engagement journey for subscribers inactive for 60–90 days (win-back campaign)
— Offer a preference centre allowing subscribers to choose frequency/topics
— Sunset non-engagers: suppressed contacts inactive after 6–12 months improve deliverability for the active list
— Reduce send frequency for low-engagement segments while maintaining high-value content quality
— Steadily decreasing open rates over time for a segment
— Increasing unsubscribe and complaint rates
— Declining CTOR despite stable open rates
— Engagement Recency data showing subscribers who haven't opened in 60+ days
— Email client caching: Apple MPP pre-loads pixels, inflating open rates and masking true engagement decline
Mitigation strategies:
— Implement Einstein Engagement Frequency to auto-suppress over-messaged contacts
— Build a re-engagement journey for subscribers inactive for 60–90 days (win-back campaign)
— Offer a preference centre allowing subscribers to choose frequency/topics
— Sunset non-engagers: suppressed contacts inactive after 6–12 months improve deliverability for the active list
— Reduce send frequency for low-engagement segments while maintaining high-value content quality
Sender Profile: Defines the From Name, From Email address, and optional Reply-To address used in a send. Multiple sender profiles can be created for different brands or teams.
Delivery Profile: Specifies the physical mailing address (required by CAN-SPAM), header/footer, and IP address pool used for sending. The delivery profile determines which IP addresses are used.
Send Classification: Combines a Sender Profile, Delivery Profile, and classification type into a reusable configuration. The classification type is the most important property:
— Commercial: Respects the global unsubscribe list. Used for marketing email.
— Transactional: Does NOT respect the unsubscribe list. Used for order confirmations, password resets, and other transactional messages where the subscriber must receive the email regardless of opt-out status.
Choosing the wrong classification type can lead to legal issues (sending commercial email to unsubscribed users) or subscriber experience problems.
Delivery Profile: Specifies the physical mailing address (required by CAN-SPAM), header/footer, and IP address pool used for sending. The delivery profile determines which IP addresses are used.
Send Classification: Combines a Sender Profile, Delivery Profile, and classification type into a reusable configuration. The classification type is the most important property:
— Commercial: Respects the global unsubscribe list. Used for marketing email.
— Transactional: Does NOT respect the unsubscribe list. Used for order confirmations, password resets, and other transactional messages where the subscriber must receive the email regardless of opt-out status.
Choosing the wrong classification type can lead to legal issues (sending commercial email to unsubscribed users) or subscriber experience problems.
Marketing Cloud Connect integrates Marketing Cloud with a Salesforce CRM org, enabling data synchronisation and Journey Builder triggers based on CRM events.
Configuration: Requires a Connected App in the Salesforce CRM org with OAuth credentials, and the MC Connect managed package installed in CRM.
Synchronized Data Sources: CRM objects are synced to read-only data extensions in Marketing Cloud on a configurable schedule (near real-time for supported objects). Supported objects include: Contact, Lead, User, Account, Campaign, Campaign Member, and custom objects (with configuration).
Journey Builder Salesforce Entry: Contacts/Leads enter a journey when a CRM record meets defined criteria.
Sales/Service Cloud Activity: Journey steps can create Tasks, update fields, or log activity in CRM as a contact progresses through a journey.
Token management: OAuth tokens must be refreshed; expired tokens cause sync failures — monitor via the Salesforce Connector page in Marketing Cloud Setup.
Configuration: Requires a Connected App in the Salesforce CRM org with OAuth credentials, and the MC Connect managed package installed in CRM.
Synchronized Data Sources: CRM objects are synced to read-only data extensions in Marketing Cloud on a configurable schedule (near real-time for supported objects). Supported objects include: Contact, Lead, User, Account, Campaign, Campaign Member, and custom objects (with configuration).
Journey Builder Salesforce Entry: Contacts/Leads enter a journey when a CRM record meets defined criteria.
Sales/Service Cloud Activity: Journey steps can create Tasks, update fields, or log activity in CRM as a contact progresses through a journey.
Token management: OAuth tokens must be refreshed; expired tokens cause sync failures — monitor via the Salesforce Connector page in Marketing Cloud Setup.
Einstein STO analyses each subscriber's historical email engagement data (opens, clicks) to predict the time of day and day of week when that individual is most likely to engage with email. The Journey Builder Einstein STO activity holds each contact's message delivery until their predicted optimal send window.
How it works:
1. Einstein models analyse up to 90 days of engagement history per subscriber.
2. A send window is defined (e.g., deliver within the next 7 days).
3. The contact waits at the STO activity until their predicted optimal time within the window.
4. If a subscriber has insufficient history, they are sent at the default time or a random time within the window.
Requirements: Requires Einstein Engagement Scoring licence. Needs at least 6 months of send data from the same MID for meaningful predictions. Not suitable for time-sensitive transactional messages.
How it works:
1. Einstein models analyse up to 90 days of engagement history per subscriber.
2. A send window is defined (e.g., deliver within the next 7 days).
3. The contact waits at the STO activity until their predicted optimal time within the window.
4. If a subscriber has insufficient history, they are sent at the default time or a random time within the window.
Requirements: Requires Einstein Engagement Scoring licence. Needs at least 6 months of send data from the same MID for meaningful predictions. Not suitable for time-sensitive transactional messages.
Apple Mail Privacy Protection (MPP), launched in September 2021, pre-fetches email content (including tracking pixels) via a proxy server when the email is delivered — not when the subscriber actually opens it. This means every email delivered to an Apple Mail user on iOS 15+, macOS Monterey+, or iPadOS 15+ registers as an "open" even if the subscriber never looks at it.
Impact: Open rates are artificially inflated (often 50–100% reported open rates for Apple Mail users). Open-based segments and A/B test winner criteria become unreliable.
Adaptations:
— Shift primary engagement metric to CTOR (click-to-open rate) or raw click rate, which are not affected by MPP.
— Use click-based engagement splits in Journey Builder instead of open-based splits.
— For deliverability monitoring, rely on click rates, unsubscribe rates, and complaint rates rather than open rates.
— Segment engaged subscribers based on clicks rather than opens for re-engagement and suppression logic.
Impact: Open rates are artificially inflated (often 50–100% reported open rates for Apple Mail users). Open-based segments and A/B test winner criteria become unreliable.
Adaptations:
— Shift primary engagement metric to CTOR (click-to-open rate) or raw click rate, which are not affected by MPP.
— Use click-based engagement splits in Journey Builder instead of open-based splits.
— For deliverability monitoring, rely on click rates, unsubscribe rates, and complaint rates rather than open rates.
— Segment engaged subscribers based on clicks rather than opens for re-engagement and suppression logic.