Signals Surveys is part of Compass, the AI-first customer intelligence platform. Explore Compass

Service status

All systems operational.

Current state of every Signals service. Detailed real-time status, incident history, and subscriptions are published on the shared Compass status destination.

Contact support View the changelog

Sample content. This status board is a placeholder layout. The component states and seven-day history below are illustrative, not live monitoring data, and must be connected to real monitoring before launch.

Services

Component status.

  • Survey delivery

    Rendering and serving surveys and Sparks across storefront, thank-you page, email, and dedicated URLs.

    Operational

  • Response ingestion

    Accepting, validating, and recording submitted answers, including identity resolution to a Shopify customer.

    Operational

  • Shopify sync

    Reading customers, orders, products, and tags, and writing survey-derived attributes back to Shopify.

    Operational

  • Klaviyo sync

    Publishing survey events and profile properties to Klaviyo for segmentation and flow triggers.

    Operational

  • Compass sync

    Contributing declared responses to unified Compass profiles and audiences. Optional integration.

    Operational

  • Dashboard

    The Signals admin — survey editor, response views, analytics, and configuration.

    Operational

  • API

    The public REST API, webhook delivery, and the SDK surface built on top of them.

    Operational

Status is reported per service rather than as a single overall figure, because a Klaviyo sync delay and a survey delivery outage are very different problems for your store.

Recent history

The last seven days.

  1. All systems operational.
  2. All systems operational.
  3. All systems operational.
  4. All systems operational.
  5. No incidents recorded.
  6. All systems operational.
  7. All systems operational.

A longer incident history, uptime figures, and email or webhook status subscriptions are available on the shared status destination at status.compass.st.

How we handle degradation

What happens when something goes wrong.

Ingestion is protected first

If a downstream sync degrades, response ingestion keeps accepting answers and the sync catches up. A Klaviyo problem should never cost you a customer response.

Syncs retry, they do not drop

Failed sync operations are queued and retried with backoff rather than discarded, so a temporary outage delays delivery instead of losing it.

Isolation between tenants

One merchant's load or data volume does not affect another's. Tenant isolation is an implemented control, not an aspiration.

Incidents are written down

Anything with customer-visible impact appears here with what happened and what changed as a result.

Seeing something we are not?

Report it, even if this page is green.

A store-specific problem — one survey not rendering, one Klaviyo property not updating — will not show up here, because the service as a whole is healthy. Those are worth reporting directly. Include your store domain, the survey name, and roughly when you first noticed.

Report an issue Troubleshooting guide
  • Full status and subscriptions — status.compass.st
  • Did behaviour change on purpose? — Changelog
  • Common problems and fixes — Help center
  • Webhook delivery and retries — API reference
  • Security disclosure — Security

Start learning directly from your customers.

Build your first survey, publish a Spark, and turn every response into usable customer intelligence.

Install Signals See Signals in action