Sales & Marketing AutomationThe CRM and Marketing Automation Guru's You Can Trust.
Sales & Marketing Automation
Connecting Salesforce and Pardot can look simple at first. A prospect enters Pardot, marketing activity is captured, information moves into Salesforce, sales follows up, and both teams use the same customer data. In practice, the connection becomes much more important than a basic data sync.
A strong Salesforce Pardot CRM integration needs clear rules for record identity, field ownership, lead creation, user access, campaign tracking, sales handoffs, selective syncing, automation, error handling, and reporting. When those rules are unclear, a working connector can still produce duplicate records, overwritten fields, missing prospects, wrong owners, incomplete campaign data, and reports that marketing and sales do not trust.
Pardot is now called Salesforce Marketing Cloud Account Engagement, although the Pardot name is still widely used by teams, documentation, searches, and older configurations. This guide uses both names where helpful while focusing on the current Salesforce and Account Engagement connection.
The goal is not simply to make Salesforce and Pardot exchange data. The goal is to build one controlled revenue system where marketing activity can become useful sales context without damaging CRM data or creating another layer of manual cleanup.
For a wider view of how CRM, marketing, sales, and automation should work together, review our sales and marketing automation guide and our B2B lifecycle automation framework.
A Salesforce Pardot CRM integration connects marketing engagement data in Account Engagement with lead, contact, account, campaign, opportunity, ownership, and other CRM information in Salesforce.
The connection allows marketing and sales to work from related records instead of keeping two isolated databases. Marketing can use Salesforce information to improve segmentation, qualification, nurture, and automation. Sales can see marketing activity and use that context when following up with a prospect.
But integration does not mean that every field, record, and automation should move freely in both directions.
A controlled integration answers several questions first:
These questions turn a connector into an integration strategy.
The Salesforce connector provides the technical path for information to move. It does not automatically create the right business rules for your company.
If a CRM has duplicate records, unclear ownership, old lifecycle stages, inconsistent country values, poor campaign naming, or conflicting automation, connecting another system can spread those problems rather than solve them.
Salesforce’s current Salesforce Connector v2 setup documentation separates configuration into Salesforce setup, Account Engagement setup, testing, and initial sync steps. That is a useful technical structure, but your business rules should be documented before data starts moving at scale.
If your CRM foundation needs attention first, review our CRM data quality strategy.
Start the project with the customer and revenue process rather than the connector settings.
Draw the path a record should follow from the first marketing interaction through qualification, sales ownership, opportunity creation, customer conversion, and future marketing communication.
Account Engagement is commonly used for forms, email marketing, nurture, scoring, segmentation, marketing automation, and engagement tracking. Salesforce commonly controls CRM ownership, sales activity, accounts, opportunities, pipeline, and other revenue data.
Your exact model may be different. What matters is that both teams know which system is responsible for each major type of information.
A basic operating model may look like this:
Some actions have enough business impact that they may need extra controls.
For example, changing an account owner, marking a person as a customer, changing opportunity status, overwriting a legal consent value, or assigning a large named account may require Salesforce rules or human review instead of unrestricted marketing automation.
Write these restrictions down before workflows are created.
A healthy connector depends on more than a green connection status.
Lead, contact, account, owner, opportunity, lifecycle, and campaign rules are defined.
The team knows how prospects match leads, contacts, and person accounts.
Assignment, qualification, suppression, field updates, and handoffs have clear owners.
Sync errors, unmatched records, routing, response, campaigns, and pipeline can be reviewed.
Once the business model is clear, configure the technical connection around that model.
For newer Account Engagement business units, Salesforce’s connector v2 setup follows three broad phases: enable Account Engagement, configure Salesforce, and configure Account Engagement. The connector is created in a paused state and should be reviewed before it is allowed to begin normal syncing.
Review the current Salesforce Connector v2 setup guide before changing a production environment.
The integration can only perform actions that its Salesforce access allows. Poor permissions can block records, fields, campaigns, or other actions from syncing.
Review object access, field access, record visibility, campaign access, and any custom objects used by the marketing process.
Do not treat broad permissions as a substitute for good design. The connector needs enough access to perform its job, but your sync strategy should still control which records and data are allowed into each business unit.
When you are changing selective-sync rules, field structures, or other high-impact configuration, keeping the connector paused can prevent records from entering the wrong state while the setup is incomplete.
Salesforce specifically tells admins to pause the connector before configuring or editing Marketing Data Sharing rules.
Before the first large sync, record:
This gives the team a baseline if something changes after launch.
Review Sales Cloud implementation, integration, automation, migration, support, and system-audit services from Sales & Marketing Automation.
One of the most important integration questions is simple: how does Account Engagement know which Salesforce record belongs to a prospect?
That answer affects duplicate control, imports, lead creation, contact relationships, reporting, and sales history.
Account Engagement business units that allow multiple prospects with the same email address use CRM IDs as a key part of the Salesforce relationship. Salesforce describes the goal as creating a one-to-one relationship between an Account Engagement prospect and a Salesforce lead, contact, or person account.
That is especially important when the same email address can appear on more than one Salesforce record.
Salesforce recommends using CRM ID when importing prospects from Salesforce where possible. This helps the new prospect connect directly to the intended CRM record instead of relying only on email matching.
Review Salesforce’s current guidance for multiple prospects with the same email address before changing import or matching processes.
When an Account Engagement connector is first created, existing Salesforce leads and contacts require special attention.
Salesforce’s initial prospect sync documentation explains that the connector does not simply create Account Engagement prospects for every Salesforce lead and contact that already existed before setup. Existing records may need to be imported so the prospect can be matched and future changes can sync.
Not every person who downloads a resource needs to become a Salesforce lead immediately.
You may choose to create a CRM record after:
Another company may send every valid prospect to Salesforce immediately. Either approach can work if it is intentional and reporting is designed around it.
Before automation acts, know which record the person belongs to.
Lead / Contact / Person Account
Prospect
Field mapping is where many Salesforce Pardot CRM integrations become difficult.
A field may exist in both platforms, but that does not mean both systems should have equal authority to change it.
Start with fields that control business decisions. Common examples include:
For many Account Engagement prospect fields, administrators can control whether the Account Engagement value, Salesforce value, or the most recently updated value should win when the two systems disagree.
Salesforce’s prospect field sync behavior documentation should be reviewed before changing these settings.
Do not automatically use “most recently updated” for every field. A newer value is not always a better value.
For example, if Salesforce controls territory after sales operations validates an account, a later marketing form should not necessarily overwrite that territory simply because the form submission happened more recently.
Integration problems can occur when Salesforce and Account Engagement field structures do not agree.
A dropdown in one system may contain values that are missing in the other. A field may be mapped to a lead but not a contact. A connector user may not be able to see the Salesforce field. A field type may not be supported for normal Account Engagement mapping.
Salesforce’s custom field mapping guidance notes several important points, including field visibility requirements and limits for certain Salesforce field types.
Fields that affect revenue, routing, customer status, consent, or reporting deserve stronger control than a basic preference field.
For each high-risk field, document:
Use a written rule for important fields before choosing technical sync behavior.
A clean integration should explain how a person moves between marketing and sales without creating unnecessary records or losing important context.
When a qualified Account Engagement prospect is ready for Salesforce, decide whether the normal destination should be a lead, an existing contact, or another supported record model.
Do not allow different campaigns to invent different record-creation rules unless there is a real business reason.
Before creating a new record or changing an owner, check whether the person already belongs to:
A form submission should add useful context to an established relationship rather than reset that relationship.
When Salesforce leads become contacts, make sure the fields that marketing depends on continue to work after conversion.
Review important lead and contact custom fields together. If marketing needs the same information before and after lead conversion, the CRM structure should preserve that information in a predictable way.
Marketing should know when a prospect becomes a customer or enters an active opportunity when that information changes campaign eligibility.
This helps prevent early-stage prospect emails from continuing after a real sales or customer relationship has started.
For a deeper lead-flow model, see our Salesforce lead management guide and marketing automation lead management guide.
Some Account Engagement environments need only part of the Salesforce database to sync into a business unit.
Marketing Data Sharing can be used in supported Account Engagement editions to define which Salesforce records are eligible to sync.
This becomes especially important when one Salesforce organization supports several brands, regions, products, or Account Engagement business units.
Write the business population in plain language first.
For example:
Then build the technical rule around a stable Salesforce field.
A selective-sync field should not change casually because normal sales activity happens.
If the rule depends on a field that salespeople frequently edit for another purpose, contacts can unexpectedly enter or leave the business unit.
Salesforce’s current Marketing Data Sharing documentation notes that lead and contact criteria need to be considered together when using selective sync for those objects.
This matters because a lead can later become a contact. The converted record should still belong to the correct marketing population.
Salesforce recommends pausing the connector before setting up or editing Marketing Data Sharing rules. That reduces the chance of data moving to the wrong business unit while the criteria are being changed.
If Salesforce and Account Engagement are only part of your stack, the HubSpot Health Check can review data structure, workflows, lifecycle stages, lead routing, and reporting inside your HubSpot environment.
A Salesforce Pardot CRM integration should connect more than contact fields. It should also help the business understand which marketing activity reached a person and how that activity relates to later sales movement.
Campaign names, record types, member statuses, hierarchy, ownership, and reporting rules should be planned before large amounts of marketing activity are connected.
If the Salesforce campaign structure is inconsistent, Connected Campaigns can make the same inconsistency more visible in Account Engagement.
Connected Campaigns lets teams align Salesforce campaigns with Account Engagement campaigns and manage campaign records through Salesforce.
Before turning the feature on or expanding it, identify:
Review Salesforce’s current Connected Campaigns setup guidance before enabling or restructuring the feature.
Campaign Member Sync can create Salesforce campaign-member records from Account Engagement activity when its requirements are met.
Salesforce states that Campaign Member Sync works from Account Engagement to Salesforce, and its current setup documentation warns that enabling the feature is a permanent change.
Because of that, review the current Campaign Member Sync documentation before enabling it.
A campaign can show useful marketing participation, but the CRM still needs lifecycle, ownership, opportunity, and sales activity data to explain what happened after engagement.
Campaign reporting is strongest when it is connected to a broader revenue model instead of being treated as a separate marketing report.
Source
Which campaign or marketing touch brought the person into the journey?
Response
What meaningful action did the prospect take after receiving the campaign?
Revenue
Did engagement move into sales acceptance, opportunity, pipeline, or another useful result?
The integration creates more value when Salesforce receives enough information for sales to understand why a prospect matters.
Sending a lead without context creates more work for the salesperson and makes the marketing score harder to trust.
Useful handoff information may include:
Routing should answer who owns the next action.
Ownership may depend on territory, account, product, business line, market, company size, named-account status, partner relationship, or another controlled rule.
If no valid owner can be found, do not silently leave the record unassigned. Send it to an exception queue or another visible review process.
The integration can track when a prospect became sales-ready and when sales took the first qualifying action.
This helps the business separate marketing-to-CRM delay from actual sales response time.
Not every sales-ready lead converts immediately.
When sales returns a lead to marketing, use controlled reasons such as timing, no budget, wrong person, not a fit, future project, duplicate, or another agreed category.
Those reasons can help determine whether the person should return to nurture, stay with the salesperson, be suppressed, or leave the normal marketing process.
A connector should not be considered tested because one lead moved successfully from Account Engagement to Salesforce.
The test needs to cover the different ways records can enter, change, fail, and leave the process.
Create controlled test prospects and confirm what happens when:
Change important values in Account Engagement and verify the expected Salesforce result. Then change the Salesforce value and verify the expected Account Engagement result.
Test both conflicting values and blank values.
Convert a test lead into a contact and confirm that the prospect remains connected to the correct CRM record and that important data continues to work.
Change an owner and confirm that routing, alerts, permissions, and Account Engagement assignment behave as designed.
Confirm that the correct campaign appears, membership is created where intended, statuses are usable, and the marketing team can see the expected engagement data.
Use test records for customers, active opportunities, unsubscribed people, competitors, employees, or any other group that should not receive normal marketing communication.
Create controlled failure cases such as an invalid field value, missing required data, inaccessible record, or unsupported value.
The team should know where the error appears and who is responsible for fixing it.
If your organization uses HubSpot alongside Salesforce or for another business unit, review the HubSpot pipeline funnel for help with pipeline structure and CRM process improvement.
Sync errors are not only technical problems. They are signals that something in the data model, permissions, CRM rules, or business process does not agree with the action the integration is trying to perform.
Salesforce lists data formatting, access, and process alignment among common causes of Account Engagement prospect sync errors.
Review the current Salesforce prospect sync error guide when investigating production errors.
A value may not meet Salesforce requirements. A number field may receive text. A state field may require a specific format. A dropdown may receive a value that Salesforce does not allow.
Do not simply correct the one record. Find the source of the bad value so the same problem does not continue.
The connector may be able to see one object but not edit a required field, campaign, contact, account, or related record.
Review object permissions, field-level access, sharing, ownership, queues, and any automation that expects the connector user to perform a Salesforce action.
A Salesforce Flow, validation rule, required field, duplicate rule, or other process can reject an update sent through the connector.
An Account Engagement sync error may therefore be caused by Salesforce business logic rather than Account Engagement itself.
If one field refuses to update while the rest of the record syncs, check:
A paused or unverified connector can explain wider syncing problems. Check connection health before investigating hundreds of individual records.
A Salesforce Pardot CRM integration should be measured as an operating system, not only as a technical connection.
A connector can have no visible outage while the business is still losing leads through missing owners, field conflicts, slow handoffs, bad campaign data, or records that never enter the correct platform.
Connect the integration to results such as opportunity creation, pipeline, conversion, customer movement, and other business outcomes that match your revenue process.
The integration is useful when it gives marketing and sales a clearer view of the same buyer journey.
Salesforce and Account Engagement will continue changing after launch. New fields are created. New campaigns appear. Teams change. Territories move. Products are added. Workflows are edited. New integrations are connected.
Governance keeps those changes from slowly damaging the integration.
Define who owns:
A small CRM edit can affect several marketing workflows.
Changes that deserve review may include:
Account Engagement and Salesforce user access should also have a controlled process.
Salesforce User Sync can align Salesforce users with Account Engagement users, profiles, and roles. Salesforce notes that enabling User Sync has a significant effect on user management and should be reviewed carefully before activation.
Do not wait until a major problem appears.
A regular review can cover:
If you need ongoing help managing automation and CRM operations, review how Sales & Marketing Automation can help.
Use the first month to find real operating problems before they become normal.
Watch the Connection Closely
Review new prospects, CRM creation, ownership, important fields, campaign activity, and sync errors several times during the initial launch period.
Compare Real Records to the Design
Check whether marketing and sales records are following the planned path instead of relying only on test records.
Fix Repeating Patterns
Group errors by cause and repair the field, workflow, permission, routing, or data rule creating the pattern.
Move Into Normal Governance
Document what changed, close remaining issues, set normal review ownership, and create the ongoing health dashboard.
A strong Salesforce Pardot CRM integration is not built by turning on every sync option. It is built by deciding what the business needs the two systems to do together.
Start with record identity. Define which leads and contacts belong in Account Engagement. Choose the CRM destination for qualified marketing prospects. Map only the fields that have a clear purpose. Decide which system owns important values. Protect customer and opportunity status. Create controlled campaign structures. Test the handoff from marketing to sales. Build visible exception paths for records the automation cannot confidently process.
Then monitor the integration after launch.
Review sync errors, duplicate records, missing owners, field conflicts, campaign membership, qualification, sales response, opportunity movement, and reporting. The connector should support the revenue process rather than become another system the team has to work around.
The best integration is understandable enough that a new administrator can see why records move, what controls the movement, what happens when something fails, and who owns the correction.
For more examples of CRM and marketing automation work across Salesforce, Pardot, Marketing Cloud, and other platforms, review our customer stories.
Need help with Salesforce, Pardot, CRM automation, lifecycle marketing, lead management, integrations, reporting, or ongoing marketing operations?
Salesforce Pardot CRM integration connects Salesforce CRM with Salesforce Marketing Cloud Account Engagement, formerly Pardot. The connection allows prospect information, selected CRM data, ownership, marketing engagement, campaigns, and other supported information to work across the sales and marketing process.
Salesforce renamed Pardot to Marketing Cloud Account Engagement. The Pardot name is still commonly used by customers, administrators, older documentation, search terms, and existing system labels, so both names are often used when discussing the platform.
No. Sync behavior depends on the record relationship, assignment, connector settings, business-unit configuration, and other rules. A prospect may already have a corresponding Salesforce record, or it may need to meet the conditions that allow Account Engagement to create or update a CRM record.
Not necessarily. Connector settings, record timing, permissions, Marketing Data Sharing, and business-unit configuration can affect whether a Salesforce record is created or available in Account Engagement. Existing Salesforce records also need special attention during the initial integration setup.
The matching method depends on the Account Engagement business-unit configuration and the situation. In business units that allow multiple prospects with the same email address, CRM IDs are an important part of the one-to-one relationship between prospects and Salesforce leads, contacts, or person accounts. Imports from Salesforce should use CRM ID where appropriate to preserve the intended relationship.
There does not need to be one answer for every field. Salesforce may control sales ownership, accounts, opportunities, territories, and customer status, while Account Engagement may control marketing scores and other marketing-specific information. The important step is to define the source of truth for every field that affects important business decisions.
For many prospect fields, Account Engagement administrators can configure sync behavior that determines which value takes priority. Options can include using the Account Engagement value, using the Salesforce value, or using the most recently updated value. The correct choice depends on the purpose and ownership of the field.
Common causes include an incorrect field mapping, mismatched field types or values, missing connector permissions, the wrong lead or contact field, a Salesforce validation rule, another CRM automation, an unsupported field type, a paused connector, or a sync error on the prospect.
The Salesforce record may be outside Marketing Data Sharing criteria, invisible to the connector user, missing required information such as an email address, created before the initial connector process, or affected by another configuration rule. Review the connector, permissions, selective-sync rules, and record history together.
Start with clean CRM data, understand how your business unit identifies prospects, use CRM IDs during Salesforce imports where appropriate, control when new CRM records are created, and test scenarios where the same email address already exists on a lead or contact. Duplicate prevention should also include Salesforce duplicate-management rules and clear lead-creation processes.
Marketing Data Sharing is a selective-sync feature available in supported Account Engagement environments. It can be used to control which Salesforce leads, contacts, opportunities, and supported objects belong in an Account Engagement business unit. It is especially useful when different business units should receive different CRM populations.
Connected Campaigns align Salesforce campaigns and Account Engagement campaigns so marketing teams can manage campaign structure through Salesforce while bringing Account Engagement activity into the connected campaign model. Campaign record types and campaign governance should be planned before the feature is expanded across the organization.
Campaign Member Sync can create Salesforce campaign membership from qualifying Account Engagement campaign activity. Salesforce documentation states that the member sync works from Account Engagement to Salesforce and warns that enabling Campaign Member Sync is a permanent change, so the configuration should be reviewed before activation.
Test new record creation, existing lead matching, existing contact matching, duplicate-email scenarios, CRM ID matching, field sync in both directions, blank values, owner changes, lead conversion, customer status, active opportunities, Marketing Data Sharing exclusions, campaign membership, forms, qualification, routing, opt-outs, Salesforce automation, and controlled failure scenarios.
Monitor connector status, prospect sync errors, duplicate records, missing owners, field conflicts, excluded records, campaign membership, qualification-to-assignment time, sales response, opportunity creation, pipeline movement, and any manual corrections required by marketing or sales.
Review critical errors and lead-flow problems regularly, then perform broader reviews after major CRM, campaign, territory, user, field, automation, or business-unit changes. A scheduled integration health review can also help find slow data-quality problems before they become larger reporting or revenue issues.