marketing-cloud-vs-mcae-selection

# Marketing Cloud vs. MCAE Platform Selection

This skill activates when a practitioner or architect must choose between Marketing Cloud Engagement (MCE) and Marketing Cloud Account Engagement (MCAE, formerly Pardot) for a Salesforce marketing implementation. It produces a structured recommendation grounded in audience type, channel requirements, volume, and CRM alignment needs. It does not cover configuration or implementation of either platform.

---

## Before Starting

Gather this context before working on anything in this domain:

- **Audience model:** Confirm whether the marketing audience is primarily B2C (high-volume, subscriber lists, anonymous or semi-anonymous consumers) or B2B (known prospects tied to Accounts, managed through a sales pipeline).
- **Most common wrong assumption:** Practitioners frequently assume MCE and MCAE are two editions of the same product with overlapping feature sets. They are separate products with separate data stores, separate licensing, and architecturally different data models. Features do not transfer between them.
- **Platform constraints in play:** MCAE has a prospect record limit tied to the purchased edition (Growth, Plus, Advanced, Premium). MCE scales to very high subscriber volumes but requires Data Extensions for contact management rather than native Salesforce object sync.

---

## Core Concepts

### Marketing Cloud Engagement (MCE) — B2C, High-Volume, Multi-Channel

MCE is purpose-built for high-volume, consumer-facing marketing across multiple channels: email, SMS, push notifications, in-app messaging, advertising audiences, and social. Its data model centers on **Data Extensions (DEs)** — flat, relational tables that hold contact and send data. MCE does not natively sync Salesforce CRM objects in real time; integration with Sales Cloud or Service Cloud requires **Marketing Cloud Connect**, a managed package that maps Contacts and Leads to Subscriber records.

Key MCE characteristics:
- Subscriber volumes in the tens of millions are supported.
- Journey Builder orchestrates multi-step, multi-channel customer journeys triggered by data events.
- Automation Studio runs scheduled and triggered batch processes on DEs.
- Email Studio, MobileConnect, MobilePush, Advertising Studio, and Interaction Studio (now Personalization) are discrete sub-applications, each licensed separately.
- There is no native lead scoring, lead grading, or sales activity tracking. These capabilities do not exist within MCE.

### Marketing Cloud Account Engagement (MCAE) — B2B, Lead Nurturing, CRM-Aligned

MCAE is purpose-built for B2B demand generation, lead lifecycle management, and tight bidirectional CRM sync. Its data model centers on **Prospects** — records that map 1:1 to Salesforce Leads or Contacts, with full field sync, activity tracking, and campaign influence attribution.

Key MCAE characteristics:
- **Scoring** assigns numeric values (0–100 default scale) to prospects based on engagement activity (email opens, clicks, form submissions, page views).
- **Grading** assigns an A–F grade based on explicit profile criteria (job title, company size, industry) configured by the marketer.
- **Engagement Studio** is a rule-based drip and nurture program engine that operates at the prospect level — not equivalent to Journey Builder.
- Prospect records sync bidirectionally with Salesforce on a ~2-minute cycle (varies by edition). Field-level sync rules are configured per field.
- MCAE is constrained to email, forms, landing pages, and social posting. It does not natively support SMS, push notifications, or advertising audiences.
- Prospect record limits apply by edition: Growth (10K), Plus (10K), Advanced (10K), Premium (75K). Additional prospects require license upgrades.

### Separate Licenses, Separate Data Stores — Not Substitutes

MCE and MCAE are separately licensed, separately priced, and maintain completely separate data stores. There is no shared contact database between the two products. An organization running both must manage the boundary between MCE subscriber data (in DEs) and MCAE prospect data (in the MCAE database), which syncs to Salesforce CRM objects.

**MC Connect** is the mechanism for using MCE and MCAE together within a single Salesforce org. It allows MCAE prospect lists to be pushed into MCE for high-volume sending, then engagement data returned to MCAE. However, MC Connect does not merge the two data stores — each product retains its own data layer. Both licenses remain required.

---

## Common Patterns

### Pattern 1: Pure B2C — MCE Only

**When to use:** The audience is consumer-facing, subscriber volumes exceed 10K–50K, the marketer needs multi-channel orchestration (email + SMS + push), and there is no sales team requiring lead-level engagement visibility.

**How it works:** MCE is provisioned with the appropriate edition (Email, Growth, Advanced, etc.). Contacts are managed in Sendable Data Extensions. Journey Builder handles lifecycle campaigns. Marketing Cloud Connect links MCE to Salesforce for opt-out sync and reporting if a CRM is in use. MCAE is not purchased.

**Why not the alternative:** MCAE's prospect limits, email-only channel coverage, and per-prospect data model are not suited to consumer audiences at volume. Attempting to use MCAE for a 500K subscriber list would require an edition that is cost-prohibitive and architecturally inappropriate.

### Pattern 2: Pure B2B — MCAE Only

**When to use:** The audience is a known set of business prospects tied to Accounts in Sales Cloud, the sales team needs pipeline-level engagement data, lead scoring and grading are required, and send volumes are within edition limits.

**How it works:** MCAE is provisioned and connected to Salesforce via the native MCAE connector (not MC Connect). Prospects sync bidirectionally. Engagement Studio programs manage nurture sequences. Pardot Campaigns and Salesforce Campaigns are aligned. Scoring and grading models are configured to reflect the sales qualification criteria.

**Why not the alternative:** MCE has no native lead scoring, no prospect-to-Account relationship model, and no native CRM field sync. Using MCE for B2B lead nurturing requires significant custom integration work to approximate what MCAE provides natively.

### Pattern 3: Hybrid B2B + B2C — MCE + MCAE via MC Connect

**When to use:** The organization has both consumer-facing marketing (high volume, multi-channel) and B2B demand generation (lead nurturing, sales alignment) running simultaneously — for example, a technology vendor with a self-serve product (B2C) and an enterprise sales motion (B2B).

**How it works:** Both MCE and MCAE are licensed. MC Connect is configured to allow MCAE prospect lists to be used as audiences in MCE Journey Builder. MCE handles high-volume delivery. MCAE handles CRM sync, scoring, and grading. Each platform retains its own data store. Architects must explicitly map which data lives where and design the handoff points.

---

## Decision Guidance

| Situation | Recommended Approach | Reason |
|---|---|---|
| B2C audience, high volume (>50K), multi-channel | MCE | Built for scale, multi-channel orchestration, Data Extension model |
| B2B lead nurturing, sales alignment, <75K prospects | MCAE | Native CRM sync, scoring, grading, Engagement Studio |
| Need SMS or push notifications for any audience | MCE (required) | MCAE does not support SMS or push |
| Need lead scoring and grading | MCAE (required) | MCE has no native scoring or grading capability |
| Sales team needs prospect-level engagement in CRM | MCAE | MCAE syncs activity to Salesforce natively |
| Both B2C and B2B in the same org | MCE + MCAE with MC Connect | Both licenses required; each retains its own data store |
| Budget allows only one platform, mixed audience | Evaluate primary motion; default to MCAE if sales alignment is the core use case, MCE if volume and channel breadth are the core use case | Feature gaps cannot be bridged without the other license |
| High-volume transactional email (order confirmations, receipts) | MCE | MCAE is not designed for transactional volume at scale |

---

## Recommended Workflow

Step-by-step instructions for an AI agent or practitioner guiding platform selection:

1. **Characterize the audience.** Confirm whether the primary audience is B2C (consumer, subscriber-based, anonymous or semi-anonymous) or B2B (known prospects tied to Accounts, managed through a sales pipeline). If both, document the volume and motion for each segment separately.
2. **Identify required channels.** List every channel the marketing program requires: email, SMS, push, in-app, advertising, social. If SMS or push is required for any segment, MCE is mandatory for that segment. MCAE covers email only.
3. **Quantify send volume and prospect/subscriber count.** Confirm expected subscriber counts for MCE planning and prospect counts for MCAE edition selection. MCAE edition limits (Growth 10K through Premium 75K) are a hard constraint.
4. **Assess sales alignment requirements.** Determine whether the sales team needs prospect-level engagement data in Salesforce, lead scoring, lead grading, or automated sales alerts. If yes, MCAE is required. MCE does not provide these natively.
5. **Evaluate budget and license feasibility.** Confirm which licenses the customer can purchase. MCE and MCAE are separately priced. If both are needed, confirm MC Connect will be part of the implementation scope.
6. **Document the recommendation with rationale.** Produce a written decision — MCE only, MCAE only, or both with MC Connect — citing each driving factor. Use the decision table above as a reference. Record any open questions or risks.
7. **Identify what each platform will not cover.** Explicitly document the capability gaps for the selected configuration so the customer understands what they are accepting — for example, if MCAE only, document that SMS and push are out of scope.

---

## Review Checklist

Run through these before marking work in this area complete:

- [ ] Audience type (B2C / B2B / mixed) is explicitly documented
- [ ] Required channels are enumerated; SMS/push presence drives MCE requirement
- [ ] Prospect and subscriber volume estimates are confirmed against edition limits
- [ ] Sales alignment requirements (scoring, grading, CRM sync) are assessed
- [ ] License availability is confirmed for the recommendation
- [ ] Capability gaps for the selected configuration are documented
- [ ] MC Connect scope is addressed if both platforms are recommended

---

## Salesforce-Specific Gotchas

Non-obvious platform behaviors that cause real production problems:

1. **MCAE scoring and grading are not available in MCE** — Practitioners sometimes assume that because both products are branded "Marketing Cloud," scoring and grading features can be enabled in MCE. They cannot. Scoring (activity-based numeric score) and grading (profile-based letter grade) are MCAE-exclusive capabilities. There is no configuration path to bring them into MCE.
2. **MC Connect does not create a shared data store** — When MCE and MCAE are connected via MC Connect, they still maintain completely separate databases. MCAE prospect data lives in the MCAE database, synced to Salesforce CRM objects. MCE contact data lives in Data Extensions. MC Connect creates sending and reporting bridges but does not merge these stores. Architects who assume a unified contact record will encounter data consistency problems.
3. **MCE does not natively sync Salesforce CRM objects** — Unlike MCAE, which has a built-in bidirectional sync with Leads and Contacts, MCE has no native Salesforce object sync. Marketing Cloud Connect is required for even basic opt-out and contact sync. Custom integrations or Marketing Cloud Connect configurations must be explicitly designed.

---

## Output Artifacts

| Artifact | Description |
|---|---|
| Platform Selection Recommendation | Written rationale document stating MCE, MCAE, or both, with each driving decision factor documented |
| Decision Matrix | Table mapping each business requirement to its platform capability or gap |
| Open Questions Log | List of requirements not yet confirmed that could change the recommendation |
| Capability Gap Register | Explicit list of marketing capabilities the selected configuration does not cover |

---

## Related Skills

- `admin/mcae-pardot-setup` — Use after selecting MCAE; covers initial configuration, business unit setup, and Salesforce connector setup
- `admin/marketing-cloud-engagement-setup` — Use after selecting MCE; covers provisioning, sender authentication, and initial configuration
- `admin/marketing-automation-requirements` — Use upstream of this skill to gather and document marketing automation requirements before platform selection
- `data/data-extension-design` — Use when MCE is selected; covers Data Extension modeling for sendable and non-sendable contact data