When the sync between Salesforce and Marketing Cloud Account Engagement (Pardot) breaks, nothing crashes. No alarms. Prospects just quietly stop updating, leads stop routing, and three weeks later someone asks why the pipeline report looks thin. Sync errors are the most common — and most ignored — infrastructure problem in B2B revenue stacks.
Here's how the connector actually works, the errors we see most, and a diagnostic routine that catches problems before your pipeline does.
The Account Engagement connector links prospects (Pardot side) to leads and contacts (Salesforce side), syncing field values in both directions on a rolling basis. Which side wins a conflict depends on your sync behavior settings — per field, you can prefer Salesforce's value, Account Engagement's value, or the most recently updated. Records that can't sync land in the sync error queue, where they wait for someone to notice. That queue is the single most informative — and least visited — screen in the platform.
1. Validation rules blocking updates. The classic. Salesforce has a validation rule ("Industry is required"), Account Engagement tries to sync a prospect without that field, Salesforce rejects it, and the prospect is stuck — forever, until fixed. Fix: either exempt the integration user from validation rules (a dedicated integration user profile makes this clean), or ensure your forms and form handlers collect the required fields before the record ever syncs.
2. The connector user lacks permissions. Field-level security silently blocks the connector from reading or writing specific fields. The sync "works" but data is missing. Fix: audit the connector user's profile against every synced field; when in doubt, run the connector as an integration user with appropriately broad field access.
3. Duplicate records confusing the match. Two contacts with the same email, or a lead and a contact with the same email — the connector matches on email address, and duplicates make matching ambiguous. Updates land on the wrong record or bounce. Fix: deduplicate Salesforce (this is why data hygiene is a marketing problem, not just an admin chore) and define your lead-vs-contact matching policy deliberately.
4. Deleted or unconverted records. A Salesforce lead gets deleted or merged, and its paired prospect keeps trying to sync into the void. Fix: review the error queue for "record not found" patterns after any bulk cleanup, and recycle-bin restores need a matching prospect check.
5. Picklist mismatches. Account Engagement sends "Health Care"; the Salesforce picklist only accepts "Healthcare." With restricted picklists, the update fails. Fix: mirror picklist values exactly across both platforms, and document the canonical list so nobody "improves" one side unilaterally.
6. Sync paused and nobody noticed. Connector credentials expire, a password rotates, a Salesforce release changes something — and the connector has been paused for a month. Fix: a monthly two-minute check of connector status belongs on someone's recurring calendar. (It's on ours for every retainer client.)
A sync error isn't a record problem — it's a revenue-process problem. Stuck prospects don't route to sales, so your hottest leads sit unworked. Field values diverge, so lead scoring fires on stale data. And campaign attribution quietly decays, which is a big part of why your Salesforce and Pardot reports stop agreeing. One unnoticed month of sync failures can take a quarter to fully reconcile.
Fifteen minutes, once a month:
If your error queue has four digits, your database has years of duplicates, or nobody knows what the sync behavior settings should be — that's a rebuild conversation, not a checklist. Cross-platform plumbing is the center of our Account Engagement work, precisely because most "Pardot problems" turn out to be Salesforce problems in disguise. Let's talk — a connector audit is usually a one-week fix that pays for itself in the first month.
Founder of Thompson Technology. Salesforce and Account Engagement consultant for B2B companies.
