Loading tutorials…
Loading tutorials…
Marketing Cloud Account Engagement (the tool Salesforce renamed from Pardot in 2022) is the marketing automation layer for B2B Salesforce orgs. The Salesforce-Pardot connector is the most-broken piece of integration in the Salesforce ecosystem. Here is the setup discipline that holds up.
Who this is forB2B marketing ops leads, RevOps owners, and founders running Pardot/Account Engagement alongside Salesforce. If you have ever seen sync errors that nobody can explain, or 'Pardot says converted but Salesforce says still a Lead,' this tutorial is for you.
What you'll need
Step 1
Salesforce renamed Pardot to 'Marketing Cloud Account Engagement' in 2022. Same product, same data model, same connector. The naming change broke a lot of docs but not the underlying integration.
Pardot is now 'Marketing Cloud Account Engagement' (often shortened to 'Account Engagement' or MCAE). Some Salesforce UIs still say Pardot; some say Account Engagement. They are the same tool.
Editions: Growth ($1,250/mo), Plus ($2,500/mo), Advanced ($4,000/mo), Premium ($15,000/mo). Most B2B teams under 100K prospects run on Growth or Plus.
Marketing Cloud Account Engagement is separate from Marketing Cloud Engagement (formerly Marketing Cloud — the bigger, more complex platform for B2C and high-volume). Do not confuse them. MCAE = B2B; MCE = B2C/enterprise multi-channel.
The connector between MCAE and Salesforce uses an OAuth-based "v2 Connector" since 2020. If your org is still on the legacy v1 connector, migrate now — Salesforce deprecates v1 with limited support.
Trailhead modules for MCAE are still labeled "Pardot" in many places. The product UI inside Salesforce Lightning shows as "Marketing Setup → Account Engagement Setup."
Step 2
Setup → Account Engagement Setup → Connect. This is the v2 OAuth flow that establishes the trust between Salesforce and Account Engagement.
Setup → Quick Find → "Account Engagement Setup" → click "Get Started" or "Configure Account Engagement."
Step 1: Enable the Account Engagement Lightning App. Setup → Apps → App Manager → find "Account Engagement" → set Visible for the right profiles.
Step 2: Configure the v2 Connector. Account Engagement → Settings → Connectors → click the Salesforce connector → "Reconnect" if needed. Authenticate as a dedicated integration user (NOT your personal admin user).
Step 3: Create the integration user. Setup → Users → New User → License Type "Marketing User" or "Identity" → Profile "B2BMA Integration User" or a custom Profile with Account Engagement Admin permission set. Email: pardot-integration@yourco.com.
Step 4: Set Verified Status. Account Engagement → Settings → Connectors → Salesforce connector → "Verify" the connection. If verification fails, the most common cause is the integration user does not have access to certain Salesforce objects (Lead, Contact, Account, Opportunity, Campaign).
Step 3
Account Engagement → Settings → Object and Field Configuration. Map every Prospect field to its Salesforce Lead/Contact equivalent. Sync direction matters.
Account Engagement → Settings → Object and Field Configuration → Salesforce Field Mappings.
For each MCAE field (Prospect First Name, Email, Company, Lead Source, custom fields), choose: which Salesforce field does it map to? Direction (Prospect-to-Salesforce, Salesforce-to-Prospect, Both)? Sync behavior on conflict?
Critical: "Most Recently Updated Record" is the default conflict-resolution. In practice this means whichever system updated last wins. For high-volume fields (Email, Phone), this can cause data to ping-pong.
For attribution fields (UTM Source, UTM Campaign, First Touch Channel): sync direction should be Prospect-to-Salesforce ONLY. Marketing data should never be overwritten by sales.
For lifecycle fields (Lifecycle Stage, MQL Date): sync direction should be Salesforce-to-Prospect ONLY. Sales decides when a Lead becomes an MQL; Marketing should not flip it back.
Document every field mapping in a Field Sync Map outside the platform. When sync errors hit, the doc tells you where to look.
Step 4
Account Engagement → Settings → Salesforce → Prospect Sync. Decide which Prospects sync to Salesforce as Leads — and which stay in MCAE only.
Account Engagement → Settings → Salesforce → Prospect Sync. Enable Auto-Sync.
Choose the Sync Trigger: 'Sync all Prospects' (sends every MCAE prospect to Salesforce as a Lead — high volume) or 'Sync only assigned Prospects' (only sends Prospects assigned to a user — cleaner).
Most healthy orgs use "Sync only assigned Prospects" or "Sync via Engagement Studio rule" — only Prospects who have engaged (hit a threshold score, downloaded a whitepaper) sync to Salesforce. Junk traffic stays in MCAE.
Set up Lead Source mapping: every Prospect synced should have a Lead Source value set in MCAE (Inbound Form, Webinar Registration, Outbound Sync). This populates the Lead.Lead_Source field at creation in Salesforce.
Verified Visitors (formerly 'Verified' status in Pardot): identifies a Prospect's IP-resolved company. Useful for ABM. Configure in Account Engagement → Settings → Visitor Settings.
Step 5
Score = engagement-based (visits, clicks, downloads). Grade = fit-based (company size, industry, role). Both matter. Configure both.
Account Engagement → Settings → Automation Settings → Scoring Rules. Set point values for actions: page view = +1, whitepaper download = +25, demo request = +100, email click = +5, unsubscribe = -50.
Account Engagement → Marketing → Segmentation → Grading Profiles. Build a Grading Profile per ICP. Example: B2B SaaS ICP — Company Size > 100 = +1 grade letter; Industry = SaaS = +1; Title contains VP or Director = +1; Country = USA or Canada = +1. Letter grades A through F.
Sync Score + Grade to Salesforce as fields on Lead and Contact. Add them to the page layout so SDRs see "Score: 85, Grade: A" at a glance.
Build an Engagement Studio program: when Score > 50 AND Grade >= B, mark the Prospect as MQL, assign to SDR queue. When Score > 100 AND Grade = A, escalate to AE-level.
Audit scoring rules quarterly. Stale scoring = stale lead quality. Most teams ignore this and end up with "everyone is an MQL" inflation.
Step 6
Account Engagement → Sync Errors Queue. Every failed sync lands here. Treat it like a daily ticket queue.
Account Engagement → click your username → Recent Activities → Sync Errors. Or Setup → Account Engagement Setup → Sync Errors.
Each error has: Prospect, Field, Error Message, Direction. Common errors: "Field-level security blocks update" (integration user missing FLS), "Validation rule failed" (Salesforce validation rejected the value), "Duplicate record" (matching rule blocked creation).
For each error type, build a runbook: 'FLS errors → Setup → Profiles → B2BMA Integration User → Object Settings → grant field-level Edit on the failing field.'
Set up alerts: a Schedule-Triggered Flow in Salesforce that pulls the MCAE Sync Errors via API and posts a Slack message when count > 10. Or use the MCAE digest email subscription.
Sync error count over 100 = the connector is degrading marketing attribution. Fix the top 5 error categories before any new field mapping.
Step 7
Submit a form → Prospect created in MCAE → synced to Salesforce as Lead → assigned via Lead Routing → MQL'ed via score → handed to AE.
Open an incognito browser. Submit a real form on your website — the form should be MCAE-hosted or HubSpot-style POSTing to MCAE.
Within 60 seconds: the Prospect should appear in MCAE → Prospects → Prospect List.
Within 5 minutes (auto-sync interval): the Prospect should appear in Salesforce → Leads as a new Lead.
Verify: Lead Owner is correct per Lead Assignment Rule. Lead Source = the value MCAE passed. All synced custom fields populated.
Walk the Prospect through Engagement Studio: have them click an email → visit a page → download a whitepaper. Watch Score climb in MCAE and on the Salesforce Lead record.
At each step, confirm both systems agree. Disagreement = sync error or field mapping bug. Catch it now before scaling to 1,000+ Prospects.
Common mistakes
Using a personal user account as the connector integration user
What goes wrong: Marketing ops admin Sarah authenticated the connector with her personal account. She leaves the company. Her user is deactivated. The connector breaks at 3 AM that night. All sync stops. Nobody notices for 4 days because there is no alerting. Reports show a 30% revenue gap from missing MCAE attribution data.
How to avoid: Setup → Users → New User → create "pardot-integration@yourco.com" with B2BMA Integration User profile or a custom profile. Authenticate connector with this user only. Never deactivate this user.
Allowing bidirectional sync on every field
What goes wrong: Marketing changes Lead Source = 'Webinar' in MCAE. Sales changes it to 'Outbound' in Salesforce. The sync ping-pongs every 5 minutes. Reports show a 30% revenue gap as attribution data overwrites itself. Both teams accuse each other of breaking the data.
How to avoid: Set sync direction deliberately per field. Attribution fields (UTM, Lead Source, First Touch): Prospect-to-Salesforce only. Lifecycle fields (Lifecycle Stage, MQL Date): Salesforce-to-Prospect only.
Syncing every MCAE Prospect to Salesforce as a Lead
What goes wrong: Every newsletter signup, every blog visitor (anonymous visitor resolved by Verified Visitors), every tradeshow scan creates a Salesforce Lead. Salesforce hits 500K Leads in 6 months. Storage costs spike. Reports show a 30% revenue gap from junk Leads diluting MQL counts. Rep adoption drops to 20% because the Lead queue is unworkable.
How to avoid: Setup → MCAE → Prospect Sync → "Sync only assigned Prospects" or sync via Engagement Studio rule (only Prospects who hit a Score threshold). Junk stays in MCAE.
Not monitoring Sync Errors
What goes wrong: Sync Errors Queue grows to 1,200 items. Each error means a Prospect did not sync. Marketing's MQL count says 800 last month. Salesforce shows 600 Leads created. 200 MQLs never made it to Sales. Pipeline reports show a 25-30% revenue gap from missing leads.
How to avoid: Daily sync error review. Build a Schedule-Triggered Flow that alerts when sync errors > 10. Fix the top error categories before scaling.
Inflated scoring rules — "everyone is an MQL"
What goes wrong: Score thresholds are too generous. Every Prospect hits MQL within 3 weeks. Sales is flooded with low-quality MQLs. AE adoption drops to 30% after 90 days because 'MQL' means nothing. Pipeline reports show MQL → SQL conversion rate of 5% — meaningless inflation.
How to avoid: Recalibrate scoring quarterly. Pull historical MQL → SQL conversion rate by score band. Set the MQL threshold so the conversion rate is 40%+ from MQL → SQL.
Skipping the integration user permission audit
What goes wrong: After a Salesforce field-permission change (FLS update), the integration user loses Edit access to a field. Every Prospect sync for that field starts failing. Sync Errors Queue fills up. Marketing attribution data goes stale. Nobody connects the FLS change to the sync failure for 6 weeks.
How to avoid: After ANY profile or FLS change, log into Salesforce as the integration user (or run a permission check via the Setup → Users → integration user → "Login" link) and verify access to every synced field.
Recap
Done — what's next
How to set up Salesforce Leads, Contacts, and Opportunities without confusing your reps
Read the next tutorial
Hand it off
The Salesforce-MCAE connector is the most-broken integration in the Salesforce ecosystem. A specialist who has built and maintained 20+ MCAE/Pardot integrations knows the FLS pitfalls, the field-mapping patterns, and how to keep sync errors under 10. EverestX Pardot-capable specialists run $400-1,200/mo at $14-16/hr — typically $400-800 for a one-shot connector audit + cleanup.
See specialist rates
Depends on which CRM you already run. If you are deep in Salesforce — custom objects, complex sharing rules, Salesforce-native reporting — Account Engagement is the lowest-friction marketing automation. If you are flexible on CRM or just starting out, HubSpot Marketing Hub + HubSpot CRM is faster to set up and easier to maintain. MCAE costs $1,250-15,000/mo and is more powerful at the high end; HubSpot Marketing Starter is $20/seat/mo and Pro is $890/mo.
Prospects keep getting created in MCAE (forms, webinars, manual entry). They queue up for sync. When the connector is restored, Salesforce gets a backlog flood of new Leads. Validation rules and assignment rules fire on all of them at once — sometimes overwhelming Salesforce governor limits. Monitor the queue in Account Engagement → Settings → Connectors → Salesforce → Pending Syncs.
No. One MCAE business unit = one Salesforce org. To support multiple Salesforce orgs (e.g., after an acquisition), you need multiple Account Engagement business units (each on the Plus or Advanced edition) and a Marketing Cloud Account Engagement Business Unit Switcher.
Score = engagement (behavior-based: clicks, page views, downloads). Grade = fit (firmographic-based: company size, industry, title). A great Lead has both: high Score (engaged) AND high Grade (ICP fit). Most teams gate MQL on both — Score > 50 AND Grade >= B. Using only Score = MQLs that are engaged but bad fit; using only Grade = MQLs that are good fit but ignoring you.
Engagement Studio (multi-step nurture programs with branching logic, A/B testing, wait timers) is included in MCAE Plus and above. For under 5,000 Prospects with simple nurture needs, Automation Rules + Drip Programs (basic, available in Growth) are enough. Past 5,000 Prospects or complex nurture, Engagement Studio is the standard.
Salesforce
The Lead-Contact-Opportunity distinction is the single most-confused concept in Salesforce. Get it wrong and your reports double-count revenue, your reps work duplicate records, and Marketing keeps emailing people who already closed. Here is the discipline that holds up at scale.
Salesforce
Lead routing is where most Salesforce orgs leak revenue silently. A Lead lands at 2 PM, sits unassigned until Wednesday, and the prospect has booked a call with your competitor by Thursday. Here is the routing discipline that turns leads into meetings within 5 minutes.
Salesforce
Salesforce data quality decays silently. Duplicates compound, validation gaps widen, sync drift accumulates. By the time leadership notices, reports are 30% wrong and rep adoption has tanked. Here is the systematic diagnosis + fix sequence.
HubSpot Marketing Hub
Workflows are the engine under HubSpot's marketing automation. They are also where 80% of the silent breakage happens — wrong enrollment criteria, missing re-enrollment toggles, branch logic that loops. Here's how specialists build them so they hold up.
Salesforce
DIY Salesforce admin is a great idea — until it is not. This is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you are on.