IBM Software / SaaS United States

Spark Compass

Marketing Personalization · Real-time Analytics

Spark Compass wanted venues such as stadiums, airports, and entertainment sites to understand in-person customers as well as digital businesses do, but fragmented ticketing, loyalty, mobile, POS, and location systems left operators unable to personalize offers, prove sponsor impact, or react in real time.

21% increase in attendance
75%+ engagement rates across physical venues
88% venue visit rate from location-based engagement campaigns
over 140M real-world behavior data points from 22,000 active users

Reported impact

Business outcome

Spark Compass helped venues improve engagement, attendance, and conversion while giving marketing, operations, concessions, and security teams a shared view of customers they can measure, own, and act on in real time.

  • Customer Experience
  • Productivity Improvement
  • Revenue Growth
  • Scalability

Solution

Spark Compass built an open, hybrid-cloud customer-intelligence platform on IBM watsonx technologies so venues could unify physical-world signals without giving up control of their data. The platform connects more than 100 modules and sources spanning ticketing, loyalty, mobile apps, transactions, location services, and operational signals into a real-time customer view. IBM watsonx.data consolidates those fragmented inputs into a single foundation, IBM watsonx.ai predicts behavior and recommends offers or next-best actions, IBM watsonx Orchestrate triggers follow-on actions such as messaging, signage updates, or staff notifications, and IBM watsonx.governance adds oversight for customer data and automated decisions. Because the architecture is modular and API-driven, venues can keep existing systems in place while applying AI to crowd movement, concessions, engagement campaigns, and sponsor measurement. The result is a governed intelligence layer for physical environments that behaves more like a digital growth platform than a standalone app.

Data flow

Ticketing, loyalty, mobile, transaction, and location signals stream into the Spark Compass platform, watsonx.data unifies them into a live customer profile, watsonx.ai scores behavior and recommends the next action, watsonx Orchestrate triggers outreach or operational changes, and venues use the measured results to refine future campaigns and staffing decisions.

Solution architecture

4 components · 4 layers
  1. Compute
    • IBM watsonx.ai Generates behavior predictions and personalized recommendations in the moment.
  2. Storage
    • IBM watsonx.data Creates the real-time single source of truth by consolidating fragmented venue and customer data.
  3. Orchestration
    • IBM watsonx Orchestrate Automates the downstream actions triggered by AI recommendations, from offers to staff notifications.
  4. Governance
    • IBM watsonx.governance Provides transparency and oversight for AI models, customer data usage, and automated decisions.

Architecture clues

  • Teams across marketing, operations, concessions, and security use the same customer view.
  • The architecture is open API-based and hybrid-cloud so venues retain data ownership.
  • The platform unifies over 100 modules with data sources and apps.

Evidence from the source

“IBM watsonx Orchestrate enables both conversational guidance and automated workflow orchestration.”
“IBM watsonx.ai powers the intelligence layer, suggesting personalized recommendations delivered via the Spark Compass platform”
“IBM watsonx.data provides the unified foundation, consolidating fragmented customer data into a real-time, single source of truth.”
“Spark Compass unified over 100 modules with data sources, mobile apps, loyalty systems, location services, transaction data, and real-time signals into a single, coherent customer view.”
“Venues achieved 75%+ engagement rates”
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    Spark Compass customer story

    First-party
    https://www.ibm.com/case-studies/spark-compass
    Source type
    Vendor-published customer story
    Published
    Jul 10, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.