PardotSettings Metadata Type in SFDX

Architectural Overview#

The PardotSettings metadata type manages the structural connector linking core Salesforce CRM with Marketing Cloud Account Engagement (formerly Pardot). Rather than relying on legacy connector users and manual API sync, modern enterprise architectures use PardotSettings to manage the v2 B2B Marketing connector, Salesforce User Sync, and Connected Campaigns.

By committing Pardot.settings-meta.xml into version control, enterprise architects can programmatically automate the provisioning of marketing applications across developer sandboxes and staging environments. This ensures that custom fields on Campaign, Lead, and Contact map seamlessly to prospect databases without manual admin intervention during release windows.

Directory and File Conventions#

In SFDX source format, PardotSettings is represented in the settings/ folder as Pardot.settings-meta.xml and referenced as Settings:Pardot.

Key Metadata Fields#

The PardotSettings type contains critical connector parameters:

Declarative XML and Package Manifest Examples#

Below is an enterprise configuration for synchronizing Salesforce CRM with Account Engagement:

<?xml version="1.0" encoding="UTF-8"?>
<PardotSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <enableMarketingAppExtension>true</enableMarketingAppExtension>
    <enablePardotApp>true</enablePardotApp>
    <enablePardotEnabledUser>true</enablePardotEnabledUser>
    <enableProspectActivityTracking>true</enableProspectActivityTracking>
</PardotSettings>

Scratch Org Definition Configuration#

When setting up scratch orgs for marketing development:

{
  "orgName": "Account Engagement Dev Org",
  "edition": "Enterprise",
  "features": ["Pardot", "MarketingCloud"],
  "settings": {
    "pardotSettings": {
      "enablePardotApp": true,
      "enablePardotEnabledUser": true,
      "enableProspectActivityTracking": true
    }
  }
}

Package Manifest (package.xml)#

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Pardot</members>
        <name>Settings</name>
    </types>
    <version>68.0</version>
</Package>

CLI Retrieval and Deployment Commands#

Manage PardotSettings using sf:

# Retrieve Pardot settings from the authenticated org
sf project retrieve start --metadata Settings:Pardot

# Deploy Pardot settings to the target environment
sf project deploy start --metadata Settings:Pardot

# Validate deployment against target org
sf project deploy validate --metadata Settings:Pardot

Architect Best Practices and Gotchas#

• User Sync Prerequisites: Prior to enabling enablePardotEnabledUser, verify that Salesforce user profiles and PermissionSet assignments have corresponding Pardot role mappings configured in Setup.
• Connected Campaigns Dependency: To maximize ROI reporting, couple PardotSettings with Connected Campaigns so campaign hierarchies in Salesforce CRM automatically mirror marketing execution structures in Account Engagement.
• Sandbox Refresh Strategy: When refreshing full or partial sandboxes, Account Engagement connectors disconnect by default. Deploying Pardot.settings-meta.xml helps automate the re-initialization of marketing app configurations.

Frequently asked questions

What is the primary function of PardotSettings in Salesforce?

PardotSettings enables the native integration bridge between Salesforce CRM and Marketing Cloud Account Engagement, governing user sync and campaigns.

Where is PardotSettings stored in an SFDX project source tree?

It is stored under force-app/main/default/settings/ as Pardot.settings-meta.xml and retrieved using the Settings:Pardot metadata identifier.

What does the enablePardotApp setting govern?

It enables the native Lightning Account Engagement application, embedding marketing assets and prospect reports directly inside Lightning Experience.

How does PardotSettings impact Connected Campaigns?

Configuring PardotSettings enables bidirectional syncing between Salesforce Campaigns and Account Engagement campaigns for centralized ROI reporting.