Pardot and Marketing Cloud Account Engagement refer to the same product. Setting up the product is the MCAE configuration workflow; the steps below cover navigating the naming gap when reading documentation, configuring integrations, and communicating with various audiences.
- Treat both names as equivalent
When you see Pardot or MCAE in documentation, integrations, or conversation, treat them as the same product. The technical configuration, APIs, and capabilities are identical.
- Use MCAE in formal Salesforce communication
For Salesforce-facing communication (sales calls, support cases, official proposals), use the current Marketing Cloud Account Engagement branding. It signals current product knowledge.
- Use Pardot for practitioner conversation
Among marketing operations practitioners, Pardot is shorthand. Using it speeds informal conversation and matches how most certifications, books, and tutorials describe the product.
- Search documentation under both names
When researching specific features, search Trailhead and the Salesforce Help under both names. Older content uses Pardot; newer content uses MCAE. Cover both to find the complete answer.
- Configure integration platforms using the Pardot connector
Third-party integration platforms (MuleSoft, Boomi, Workato) ship Pardot-named connectors. They work against the current MCAE product despite the older name.
- Reference the pi.pardot.com domain in technical work
Tracking code, form submissions, and email tracking flow through pi.pardot.com. CSP policies, ad blockers, and DNS configuration all encounter this domain.
- Pursue the Pardot Specialist certification
Salesforce has not renamed the cert. It validates current product capability under the Pardot name and remains the standard credential for marketing operations professionals.
- Plan terminology in customer-facing assets
Internal documentation can use either name. Customer-facing assets (marketing materials, training, proposals) increasingly use MCAE. Match the audience expectation.
Current Salesforce branding for sales, proposals, and official documentation. Signals up-to-date product knowledge.
Community standard for everyday conversation. Matches certifications, books, and tutorials.
Domain references (pi.pardot.com), tracking code, and integration connectors mostly still use the Pardot name.
- Pardot and MCAE refer to the same product. Treating them as different products produces confusion in conversations and documentation searches.
- The pi.pardot.com tracking domain remains active despite the rebrand. CSP policies and ad blockers may interpret it as unrelated third-party tracking; allowlist explicitly for MCAE-tracked sites.
- Older Salesforce documentation uses Pardot terminology that may not map to current MCAE feature names. Cross-reference current docs to confirm steps still match.
- The Pardot Specialist certification has not been renamed. New marketing operations hires sometimes assume the cert is outdated because it uses the older name; it is current.
- Integration platforms ship Pardot connectors that work against MCAE. The naming gap is cosmetic; the connector is correct.