Simon Data vs Pardot
Side-by-side trajectory, velocity, and editorial themes.
Simon Data is shipping integration after integration — Movable Ink Da Vinci, Rokt, Criteo semantic matching, Amazon Ads.
Simon Data's recent cadence is dominated by activation-channel reach. April 2026 added Movable Ink Da Vinci (AI-driven email orchestration via SFTP) and Rokt (e-commerce engagement audiences). Q1 2026 brought Criteo semantic email matching, custom base URL support for self-hosted MessageFlow and ExpertSender deployments, a 14-day send-or-click attribution window, credentials search, and a Redlink → MessageFlow rename. Earlier shipping included Oracle Hospitality as a data source, Privacy Request Expirations with configurable TTL, and Braze user-alias fallback.
Simon Data is positioning itself as the CDP that plays nicely with the broadest set of activation channels — including AI-driven ones like Movable Ink Da Vinci. The integration roadmap is working harder than the core product on the value story; that's defensible for a CDP, where each connector represents real revenue, but it suggests the platform itself is in maintenance mode while the integrations team carries the cadence.
Expect more AI-activation integrations (other generative-email vendors, retail-media platforms beyond Amazon and Rokt), continued attribution-window flexibility, and possibly a Simon-side AI feature that uses the customer-data graph to suggest segments — that would be the directional break from pure integration cadence.
Pardot's Summer '26 release shows the bridge to Marketing Cloud Next is being built feature by feature.
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.
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.
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.
See more alternatives to Simon Data →
See more alternatives to Pardot →