Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Salesforce Architect
hard

How do you architect data flow between Salesforce, Marketing Cloud Engagement, and Pardot/MCAE?

Marketing data flow architecture requires understanding three distinct platforms.

Pardot / Marketing Cloud Account Engagement (MCAE):

  • B2B-focused — Lead nurture, scoring, email campaigns.
  • Lives inside Salesforce — same platform.
  • Prospect = MCAE record (separate from Lead/Contact at first).
  • Sync rules between Prospect and Lead/Contact.

Marketing Cloud Engagement (MCE, formerly ExactTarget):

  • B2C-focused — high-volume email, mobile, SMS, social.
  • Separate platform from Salesforce.
  • Subscriber = MCE contact identifier.
  • Marketing Cloud Connect integration with Salesforce CRM.

Architecture for B2B with both:

Use case:

  • B2B SaaS company with both demand gen (B2B sales motion) and consumer brand presence.
  • Pardot for lead nurture for B2B leads.
  • Marketing Cloud Engagement for B2C newsletters.

Data flow:

  • Salesforce CRM — Account / Contact / Lead canonical.
  • Pardot — leads from B2B campaigns; nurture; hand-off to sales.
  • Marketing Cloud Engagement — consumer email lists; transactional emails.

Sync patterns:

  • Salesforce -> Pardot: Account / Contact / Lead sync continuously. Pardot enriches with engagement data.
  • Pardot -> Salesforce: hot leads flagged for sales follow-up.
  • Salesforce -> Marketing Cloud Engagement: Subscriber list creation; data extension population.
  • Marketing Cloud Engagement -> Salesforce: engagement events (email opened, clicked).

Identity strategy:

  • Single source of truth for customer master.
  • External Ids to link records across platforms.
  • Identity Resolution (potentially via Data Cloud) for unified profile.

Campaign Influence:

  • Pardot campaigns recorded.
  • MCE campaigns recorded.
  • Both contribute to revenue attribution.
  • Salesforce Customizable Campaign Influence aggregates.

Architecture decisions:

1. Both platforms or one?

  • Pure B2B: Pardot only.
  • Pure B2C: MCE only.
  • Both: justified for hybrid orgs; complex.

2. Sync frequency:

  • Real-time vs batch.
  • Real-time for hot leads; batch for bulk data.

3. Conflict resolution:

  • Same person in both Pardot and MCE — single profile or distinct?
  • Salesforce CRM as source of truth for customer master.

4. Reporting:

  • Per-platform reports.
  • Cross-platform via Marketing Cloud Intelligence (Datorama) or Tableau.

Common pitfalls:

  • Both platforms with no integration — duplicates effort and data.
  • Wrong platform for use case — Pardot for B2C, MCE for B2B.
  • Sync conflicts — same person updated differently in each.

Senior architect insight: multi-marketing-platform is justified for hybrid B2B/B2C orgs but adds significant complexity. Architect carefully.

The senior framing: don't underestimate marketing data integration. It's a major architectural area, often underinvested.

Why this answer works

Senior. The B2B vs B2C distinction and multi-platform sync framework are mature.

Follow-ups to expect

Related dictionary terms