Key Takeaways
- Two admins split the work. The Salesforce admin installs the package and creates the business unit. The Account Engagement admin handles the connector, domains and assets.
- Follow Salesforce’s order: package, business unit, User Sync, fields, connector, then domains. The connector stays paused until the early steps are done.
- Clean your records and agree to the MQL definition before the first sync. Fixing either later means rework.
- A basic setup takes 10 hours to two weeks. A full rollout takes 4 to 12 weeks.
Introduction
Pardot changed its name in April 2022. Salesforce now calls it Marketing Cloud Account Engagement. The old name still shows up on field labels, on go.pardot.com and in parts of the app. The tool itself does the same job. Marketers use it to capture leads, nurture them by email and pass the ready ones to sales.
You won’t set it up alone. Your Salesforce admin installs it. Your Account Engagement admin configures it. Someone in IT adds DNS records. Your sales and marketing leads decide what a qualified lead is. Each of them owns part of the work.
This Account Engagement implementation guide follows the order Salesforce uses in its own setup docs. It starts with the prep work. Then it walks through nine setup steps and names who does each one. It ends with timelines and the mistakes that break the sync most often.
What Is an Account Engagement (Pardot) Implementation?
An Account Engagement implementation is the work of getting Marketing Cloud Account Engagement running in your Salesforce org. You install the package and connect users and records. You verify the domains you track and send from. Then you build your first forms, emails and landing pages.
Data moves both ways. So you set up three things: the Salesforce org, the Account Engagement business unit and the connector between them. Follow this Account Engagement implementation guide to the end, and your marketing team can start building campaigns.
A Salesforce Pardot implementation is the same project under the old name. Salesforce renamed the product in April 2022 and kept its core features.
Check your connector version early. New business units get version 2 of the Salesforce connector. Accounts bought before February 11, 2019 may still use version 1. Some of their steps look different.
Account Engagement or Marketing Cloud Engagement?
Account Engagement is built for B2B. It suits long sales cycles with several decision-makers. It scores and grades leads, and reps see prospect activity in Salesforce.
Marketing Cloud Engagement is the B2C product. It sends to very large consumer lists by email, SMS, mobile push and ads.
Our comparison of Account Engagement (Pardot) and Marketing Cloud covers the differences.
Marketing Cloud Account Engagement Setup Pre-Implementation Checklist
Sort out three things before anyone clicks Install. Check your Salesforce data. Decide who needs access. Line up the DNS work with IT. Skip this and you’ll face sync errors, failed email authentication and delays later.
1. Define Goals, Scope and Admin Owners
Write down what the project must fix. Note how you’ll measure success. Those KPIs become your reports and dashboards later. Decide if you’ll do the work in-house or with a Salesforce partner. Then name an owner for data, for configuration and for sign-off.
A full team has a project manager, a Salesforce admin and an Account Engagement admin. It also has a webmaster or IT specialist, power users, sales and marketing specialists and a graphic designer.
In a small company, one marketing admin can act as Salesforce admin, Account Engagement admin and project manager.
Business unit setup needs a Salesforce admin and an Account Engagement admin. Want just one? Create a custom permission set that gives Account Engagement tasks to a marketing admin.
Salesforce also offers a planning worksheet. Fill in one for each business unit. Keep notes on meetings, milestones and every configuration choice as you go.
2. Audit Your Salesforce and Prospect Data
Start the data audit in Salesforce, not in Account Engagement. Sort your leads and contacts by email address. Duplicates show up straight away. So do records with no company name or old details.
Merge or fix them before you switch the connector on. Whatever sits in Salesforce on sync day becomes a prospect. It gets scored, graded and emailed.
Check consent next. Look at subscription preferences, opt-outs and suppression lists. Then list every standard and custom field that has to sync. Ask your Salesforce admin to confirm the connector can see each one.
3. Map the Lead Lifecycle and Agree on MQL Rules
Now draw the path a prospect takes. It starts with a first website visit and ends with a qualified lead. Mark the point where marketing hands over to sales. Your Engagement Studio programs and automation rules are built on this map. A stage that only lives in someone’s head can’t be automated.
Get sales and marketing leaders to agree on one marketing qualified lead (MQL) definition. It should mix behavior, which is the score, with fit, which is the grade. Reps follow up on leads they trust. They trust rules they helped write.
4. Plan Folders, Naming Conventions and Campaigns
Set up your naming rules and folders before the first asset goes in. They decide whether anyone can find last year’s webinar form. They also cut the time spent on upkeep.
Plan your campaigns before you build assets too. Campaigns carry attribution in Salesforce. One catch-all campaign won’t show whether an event, an ad or organic traffic brought in the pipeline.
Last, choose your tracker domain and your sending domain. Don’t use the same domain for both. Salesforce warns that sharing one can hurt authentication and deliverability.
Account Engagement Setup: Step-by-Step Implementation
This is the hands-on part of the Account Engagement (Pardot) setup. The steps follow Salesforce’s own docs, so this Account Engagement implementation guide matches what you’ll see in your org. Each step names who usually does it.
Step 1: Install the AgentExchange (AppExchange) Package and Create a Business Unit
Who: Salesforce admin
Install the Account Engagement (Pardot) package before you touch the connector. Get the install link from Salesforce’s instructions. Don’t use the public AgentExchange (formerly AppExchange) listing, as Salesforce warns against it.
If the package is already in your org, skip ahead. The package adds a custom app, a custom tab and some custom fields on leads and contacts. On the security step, choose Grant access to admins only.
Next, open Business Unit Setup in Marketing Setup and click Assign Admin. Name the business unit and pick your Account Engagement admin. Set up one business unit at a time if you have several.
Choose this admin with care. You can’t change them later, and their name stays on the setup page. Then open Setup Assistant and turn Account Engagement on.
Step 2: Set Up Salesforce User Sync
Who: Salesforce admin, then Account Engagement admin
User Sync moves user management into Salesforce. Salesforce strongly recommends it. The Salesforce user record becomes the source of truth. Synced users turn read-only in Account Engagement. You can’t easily undo this, so both admins should agree first.
The Salesforce admin goes first. In Marketing Setup, open Business Unit Setup, then Manage Users, then Edit User Assignments. Add people to the Marketing Users or Sales Users group. Start with the people running the project. Put admins and most users in Marketing Users. Keep Sales Users for reps who need limited access.
The Account Engagement admin then opens the Salesforce connector settings. On the User Sync tab, they check the profile-to-role mapping, save and click Opt In. User changes take about 10 minutes to sync. Very large orgs can wait up to an hour.
Step 3: Map Fields and Configure the Salesforce Connector
Who: Account Engagement admin, with help from the Salesforce admin
Start with field mapping in Salesforce. Go to Setup > Object Manager > Lead > Fields & Relationships > Map Lead Fields. Map custom lead fields to contact fields. That way, values carry over when a lead converts. Leave the two Pardot URL fields out. Mapping them to each other creates duplicate prospects and breaks Visualforce pages.
The package adds Account Engagement fields, activities and list membership. They stay hidden until you add them to your lead and contact page layouts. For custom prospect fields, create the field in Account Engagement first.
Then pick its Salesforce match. Map phone fields to text fields, not number fields. Saving a mapping won’t start a sync on its own.
The version 2 connector starts paused. Nothing syncs until you unpause it. Use that time to set up connected campaigns. They add campaign influence and Engagement History. They also let marketers work with prospect data inside Salesforce. On Advanced or Premium edition, add Marketing Data Sharing rules to limit which records sync.
When you’re ready, go to Account Engagement Settings > Connectors. Click the gear icon and choose Edit Settings. Check the connector user, then select Unpause.
One step catches many teams out. The connector won’t turn existing leads and contacts into prospects. You have to import them. Import by CRM ID, not by email. New business units let several prospects share one email address. An email import would create duplicate leads or contacts in Salesforce.
Step 4: Add a Tracker Domain and Tracking Code
Who: Account Engagement admin, with IT or your hosting provider
A tracker domain rewrites your links and vanity URLs. This lets Account Engagement track clicks and visits. In Domain Management, click Add Tracker Domain. Enter a subdomain of your main domain, such as go.siteA.com for siteA.com. Pick a default campaign.
IT then creates a CNAME record that points to go.pardot.com. They also add the validation key to your DNS. DNS changes can take up to 24 hours. After that, click Validate. Once it passes, switch the default protocol to HTTPS.
Each campaign has its own tracking code. Paste it just before the closing </body> tag. Salesforce suggests using it on high-value pages, like landing pages and product pages. Keep it off general pages such as your home page. Business units created after February 13, 2023 use first-party tracking by default.
Step 5: Verify Your Sending Domain and Set Up DKIM
Who: Account Engagement admin, with IT
Account Engagement can’t send email until at least one sending domain is verified. Add the domain in Domain Management. Copy the validation key from Expected DNS Entries. IT adds it as a TXT record. Then click Check DNS Entries.
DKIM email authentication uses the same screen. Copy the DomainKey value. IT adds it as another TXT record. Repeat this for each domain you send from. SPF is set up by default. DKIM and DMARC are up to you. Mailbox providers check these records too. Gmail lists them in its sender rules for bulk email.
Check your email volume as well. Salesforce recommends a dedicated sending IP above 100,000 emails a month. Above 250,000, it’s required.
Step 6: Give Sales Access in Salesforce
Who: Salesforce admin
Turn on the Account Engagement Lightning app in Setup Assistant. Give users access to the b2bma_canvas connected app. Assign the Account Engagement User, Sales Cloud User, Service Cloud User or CRM User permission set. Then, in App Manager, make the app visible to each profile that needs it.
Reps should see engagement data on the records they already use. Add the Matched Leads Lightning component to account pages. It lists an account’s leads by engagement, so reps can find and convert the most active ones.
Show Engagement History on leads, contacts and campaigns. Its dashboards need Growth, Plus, Advanced or Premium edition. They don’t work in sandboxes.
Step 7: Build Forms, Emails and Landing Pages
Who: marketing team
Choose between forms and form handlers. A form is built and hosted in Account Engagement. A form handler takes data from a form hosted elsewhere, like WordPress or an event platform. Landing pages use a drag-and-drop builder. Save a few templates in your brand style first.
Emails use a drag-and-drop builder too. Set up A/B testing from your first campaign. Send two subject lines or CTAs to a small part of your list. Then send the winner to everyone else. Our guide to Salesforce email campaigns helps with planning.
Add custom fields to your forms to capture UTM tags. Keep repeated content in reusable snippets. Upload your eBooks and guides into Account Engagement. Each download is then logged against the prospect and can add to their score.
Step 8: Set Up Lead Scoring, Grading and Automation
Scoring tracks interest. Grading tracks fit. A score goes up each time a prospect engages with your content. A grade reflects company size, industry, job title and similar details. Your MQL definition should use both. Group prospects into static and dynamic lists by buying stages.
Automation rules and completion actions run as soon as a prospect acts. For example, they can send a lead to the right rep by territory after a form fill. Name and tag them clearly. Make sure they don’t clash with your Engagement Studio programs.
Agree on lead assignment rules with sales before you build them. Common criteria are location, estimated value, service area and project complexity. Then build your first Engagement Studio program. Good starting points are a nurture series, customer onboarding or a campaign for prospects who’ve gone quiet.
Step 9: Test, Train Users and Launch
Test the full chain, not one setting at a time. Submit a test form. Check that a prospect appears and links to the right lead or contact. Then check field mappings, email rendering, links and subscription preferences.
Test scoring, automation rules, lead assignment and campaign reports with sample records. Click through your tracker domains, preference pages and unsubscribe pages.
Use a sandbox if you have one. It comes with Advanced and Premium, and Plus can add it for a fee. Nothing copies across to production, so you rebuild your changes there. Sandboxes also can’t send email.
For training, run a team session first. Then share guides or short demo videos. Set up custom trailmixes on Trailhead, Salesforce’s free learning site. Give long-term admins extra workshops.
After launch, treat the first 90 days as tuning time. Watch connector errors, engagement, conversions and lead handoffs. Adjust scoring and nurture rules based on real results.
Account Engagement Features to Configure Early
Some features are easier to turn on now than to add once campaigns are live.
- Dynamic content changes text or images based on prospect data. Build versions of your landing pages, emails and CTAs. Check that each persona sees the right one. Use variable tags for single field values.
- B2B Marketing Analytics (B2BMA) gives you dashboards for pipeline, multi-touch attribution and campaign return. Set them up early so they start with clean data. They rely on connected campaigns, Campaign Influence 2.0 and contact roles. Your edition decides whether B2BMA is included.
- Campaign tracking needs one UTM framework for every channel. Test that the values reach your Salesforce campaign fields. Salesforce Engage gives reps marketing-approved email templates. They can reach out at the right time and see how each email performs.
Plan these with the rest of your Salesforce marketing automation and reporting.
What Is an Account Engagement (Pardot) Quick Start?
A Quick Start is a fixed setup package from an implementation partner. Many partners still call it a Pardot Quick Start. It usually covers these tasks:
- Turning on the Account Engagement Lightning app
- Setting up admins, accounts and business units
- Connecting the Salesforce connector
- Activating Engagement Studio
- Configuring lead scoring, email automation, automation rules and reports
Read the scope line by line. Packages differ. Some leave out system integration, customization, process automation, user training or ongoing support.
How Long Does an Account Engagement Implementation Take?
An initial Account Engagement (Pardot) setup takes 10 hours to two weeks. A full implementation usually takes 4 to 12 weeks. The main factors are the number of users, customization, data cleanup, workflow design and campaign volume.
Scope | Typical time |
Initial setup (core configuration) | 10 hours to 2 weeks |
Quick Start package | Up to 1.5 months |
Full implementation | 4 to 12 weeks |
Re-implementation or recovery | Longer, because of the system audit and optimization |
Some waiting is out of your hands. DNS changes can take up to 24 hours. Salesforce also advises setting up business units one at a time.
Common Account Engagement Implementation Mistakes to Avoid
Most of these look small on setup day. They get costly once campaigns depend on the data.
Mistake | What goes wrong | How to avoid it |
Skipping data cleanup | Duplicates and gaps throw off segmentation and CRM matching | Clean leads and contacts before you import prospects |
Wrong field mapping | Sync settings overwrite good data | Review mappings and sync behavior, then test with sample records |
Mapping the two Pardot URL fields to each other | Duplicate prospects and broken Visualforce pages | Leave these two fields unmapped |
Unpausing the connector too early | Records sync before anyone checks sharing rules and permissions | Set up connected campaigns and Marketing Data Sharing first |
Connector user without the right access | Data doesn’t sync, often due to missing permissions or Salesforce validation rules | Check the connector user’s object and field permissions, and your validation rules |
Importing by email address | Duplicate leads or contacts in Salesforce | Import by CRM ID |
Same domain for tracking and sending | Authentication and deliverability problems | Use separate domains or subdomains |
Launching automation without testing | Unwanted emails or leads sent to the wrong rep | Test forms, scoring, automation, consent and handoffs first |
Ignoring sync errors after launch | Records stop updating and nobody notices | Check connector status and sync errors often |
Conclusion
Most of the work happens before launch. You need clean prospect data and a connector set up in the right order. You also need scoring and automation rules that sales and marketing agree on together.
Work through this Account Engagement implementation guide from the checklist to Step 9. Test the whole workflow end to end. Then use the first 90 days to tune scoring and nurture rules.


