LoginSign Up
← Back to all sparks
Pardot logo

Pardot

MKT AUTO
Velocity6.3

Salesforce B2B marketing automation

www.salesforce.com/products/pardot/overview ↗

Pardot's Summer '26 release shows the bridge to Marketing Cloud Next is being built feature by feature.

summer-26-releasemarketing-cloud-nextconsent-managementpardot-migrationsalesforceingestion-noise
◆Current state
The substantive signal in this window is the Salesforce Summer '26 release for Marketing Cloud Account Engagement (the artist formerly known as Pardot): consent data now syncs between Account Engagement and Marketing Cloud Next via static public list mapping, plus expanded email capabilities (CC recipients, archiving) inside Marketing Cloud Next. The rest of the captured feed is broken scrapes of Salesforce help pages - mostly CSS errors and JavaScript exceptions.
◆Where it's heading
Salesforce is gradually wiring Pardot into Marketing Cloud Next rather than sunsetting it abruptly - consent sync and shared email primitives are the kind of integrations that smooth a long-running migration. Expect each seasonal release to add another shared object (subscriptions, audiences, journeys, attribution) until the practical difference between the two products narrows. The ingestion problem on the source side is severe; most product-relevant context is buried under broken page captures.
◆Prediction
Next likely beats: shared audience and segmentation primitives between Account Engagement and Marketing Cloud Next, plus journey-stitching across both. On data quality, the Salesforce help center scraping needs a different ingestion approach - likely the official release-notes RSS or PDF rather than the JS-rendered help portal.

◆Recent moves

  1. 13d ago

    Marketing Cloud Account Engagement Summer '26 Release Notes

    ⚡ SPARK

    The Summer '26 release for Account Engagement/Pardot adds consent-data sync to Marketing Cloud Next, plus CC and archive email capabilities inside Marketing Cloud Next. The first concrete migration-path features for the Pardot install base wondering how Salesforce plans to converge the two products.

    View source ↗
  2. 20d ago

    Duplicate of Summer '26 release notes

    Duplicate capture of the same Summer '26 release content, posted a week earlier with overlapping feature copy. No new product change.

    View source ↗
  3. 1mo ago

    Broken scrape: Salesforce help center cookie banner

    Broken scrape of a Salesforce help center page - the content is the cookie consent banner and a CSS error message rather than any product release content.

    View source ↗
  4. 1mo ago

    Broken scrape: Salesforce help portal JS error

    Another broken capture - the Salesforce help portal threw a JavaScript TypeError that landed in the body field instead of the actual release notes.

    View source ↗
  5. 1mo ago

    Broken scrape: Salesforce help center CSS error

    Same CSS-error capture pattern repeating. Underlines that the Salesforce help portal needs a different ingestion approach than rendered HTML scraping.

    View source ↗
  6. 1mo ago

    Broken scrape: Salesforce help portal JS error

    Broken scrape with the Salesforce verified-domain email policy fragment leaking into the body. No usable release content captured.

    View source ↗