NEW: Contract & SLA Management is now in open beta. Learn more →
Simon Data logo

Simon Data

Delivering the fastest out-of-the box results of any customer data platform.

Founded 2014 New York, New York, United States 51-200 employees Updated Mar 2026

Simon Data Pros & Cons

Key strengths and limitations to consider

Strengths

  • Connected deployment runs on customer Snowflake with minute-level latency
  • Native Braze and SFMC integrations documented and supported
  • Predict outputs delivered as usable datasets for activation/content

Limitations

  • Pricing is sales-led and based on contact volumes read
  • Connected deployment is Snowflake-only (managed otherwise)
  • Journeys, Mail, Predict appear as add-ons, not always included

Ideal For

Who benefits most from Simon Data

Quick Analysis

Simon Data competes in the enterprise CDP and marketing orchestration/activation layer segment, with an emphasis on using cloud data warehouse data (especially Snowflake) for segmentation, identity-aware profiles, and downstream activation to messaging and ad platforms. In practice it functions as a marketer-facing orchestration UI plus connectors/APIs that operationalize warehouse-modeled customer data into channels and journeys.

Strengths include strong Snowflake-oriented deployment options (managed vs connected), native downstream activation patterns (e.g., pushing segments to engagement tools), and add-on modules for journeys and predictive modeling that keep marketers out of BI/SQL for common lifecycle programs. It is best suited to data-mature, enterprise B2C brands (retail, travel, marketplaces, subscriptions) that already invest in a modern warehouse stack and want a CDP layer without replatforming to a closed suite. Key competitors to compare include Twilio Segment, mParticle, Tealium AudienceStream, Salesforce Data Cloud, and “warehouse-first” activation tools like Hightouch and Census.

Buyers should evaluate Simon Data when they need marketer-owned segmentation/journeys driven by warehouse data and want to minimize new data copies, but should validate (1) latency and data-sharing constraints for their Snowflake region/account setup, (2) identity model fit (IDs, hashing, anonymous-to-known), (3) breadth/quality of required channel connectors (email/SMS/push/ads), and (4) governance workflows (naming/tagging, access control, consent handling) across teams. If your primary need is event collection and real-time routing, Segment/mParticle may fit better; if your need is reverse-ETL-only activation without orchestration, Hightouch/Census may be a leaner choice.

1

Retail brand builds RFM and category affinity segments in Snowflake, syncs to Braze for lifecycle canvases

2

Travel company orchestrates cross-channel winback journeys using warehouse bookings + service signals

3

Marketplace triggers restock/price-drop messaging using latest inventory and pricing tables via dynamic content

4

Enterprise CRM team replaces weekly CSV audience pulls with automated feeds to SFMC via native/SFTP

5

Growth team uses Predict recommendations dataset to personalize email modules by next-best product

Custom Pricing

Capabilities

Core Capabilities

Data Unification / Profile Stitching Audience Segmentation Audience Activation / Sync Journey Orchestration Trigger-based Automation

Also Supports

Computed Traits / Aggregations Cross-channel Coordination Webhook Relay Event Stream Ingestion Privacy Compliance (GDPR/CCPA)

Pricing

Model

custom

Add Simon Data to Your Stack

Use our visual stack builder to see how Simon Data fits with your other tools. Plan data flows, identify gaps, and share with your team.

Open Stack Builder