To connect Marketing Cloud Account Engagement (formerly Pardot) to Salesforce, a Salesforce admin installs the Account Engagement package and creates a business unit in Marketing Setup, an Account Engagement admin sets up User Sync and maps fields, and then reviews and unpauses the version 2 Salesforce connector, which syncs as a built-in integration user. Finish by importing existing leads and contacts, connecting campaigns and testing the sync.
Every step below comes from Salesforce's Winter '27 implementation guides, Help and Trailhead, read on 22 November 2026. Still choosing a product? Read Account Engagement (Pardot) vs Marketing Cloud Engagement first.
What is the Account Engagement Salesforce connector?
The Salesforce connector is the built-in link that syncs Account Engagement prospects with Salesforce leads, contacts and person accounts, along with users, campaigns and opportunity data. Salesforce's Connector v2 guide says new business units come with version 2 of the connector, created in a paused state, and that you can have only one Salesforce connector per business unit.
Salesforce's guides note that the Pardot name still appears in places, including the app and the package; see our list of Salesforce product name changes. To check your connector version, Trailhead says an admin can open Account Engagement Settings and read the Connector Version row.
What do you need before you start?
The Account Engagement Setup Implementation Guide says setup needs both a Salesforce admin and an Account Engagement admin, with a separate plan for each business unit.
- Salesforce permissions: Download AppExchange Packages to install the package; Customize Application and Modify All Data to enable Account Engagement and create business units.
- Account Engagement permission: the Account Engagement Administrator role to edit the connector, map fields, connect campaigns and manage domains.
- A user list for Salesforce User Sync, and your DNS owner for domain records.
- A sync decision: every eligible record, or a subset with Marketing Data Sharing (Advanced or Premium edition).
How do you connect Account Engagement to Salesforce, step by step?
- Install the package. Use the installation link in Salesforce's guide; the guide says not to install the package directly from AppExchange. On step 2 of the wizard, choose Grant access to admins only.
- Create the business unit. In Marketing Setup, under Business Unit Setup, click Assign Admin, name the business unit and assign its Account Engagement admin. This admin cannot be changed later. In Setup Assistant, turn on Account Engagement.
- Set up Salesforce User Sync. The Salesforce admin assigns users to Account Engagement; the Account Engagement admin maps Salesforce profiles to Account Engagement roles on the connector's User Sync tab and clicks Opt In. The guide says user changes then take about 10 minutes to apply.
- Give users the Lightning app. Grant the b2bma_canvas connected app and a permission set such as Account Engagement User or CRM User.
- Prepare Salesforce. Map custom lead fields to contact fields so data survives lead conversion, and add the Account Engagement fields, Visualforce pages and buttons to lead and contact page layouts.
- Map fields in Account Engagement. On the Prospect Fields page, choose the Salesforce Field Name for each custom field and set its sync behavior (see below).
- Connect campaigns and decide on data sharing. Salesforce recommends setting up Connected Campaigns, and Marketing Data Sharing if you use it, before you unpause.
- Review and unpause the connector. In the Lightning app, open Account Engagement Settings, then Connectors, click the gear next to the Salesforce connector and choose Edit Settings. Review, then select Unpause.
- Trigger the initial sync. Import existing leads and contacts. The connector does not create prospects from existing Salesforce records on its own. New business units allow duplicate prospect emails by default; then import by CRM ID, or you create duplicate leads and contacts.
What is the integration user, and when do you need a custom connector user?
The integration user, named B2BMA Integration, is provisioned automatically to sync data. Salesforce's connector guide says it uses no standard Salesforce user license, has no password, cannot log in directly and authenticates through the Pardot Integration Connected App. Connector changes are attributed to it.
When the integration user is the connector user, it syncs all records for the objects that sync. To limit what syncs, Salesforce gives two routes: set up Marketing Data Sharing, which it recommends doing with the integration user, or switch to your own connector user with narrower access. A custom connector user needs the connector user permission set plus object permissions you set by hand, including View All on accounts and opportunities, Create, Edit, Read, View All and Modify All on leads and contacts, and View All and Modify All on ObjectChangeLogs.
How do prospects sync with leads and contacts?
The connector keeps a one-to-one link between each prospect and a Salesforce lead, contact or person account. Salesforce's connector guide sets the rules:
- Records sync on the CRM ID field. If a prospect has no matching Salesforce record, Account Engagement creates a lead, and an assigned prospect that is not yet syncing is created as a lead.
- If a prospect has no CRM ID and Salesforce has a record with the same email address, it syncs to that record; with several matches, to the first one found.
- Unassigned prospects sync, but no Salesforce record is created when there is no matching email address.
- Map users first. If a prospect's assigned user is not mapped to a Salesforce user, the prospect is assigned to the connector user.
- Default scoring adds 50 points for a created opportunity and subtracts 100 for a lost one, so check score-based automation.
Field mapping and sync behavior
Each mapped field has a sync behavior that decides which system wins. Salesforce Help names three settings: Account Engagement as master, Salesforce as master, and most recently updated. The Help article on overwritten values adds that by default a blank Salesforce value is filled from Account Engagement, even with Salesforce as master; Support can change this on request.
Mapping rules from the guide: create the custom field in Account Engagement first; to map one field to both lead and contact, the Salesforce API names must match; lookup and geolocation fields do not sync; map phone fields to text fields. Mapping does not trigger a sync. The connector troubleshooting article says newly mapped fields need a full sync, from the Queue prospects for a full sync prompt or through Support.
How do you set up Connected Campaigns?
Connected Campaigns link Account Engagement and Salesforce campaigns, so you manage campaigns in Salesforce and get Engagement History and campaign influence. The Connected Campaigns guide says it requires a verified Salesforce connector, and advises not turning it off once it is on.
- Dedupe, then create a Salesforce campaign for each Account Engagement campaign you keep, including Website Tracking and Salesforce Sync.
- Create campaign record types for the campaigns you want to connect. Salesforce advises against the Master record type, and for separate record types when several business units share one org.
- In Account Engagement Settings, open Connectors, edit the Salesforce connector and select the Campaigns tab. Select Enable Connected Campaigns and Engagement History, choose the record types and save.
- Connect campaigns one at a time with Connect to CRM Campaign, or in bulk with the mapping workbook.
- Select Use Salesforce to manage all campaigns. From then on, users create campaigns only in Salesforce.
Connected Account Engagement campaign records become read-only, and Salesforce replaces fields such as Name and Cost, which cannot be undone.
How do you set up a tracker domain?
A tracker domain rewrites links and vanity URLs on a subdomain of your own website for tracking. In Domain Management, click Add Tracker Domain and enter a subdomain that matches its root domain, such as go.example.com for example.com. Choose a default campaign, ask IT to point a CNAME for the subdomain to go.pardot.com, and add the validation key Account Engagement provides to your root domain's DNS.
DNS can take up to 24 hours to propagate. Then click Validate, set the default protocol to HTTPS and add the campaign tracking code before the closing body tag on high-value pages such as landing pages. Business units created after 15 February 2021 use HTTPS for tracker domains by default. Email sending domains and DKIM are set up on the same page.
How do you verify that the sync works?
Run Salesforce's four connector tests, ideally first in an Account Engagement sandbox (included in Advanced and Premium, a paid add-on in Plus):
- Existing record: create a prospect who already exists in Salesforce and click Sync with CRM, or wait 10 to 15 minutes for the automatic sync.
- New record: create a prospect who is not in Salesforce, then a lead or contact with the same email, and sync.
- Assignment: assign a new prospect to a sales user and sync.
- Salesforce first: if the connector setting to create prospects from Salesforce records is on, create a lead or contact and wait 10 to 15 minutes for the prospect.
How do you fix common sync errors?
Review errors on the connector's Sync Errors page: in the Lightning app, Account Engagement Settings, Connectors, Salesforce. A Salesforce Help article groups errors into four causes, and says each must be resolved before an admin can clear it so the prospect syncs again.
| Cause | Example errors | Where to look |
|---|---|---|
| Data formatting | Invalid picklist value; field too long; country/state integrity; Field Type Mismatch in a batch | Field types, restricted picklists and field mapping |
| Access | Insufficient access rights on object id | Connector user object, field and record access |
| Process alignment | Custom validation exception; duplicate value; duplicate matching rule conflict | Validation and duplicate rules in Salesforce |
| Customization | Cannot execute flow trigger | Flows and other automation on leads and contacts |
The connector user is subject to validation and duplicate rules; Salesforce suggests exceptions for records it creates. A v2 connector stuck in Verification in Progress may be missing a provisioning step. If your org restricts login IPs by profile, add the Account Engagement IP ranges.
What governance keeps the integration healthy?
- Give the sync queue an owner. Trailhead warns that without someone watching it, some records may not sync and fields may not update.
- Document every mapped field with its sync behavior and owner.
- Test in a sandbox first any new validation rule, duplicate rule or flow on leads and contacts.
- Keep campaign record types tidy so only intended campaigns replicate.
- Align with sales. Agree assignment, lead status and score thresholds with your Sales Cloud team before the first import.
Frequently asked questions
Is Pardot the same as Marketing Cloud Account Engagement?
Yes. Marketing Cloud Account Engagement is Salesforce's current name for the product formerly called Pardot. Salesforce's own setup guides say you will still see the Pardot name in a few places, including in the app itself, the AppExchange package and some permission sets and buttons.
Which user does the Account Engagement Salesforce connector sync as?
Version 2 of the connector syncs as the integration user, an automatically provisioned user named B2BMA Integration. Salesforce says it does not use a standard Salesforce user license, has no password and cannot log in to Salesforce directly.
Why don't my existing Salesforce leads and contacts appear in Account Engagement?
The connector does not create prospects from existing Salesforce leads and contacts automatically. Salesforce's guide says to import them into Account Engagement once after you connect. New business units allow multiple prospects with the same email address by default, and in that case you must import by CRM ID, or the import creates duplicate leads or contacts in Salesforce.
How often does Account Engagement sync with Salesforce?
Salesforce's connector guide says syncs can occur as often as every 2 minutes, and that a larger volume of data takes longer to sync. When you test the connector, Salesforce suggests waiting 10 to 15 minutes to see whether an automatic sync starts, or clicking Sync with CRM on the prospect record to sync it at once.
Can I connect more than one Account Engagement business unit to one Salesforce org?
Yes, but plan it. You can have only one Salesforce connector per business unit. If several business units link to one Salesforce org, you cannot use the integration user unless you also use Marketing Data Sharing, which needs Advanced or Premium edition. For Connected Campaigns, Salesforce advises separate campaign record types for each business unit.
Next steps
Techila Global Services is a Salesforce Summit Partner headquartered in Frisco, Texas, with 700+ projects and 500+ Salesforce certifications. Our Marketing Cloud team sets up and audits Account Engagement connectors; our Salesforce integration services team connects the rest of your stack; see our integration catalog. To plan your connector setup or fix a stuck sync, book a call with our team.