Simon Data vs Lytics
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.
Lytics retires the legacy audience builder, ships zero-copy Salesforce Data Cloud sync, and pushes integrations weekly.
Lytics is a CDP shipping at a steady weekly cadence. Recent work cuts across three vectors: a forced migration off the legacy audience builder (sunset May 4, 2026) toward a redesigned builder with geolocation rules; heavy expansion of cloud-warehouse and ad-platform integrations (Salesforce Data Cloud, The Trade Desk, Microsoft UET, Pushly, Algolia, GCS); and admin-side governance — naming conventions, metric threshold alerts, easier OAuth recovery.
Two arcs are visible. First, the integration catalog is being deepened toward server-side conversion APIs and zero-copy data movement — Salesforce Data Cloud's bidirectional sync with zero-copy bulk via GCS is the architecturally interesting move and likely a template for what's next. Second, the platform itself is being made more legible to large operators: naming conventions, threshold alerts, and reconnect-in-place auth all target customers running Lytics at scale rather than acquiring net-new ones.
Expect the next quarter to bring more zero-copy/streaming export jobs patterned after the Salesforce Data Cloud blueprint (Snowflake or Databricks are the obvious next targets), plus additional governance features — likely per-team audience permissions or audit-log enhancements — as the natural follow-on to naming conventions.
See more alternatives to Simon Data →
See more alternatives to Lytics →